Event Idempotency Audit
Find out whether a batch can be deduplicated. Reports events carrying no id at all, ids that repeat with an identical payload - a redelivery a consumer must be idempotent about - and, separately, ids that repeat with a different payload, which means the id is not identifying the event. Volatile fields such as a delivery timestamp can be excluded from the comparison without being excluded from the duplicate detection.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
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.
Pay 0.11 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
- 110000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "110000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"events": [
{
"type": "order.created",
"total": 42.5,
"offset": 101,
"stream": "orders-0",
"event_id": "evt-1",
"order_id": "o-1",
"schema_version": "2"
},
{
"type": "order.created",
"total": 19.99,
"offset": 102,
"stream": "orders-0",
"event_id": "evt-2",
"order_id": "o-2",
"schema_version": "2"
},
{
"type": "order.created",
"total": 7,
"offset": 104,
"stream": "orders-0",
"event_id": "evt-4",
"order_id": "o-4",
"schema_version": "2"
},
{
"type": "order.created",
"total": 7.5,
"offset": 105,
"stream": "orders-0",
"event_id": "evt-4",
"order_id": "o-4",
"schema_version": "2"
},
{
"type": "order.created",
"total": "12.00",
"offset": 106,
"stream": "orders-0",
"event_id": "evt-5",
"order_id": "o-5",
"schema_version": "1"
},
{
"type": "order.cancelled",
"offset": 1,
"reason": "customer",
"stream": "orders-1",
"event_id": "evt-6",
"order_id": "o-1",
"schema_version": "2"
},
{
"type": "order.cancelled",
"offset": 2,
"reason": "fraud",
"stream": "orders-1",
"order_id": "o-2",
"schema_version": "2"
}
],
"id_field": "event_id",
"ignore_pointers": [
"/offset"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxEvents": 2000,
"maxSchemas": 100,
"maxFindings": 500,
"maxAttributes": 500,
"maxPartitions": 500,
"cardinalityWarning": 100
},
"passed": false,
"complete": true,
"findings": [
{
"code": "IDEMPOTENCY_KEY_MISSING",
"event": 6,
"detail": "Event 6 carries no event_id, so no consumer can deduplicate it."
},
{
"id": "evt-4",
"code": "DUPLICATE_ID_DIVERGENT_PAYLOAD",
"event": 3,
"detail": "event_id evt-4 appears at events 2 and 3 with different payloads, so the id is not identifying the event.",
"changes": [
{
"to": "7.5",
"code": "TYPE_CHANGED",
"from": "7",
"pointer": "/total",
"to_type": "number",
"from_type": "integer"
}
]
}
],
"request_id": "example-request",
"service_id": "event_idempotency_audit",
"assumptions": [
"A repeat whose payload matches is a redelivery, which is normal and which a consumer must be idempotent about. A repeat whose payload differs means the id is not identifying the event, which is a diff...",
"Volatile fields such as a delivery timestamp can be excluded, and exclusions are applied to the comparison only, never to the duplicate detection."
],
"limitations": [
"Identity and duplication within the batch supplied. A duplicate across two batches is not visible here.",
"deduplicable is true only when every event carried an id and no id was repeated."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"deduplicable": false,
"not_examined": [],
"divergent_ids": [
"evt-4"
],
"finding_count": 2,
"service_version": "1.0.0",
"findings_by_code": {
"IDEMPOTENCY_KEY_MISSING": 1,
"DUPLICATE_ID_DIVERGENT_PAYLOAD": 1
},
"distinct_id_count": 5,
"events_without_id": 1,
"repeated_id_count": 1,
"divergent_id_count": 1,
"examined_event_count": 7,
"supplied_event_count": 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",
"id_field"
],
"properties": {
"events": {
"type": "array",
"items": {
"type": "object"
},
"maxItems": 2000,
"minItems": 1
},
"id_field": {
"type": "string",
"maxLength": 256
},
"ignore_pointers": {
"type": "array",
"items": {
"type": "string",
"maxLength": 512
},
"maxItems": 100,
"minItems": 1
}
},
"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 07:58Z
- Last indexed by Roundhouse
- 2026-10-07 01:11Z
- Last enriched (probe, favicon, geo)
- 2026-10-04 11:16Z
- 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
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 4 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Event Idempotency 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=Event%20Idempotency%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/event-idempotency-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.