Genera con IA un borrador de postmortem de un incidente
Un agente combina un incidente de una página de estado con el registro de un pago afectado y rellena una plantilla de postmortem sin culpables.
- Archivos
- Conexión de solo lectura
- Web
- Límite de presupuesto
Mira una ejecución real
Una ejecución real del 7 oct 2026, reproducida. Modelo: openai/gpt-6-luna.
{
"payment_id": "pay_124",
"status_url": "https://ephemer.al/api/samples/status"
}- En colapresupuesto de $0.05 reservado
- MicroVMmicroVM ready
- MicroVMworker started · shell off · web on
- Conexiónpayments GET /payments/pay_124
- Conexiónpayments GET /payments/pay_124/attempts
- Web
web_fetch https://ephemer.al/api/samples/status - Archivo
read postmortem-template.md - Resultado
payments GET → 200 - Resultado
payments GET → 200 - Resultado
web https://ephemer.al/api/samples/status → 200 - MicroVMmicroVM destroyed
- Completada2 llamadas al modelo, 4,039 tokensResultado grabado (en inglés)
Postmortem: Elevated card payment errors in Europe
Blameless. Describe what happened and what the system allowed, not who did it.
Summary (2 sentences)
On 2026-10-05, some EU card payments failed with processor timeouts during an incident. Payment
pay_124failed with a processor timeout and was not retried in the recorded attempt.Impact (who, how many, how long, money if known)
One failed payment is documented: €129.00. Total customers and payments affected are not known. The incident timeline says affected failures occurred between 13:25 and 14:15 UTC.
Timeline (UTC, one line each, only facts from the sources)
- 2026-10-05 13:31 UTC — Incident investigating: some EU card payments failed with a processor timeout.
- 2026-10-05 13:42:51 UTC —
pay_124failed; its attempt recorded a processor timeout. - 2026-10-05 13:58 UTC — Incident identified as a network change at one acquiring partner.
- 2026-10-05 14:20 UTC — Incident resolved; card payments in Europe were processing normally. Failed payments from 13:25–14:15 UTC could be retried.
Cause
The incident source attributes the errors to a network change at one acquiring partner.
What went well
The incident was identified and resolved, and the status update said affected payments could be retried.
Action items (owner role, not a person)
Not known from the sources.
- Worker destruido$0.004235 cobrados, $0.045765 liberados
Ejecútalo tú mismo
Abre el ejemplo en el playground con la solicitud completa ya rellenada. Se ejecuta en tu propia cuenta, dentro del presupuesto indicado, contra los mismos sistemas de ejemplo de solo lectura.
Presupuesto de este ejemplo: $0.05
Cómo funciona
Dos fuentes de solo lectura y una plantilla. El agente lee la cronología del incidente en la página de estado y el pago fallido en la API de pagos, y escribe únicamente lo que dicen esas fuentes. Las acciones de mejora nombran roles, no personas.
Lo que el agente puede y no puede hacer
Los permisos forman parte de la solicitud. Todo lo que no figura aquí no está disponible para la ejecución.
| Ajuste | Permitido |
|---|---|
| Conexiones | payments: solo GET, en ephemer.al/api/samples/payments-api |
| Web | Solo ephemer.al |
| Shell | Desactivado |
| Archivos | postmortem-template.md (solo lectura) |
| Retención cero de datos | Desactivada: el registro se conserva 30 días |
| Presupuesto | $0.05, límite estricto |
| Tiempo límite | 120 segundos |
Las credenciales nunca entran en la máquina: un broker las añade a cada llamada y aplica los métodos indicados arriba.
El código
Esta es la solicitud exacta que envía el ejemplo. Define EPHEMERAL_API_KEY con una clave de miembro de tu organización.
curl -X POST $EPHEMERAL_URL/v1/runs \
-H "Authorization: Bearer $EPHEMERAL_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d @request.jsonArchivos de la solicitud
Se pasan en línea, así que no hay que subir nada antes. El agente ve cada uno como un archivo de solo lectura.
postmortem-template.md
# Postmortem: <title>
Blameless. Describe what happened and what the system allowed, not who did it.
## Summary (2 sentences)
## Impact (who, how many, how long, money if known)
## Timeline (UTC, one line each, only facts from the sources)
## Cause
## What went well
## Action items (owner role, not a person)
Cuerpo completo de la solicitud request.json
El mismo cuerpo, con los archivos en línea.
{
"prompt": "Write a postmortem draft for the incident that affected the payment in input.payment_id. Read the payment and its attempts from the payments connection, and the incident timeline from input.status_url with web_fetch. Fill postmortem-template.md, at most 250 words in total. Put every timeline line in UTC and only from the sources. If the sources do not show something (such as the number of customers affected), write 'not known' instead of estimating. Use only what the data returns and never guess; if a call fails or a field is missing, say so.",
"input": {
"payment_id": "pay_124",
"status_url": "https://ephemer.al/api/samples/status"
},
"files": [
{
"path": "postmortem-template.md",
"content": "# Postmortem: <title>\n\nBlameless. Describe what happened and what the system allowed, not who did it.\n\n## Summary (2 sentences)\n## Impact (who, how many, how long, money if known)\n## Timeline (UTC, one line each, only facts from the sources)\n## Cause\n## What went well\n## Action items (owner role, not a person)\n"
}
],
"connections": {
"payments": {
"type": "http",
"url": "https://ephemer.al/api/samples/payments-api",
"auth": {
"type": "bearer",
"token": "sample_read_key"
},
"allowed_methods": [
"GET"
],
"instructions": "GET /payments/{id} returns a payment (status, amount in cents, currency, failure_code, failure_message, attempt_count). GET /payments/{id}/attempts returns its attempts."
}
},
"web": {
"allow": [
"ephemer.al"
],
"search": false
},
"shell": false,
"timeout_seconds": 120,
"max_cost_micros": 50000
}