passabsent from every registry#6 by calls of 15 on this host
0.1 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.1 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.
duplicate key audit shares api.zfinia.com with 14 other listed endpoints and is tied 6th by calls with 10 others.
Callers of duplicate key audit supply a json body with the fields csv, key and normalise.
A response from duplicate key audit, as declared, includes limits, passed, unique, complete, findings, row_count and 2 others.
duplicate key audit drew a single call from a single payer in the trailing 30 days.
The last call to duplicate key audit came 28 days before the snapshot, 2026-10-04.
The declared price is 0.1 USDC on Base.
duplicate key audit takes 3% of the calls counted across api.zfinia.com.
TOLL files duplicate key audit under search: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
duplicate key audit answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to duplicate key audit within search: lookup person posts at win.oneshotagent.com and fullenrich people search at stableenrich.dev.
duplicate key audit is near the top of prices in search; 94% of comparable listings are cheaper.
The wallet paid by duplicate key audit is the payee of 179 endpoints across 5 hosts.
The seller's tags on duplicate key audit are data quality, duplicates, keys and pipeline gate.
duplicate key 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.
The price of duplicate key audit is declared by 41 other listings in search too.
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.1 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 13:11 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:11 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:39 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:09 UTC · method
The input and output block
{
"input": {
"body": {
"csv": "email,signed_up\nAda@Example.test,2026-01-01\nada@example.test,2026-02-01\nada@example.test ,2026-03-01\ngrace@example.test,2026-01-05\ngrace@example.test,2026-04-01\n",
"key": [
"email"
],
"normalise": [
"lowercase",
"trim"
]
},
"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,
"unique": false,
"complete": true,
"findings": [
{
"key": "grace@example.test",
"row": 5,
"code": "DUPLICATE_KEY",
"detail": "grace@example.test appears 2 times, at rows 5, 6."
},
{
"key": "ada@example.test",
"row": 2,
"code": "NEAR_DUPLICATE_KEY",
"detail": "3 different keys become ada@example.test once lowercase and trim is applied, which a unique index would have accepted and is usually the same entity twice."
}
],
"row_count": 5,
"duplicates": [
{
"key": "grace@example.test",
"rows": [
5,
6
],
"occurrences": 2
}
],
"request_id": "example-request",
"service_id": "duplicate_key_audit",
"assumptions": [
"Keys are canonicalised exactly, so 1.0 and 1 are one key and a large identifier is compared as text rather than collapsed.",
"A near duplicate is two different keys that become identical once the requested normalisation is applied. It is reported separately from an exact duplicate, because a unique index would have accepted ..."
],
"limitations": [
"Uniqueness within the dataset supplied. A duplicate against another dataset is not visible here.",
"unique is true only when the dataset was fully read and no key repeated exactly or near-identically."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 2,
"empty_key_count": 0,
"near_duplicates": [
{
"rows": [
2,
3,
4
],
"normalised_key": "ada@example.test",
"distinct_exact_keys": 3
}
],
"service_version": "1.0.0",
"findings_by_code": {
"DUPLICATE_KEY": 1,
"NEAR_DUPLICATE_KEY": 1
},
"distinct_key_count": 4,
"supplied_row_count": 5,
"duplicate_key_count": 1,
"duplicate_row_count": 1,
"near_duplicate_count": 1,
"normalisation_applied": [
"lowercase",
"trim"
]
}
}
}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, "duplicate key audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-duplicate-key-audit-8d0f70. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-duplicate-key-audit-8d0f70-2026-11-01,
author = {TOLL},
title = {duplicate key audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-duplicate-key-audit-8d0f70}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-01 05:59 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.