passabsent from every registry#1 by calls of 15 on this host
0.003 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-23 21:29 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / — / 100%
- Calls, trailing 30 days
- 6
- Unique payers, trailing 30 days
- 5
- Last called
- 2026-09-19 15:58 UTC
- First observed by TOLLderived
- 2026-09-19
- Pricederived
- 0.003 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 16 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.
Among the 15 endpoints on api.zfinia.com, data compatibility checker is 1st by calls.
data compatibility checker takes a json body with the fields source_fields, target_fields, comparison_mode, canonicalization and contract_version.
A response from data compatibility checker, as declared, includes issues, compatible, request_id, service_id, assumptions, issue_count and 2 others.
The registry's counters give data compatibility checker 6 calls and 5 unique payers over 30 days.
The most recent call was 24 days before the snapshot.
data compatibility checker is priced at 0.003 USDC on Base.
Of the calls counted across api.zfinia.com, data compatibility checker takes 22%.
api.zfinia.com serves data compatibility checker, a POST endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.
data compatibility checker answered the sweep of 2026-09-23 with a valid 402, as at every sweep since 2026-09-20.
Closest in price to data compatibility checker within the "other" category: stats at uptime.cyberwarex.com and enrich profile at win.oneshotagent.com.
data compatibility checker is priced above 20% of comparable listings in the "other" category.
data compatibility checker out-counts 92% of the 3,825 endpoints in the "other" category that carry counters.
The wallet paid by data compatibility checker is the payee of 179 endpoints across 5 hosts.
data compatibility checker was missing from the Coinbase registry at the pull of 2026-09-24, confirmed at the pull of 2026-09-24; that is registry presence, not liveness.
The price of data compatibility checker is declared by 264 other listings in the "other" category 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-09-23 21:29 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-09-23 05:23 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-23 05:23 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 05:33 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 05:56 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-20 18:36 UTC | pass | 0 | daily-2026-09-20 |
| 2026-09-20 18:19 UTC | pass | 0 | new-after-daily-2026-09-19 |
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-09-19 15:58 UTC · method
The input and output block
{
"input": {
"body": {
"source_fields": [
{
"name": "id",
"type": "string",
"nullable": false,
"required": true
}
],
"target_fields": [
{
"name": "id",
"type": "string",
"nullable": false,
"required": true
}
],
"comparison_mode": "backward_compatible",
"canonicalization": "exact",
"contract_version": "1"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"issues": [],
"compatible": true,
"request_id": "example-request",
"service_id": "data_compatibility_checker",
"assumptions": [
"Source fields represent data offered by the caller; target fields represent the receiving contract."
],
"issue_count": 0,
"limitations": [
"Structural field compatibility only; values, nested object shapes, semantic meaning, API behavior, and agent-output quality are not inspected."
],
"remediations": [],
"comparison_mode": "backward_compatible",
"service_version": "1.0.0",
"canonicalization": {
"field_names": "exact",
"changed_names": []
},
"contract_version": "1",
"checked_source_fields": 1,
"checked_target_fields": 1
}
}
}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, "data compatibility checker on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-data-compatibility-checker-0d753d. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-data-compatibility-checker-0d753d-2026-10-13,
author = {TOLL},
title = {data compatibility checker on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-data-compatibility-checker-0d753d}},
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.