event idempotency audit derived

api.zfinia.comSearch derived

POST https://api.zfinia.com/x402/v1/event-idempotency-audit

passabsent from every registry#9 by calls of 27 on this host

0.11 USDC

per call, as the listing declares it on eip155:8453

Compare with another Every figure as JSON Cite this page

the price, as of 2026-10-06 18:20 UTC · method

Validation state: pass; as of 2026-10-06 11:05 UTC · method · sweep daily-2026-10-06
Uptime, 7 / 30 / 90 days: 100% / 100% / 100%; as of 2026-10-06 11:05 UTC · method · 4 of 4 in 7d, 4 of 4 in 30d, 4 of 4 in 90d
Calls, trailing 30 days: 1; as of 2026-10-06 18:20 UTC · method
Unique payers, trailing 30 days: 1; as of 2026-10-06 18:20 UTC · method
Last called: 2026-10-04 07:58 UTC; as of 2026-10-06 18:20 UTC · method
First observed by TOLLderived: 2026-10-04; as of 2026-10-04 12:19 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived: 0.11 USDC; as of 2026-10-06 18:20 UTC · method · on eip155:8453
Networks: 1; as of 2026-10-06 18:20 UTC · method

Counters

7 observations, 1 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

Calls counted in the trailing thirty days across the 2,564 endpoints in Search that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 1,731 in the category are counted higher and 832 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 7 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.

In words

event idempotency audit was missing from the Coinbase registry at the pull of 2026-10-07, confirmed at the pull of 2026-10-07; that is registry presence, not liveness.

event idempotency audit is a POST endpoint at api.zfinia.com, listed in neither registry at the last pull and filed by TOLL under search.

event idempotency audit is priced at 0.11 USDC on Base.

The request to event idempotency audit is a json body with the fields events, id_field and ignore_pointers.

event idempotency audit answered the sweep of 2026-10-06 with a valid 402, as at every sweep since 2026-10-04.

A response from event idempotency audit, as declared, includes limits, passed, complete, findings, request_id, service_id and 2 others.

event idempotency audit shares api.zfinia.com with 26 other listed endpoints and is tied 9th by calls with 19 others.

event idempotency audit takes 3% of the calls counted across api.zfinia.com.

In the trailing 30 days: one call, one payer.

event idempotency audit was last called 4 days before the snapshot.

Closest in price to event idempotency audit within search: fullenrich people search at stableenrich.dev and aviation flight at api.x402node.dev.

event idempotency audit is near the top of prices in search; 96% of comparable listings are cheaper.

The wallet paid by event idempotency audit is the payee of 179 endpoints across 5 hosts.

The seller's own tags are events, idempotency, deduplication and data quality.

Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.

Payment options as declared

the payment options, as of 2026-10-06 18:20 UTC · method

Every payment option declared on this listing
registry	network	asset	amount	scheme	pay to
Coinbase	eip155:8453	USDC	0.11 USDC	exact	0x25e824…6a9608

Preflight checks at the last sweep

the checks, as of 2026-10-06 11:05 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTC	state	sweep
2026-10-06 11:05 UTC	pass	daily-2026-10-06
2026-10-05 09:51 UTC	pass	daily-2026-10-05
2026-10-04 13:12 UTC	pass	daily-2026-10-04
2026-10-04 12:40 UTC	pass	new-after-daily-2026-10-04

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

2026-10-07 13:20 UTCabsence from Coinbase confirmed, rule v1
2026-10-07 05:57 UTCabsent from Coinbase at this pull
2026-10-04 12:19 UTClisted in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 07:58 UTC · method

The input and output block

{
  "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
    }
  }
}

What the listing says

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 record, 2026-10-04 07:58 UTC · method

As declared

POST
eip155:8453
USDC
exact

Every tag is a field on the listing, not a keyword TOLL assigned.

Who is paid

0x25e824…6a9608

Takes payment for 179 endpoints on 5 hosts.

Among Search

counted above0%

of 2,564 that carry counters

cheaper than96%

of 2,568 with a comparable price

2,626 endpoints are in this category. 1 declare exactly this price.

the comparison, 2026-10-07 23:04 UTC · method · live

Nearest on price

google searchapi.strale.io0.108 USDClegacy v1
searchblockrun.ai0.081 USDCpass
fullenrich people searchstableenrich.dev0.15 USDCpass
aviation flightapi.x402node.dev0.15 USDCpass
serp readapi.kadec0.xyz0.08 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-10-07 23:04 UTC · method · live

Elsewhere in the record

Cite this page

This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "event idempotency audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-event-idempotency-audit-95948d. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-event-idempotency-audit-95948d-2026-10-07,
  author = {TOLL},
  title = {event idempotency audit on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-event-idempotency-audit-95948d}},
  year = {2026},
  month = {10},
  note = {Frozen at its last observation, 2026-10-07 23:04 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about event idempotency audit, or reply as the named seller