Incident Timeline Audit
Derive incident durations from a timeline and report what makes them unreliable. The finding that matters: a phase recorded before the phase that must precede it, which means a time was backfilled, so every duration derived from the pair is fiction. Also reports a time with no UTC offset, which during an incident means somebody wrote their own zone; a missing phase, so a duration cannot be derived; an unrecorded gap of an hour or more; and a derived duration beyond a target the caller states.
Dataofflineeip155:8453Exactvia cdp
Incident responsePostmortemReliability metricsData qualityDeveloper tooling
Settlements · 30d
218↓ 56%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$25.30
Verified settled volume
255 settlements proven x402 by their on-chain EIP-3009 marker.
$0.130
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-10-04 08:35Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x25e8245f07d5e4873987293dad666afbe56a9608The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Provider
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
0.13USDC≈ $0.13 USD
on Base · exact scheme
Pay 0.13 USDC on Base to 0x25e8…a9608. The signed payment is good for 1 minute.
- Paid to
- 0x25e8…a9608
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 130000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "130000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"events": [
{
"at": "2026-09-30T02:10:00Z",
"phase": "began",
"description": "deploy of 1.4.0 begins"
},
{
"at": "2026-09-30T02:55:00Z",
"phase": "acknowledged",
"description": "on call acknowledges"
},
{
"at": "2026-09-30T03:02:00Z",
"phase": "detected",
"description": "alert fires"
},
{
"at": "2026-09-30T04:35:00",
"description": "rollback starts"
},
{
"at": "2026-09-30T04:50:00Z",
"phase": "resolved",
"description": "error rate normal"
}
],
"targets": {
"detect_minutes": 10,
"resolve_minutes": 60,
"acknowledge_minutes": 5
}
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxLines": 20000,
"maxSpans": 10000,
"maxFields": 500,
"maxSamples": 20000,
"maxFindings": 500,
"maxJsonBytes": 2097152
},
"passed": false,
"coherent": false,
"complete": true,
"findings": [
{
"code": "TIMESTAMP_WITHOUT_OFFSET",
"detail": "events[3] has a time with no UTC offset. During an incident people write times in their own zone, and a timeline that mixes zones silently produces durations that are hours wrong."
},
{
"code": "PHASE_MISSING",
"phase": "mitigated",
"detail": "No mitigated event is recorded, so the durations that depend on it cannot be derived."
},
{
"code": "PHASES_OUT_OF_SEQUENCE",
"phase": "acknowledged",
"detail": "acknowledged is recorded 7 minutes before detected, which cannot have happened. One of the two times was backfilled, and every duration derived from them is fiction."
}
],
"last_event": "2026-09-30T04:50:00.000Z",
"request_id": "example-request",
"service_id": "incident_timeline_audit",
"assumptions": [
"A time with no UTC offset is reported rather than assumed, because during an incident people write times in their own zone and a timeline that mixes them silently produces durations hours wrong.",
"A phase out of sequence is reported as a backfilled time rather than as an impossible event, because that is what it is, and every duration derived from it is fiction.",
"The earliest event of a repeated phase is the one used, and the repetition is reported so the choice is visible."
],
"event_count": 5,
"first_event": "2026-09-30T02:10:00.000Z",
"limitations": [
"The events supplied. What happened in an unrecorded gap, and whether a recorded time is accurate, are outside this.",
"coherent is true only when every phase is present, in sequence, and every target the caller supplied was met."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 6,
"phases_recorded": [
"began",
"acknowledged",
"detected"
],
"service_version": "1.0.0",
"findings_by_code": {
"PHASE_MISSING": 1,
"UNRECORDED_GAP": 1,
"TARGET_EXCEEDED": 2,
"PHASES_OUT_OF_SEQUENCE": 1,
"TIMESTAMP_WITHOUT_OFFSET": 1
},
"total_span_minutes": 160,
"largest_gap_minutes": 93,
"time_to_detect_minutes": 52,
"time_to_resolve_minutes": 160,
"time_to_mitigate_minutes": null,
"time_to_acknowledge_minutes": -7
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"events"
],
"properties": {
"events": {
"type": "array",
"items": {
"type": "object",
"required": [
"at"
],
"properties": {
"at": {
"type": [
"string",
"number"
]
},
"phase": {
"enum": [
"began",
"detected",
"acknowledged",
"mitigated",
"resolved"
],
"type": "string"
},
"description": {
"type": "string",
"maxLength": 512
}
},
"additionalProperties": false
},
"maxItems": 5000,
"minItems": 1
},
"targets": {
"type": "object",
"properties": {
"detect_minutes": {
"type": "number",
"minimum": 0
},
"resolve_minutes": {
"type": "number",
"minimum": 0
},
"acknowledge_minutes": {
"type": "number",
"minimum": 0
}
},
"additionalProperties": false
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-04 08:35Z
- Last indexed by Roundhouse
- 2026-10-05 00:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-05 00:46Z
- x402 version
- 2
- Max timeout
- 60s
- Liveness probe
- HTTP 0
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Incident Timeline Audit and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Incident%20Timeline%20Audit' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.zfinia.com/x402/v1/incident-timeline-audit, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.