passabsent from every registry#7 by calls of 15 on this host
0.12 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-04 21:22 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:09 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.12 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 2 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.
Of api.zfinia.com's 15 listings, key coverage audit ranks tied 7th by calls with 9 others.
Callers of key coverage audit supply a json body with the fields key and datasets.
A response from key coverage audit, as declared, includes limits, passed, complete, datasets, findings, request_id and 2 others.
key coverage audit drew a single call from a single payer in the trailing 30 days.
The last call to key coverage audit came 9 days before the snapshot, 2026-10-04.
A call to key coverage audit costs 0.12 USDC on Base, as declared.
Of the calls counted across api.zfinia.com, key coverage audit takes 4%.
At api.zfinia.com, key coverage audit takes POST requests, is listed in neither registry at the last pull, and falls under search by TOLL's rules.
key coverage audit answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to key coverage audit within search: aviation flight at api.x402node.dev and search at blockrun.ai.
key coverage audit is near the top of prices in search; 97% of comparable listings are cheaper.
The wallet paid by key coverage audit is the payee of 179 endpoints across 5 hosts.
The seller's tags on key coverage audit are data quality, coverage, master data and reconciliation.
key coverage audit was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; that is registry presence, not liveness.
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.
the payment options, as of 2026-10-04 21:22 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.12 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 13:04 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 13:04 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:31 UTC | pass | 0 | new-after-daily-2026-10-04 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 08:10 UTC · method
The input and output block
{
"input": {
"body": {
"key": [
"customer_id"
],
"datasets": [
{
"csv": "customer_id\nC-001\nC-002\nC-003\n",
"name": "crm"
},
{
"csv": "customer_id\nC-001\nC-002\n",
"name": "billing"
},
{
"csv": "customer_id\nC-001\nC-004\n",
"name": "warehouse"
}
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxRows": 5000,
"maxListed": 200,
"maxColumns": 64,
"maxCsvBytes": 262144,
"maxDatasets": 10,
"maxFindings": 500,
"maxCategories": 1000,
"maxKeyColumns": 4
},
"passed": false,
"complete": true,
"datasets": [
{
"name": "crm",
"rows": 3,
"distinct_keys": 3
},
{
"name": "billing",
"rows": 2,
"distinct_keys": 2
},
{
"name": "warehouse",
"rows": 2,
"distinct_keys": 2
}
],
"findings": [
{
"key": "C-003",
"code": "KEY_IN_ONE_DATASET_ONLY",
"detail": "C-003 appears only in crm.",
"dataset": "crm"
},
{
"key": "C-004",
"code": "KEY_IN_ONE_DATASET_ONLY",
"detail": "C-004 appears only in warehouse.",
"dataset": "warehouse"
},
{
"key": "C-002",
"code": "KEY_MISSING_FROM_SOME_DATASETS",
"detail": "C-002 is present in crm, billing and missing from warehouse."
}
],
"request_id": "example-request",
"service_id": "key_coverage_audit",
"assumptions": [
"Keys are canonicalised exactly, so the same identifier formatted differently across systems is one key.",
"A key present in three of five datasets is reported as such. A pairwise comparison cannot express that, which is why coverage is counted across all datasets at once."
],
"limitations": [
"Key presence across the datasets supplied. Whether the rows behind a shared key agree is dataset_reconciliation, not this.",
"fully_covered is true only when every dataset was fully read and every key appeared in all of them."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"unique_keys": [
{
"key": "C-003",
"only_in": "crm"
},
{
"key": "C-004",
"only_in": "warehouse"
}
],
"not_examined": [],
"partial_keys": [
{
"key": "C-002",
"present_in": [
"crm",
"billing"
],
"missing_from": [
"warehouse"
]
}
],
"dataset_count": 3,
"finding_count": 3,
"fully_covered": false,
"service_version": "1.0.0",
"findings_by_code": {
"KEY_IN_ONE_DATASET_ONLY": 2,
"KEY_MISSING_FROM_SOME_DATASETS": 1
},
"in_every_dataset": 1,
"partially_covered": 1,
"coverage_histogram": {
"1": 2,
"2": 1,
"3": 1
},
"distinct_key_count": 4,
"in_one_dataset_only": 2
}
}
}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, "key coverage audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-key-coverage-audit-5e1da1. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-key-coverage-audit-5e1da1-2026-10-13,
author = {TOLL},
title = {key coverage audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-key-coverage-audit-5e1da1}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.