passabsent from every registry#7 by calls of 15 on this host
0.2 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-05 05:36 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 67% / 67%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 07:49 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.2 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 3 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, dataset reconciliation ranks tied 7th by calls with 9 others.
dataset reconciliation takes a json body with the fields key, left and right.
A response from dataset reconciliation, as declared, includes left, right, limits, complete, warnings, comparison and 2 others.
dataset reconciliation drew a single call from a single payer in the trailing 30 days.
The last call to dataset reconciliation came 9 days before the snapshot, 2026-10-04.
Each call is priced at 0.2 USDC, payable on Base.
dataset reconciliation takes 4% of the calls counted across api.zfinia.com.
At api.zfinia.com, dataset reconciliation takes POST requests, is listed in neither registry at the last pull, and falls under inference by TOLL's rules.
dataset reconciliation answered the sweep of 2026-10-05 with a valid 402, passing 2 of 3 sweeps since 2026-10-04.
Closest in price to dataset reconciliation within inference: profiles search at api.linkedpanda.com and agent call at api.losbeto.xyz.
dataset reconciliation is near the top of prices in inference; 99% of comparable listings are cheaper.
The wallet paid by dataset reconciliation is the payee of 179 endpoints across 5 hosts.
The seller's tags on dataset reconciliation are reconciliation, data diff, join integrity and data quality.
dataset reconciliation was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-06; 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-05 05:36 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.2 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-05 09:20 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-05 09:20 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:10 UTC | fail | 1 | daily-2026-10-04 |
| 2026-10-04 12:38 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 07:49 UTC · method
The input and output block
{
"input": {
"body": {
"key": [
{
"left": "order_id",
"right": "orderId"
}
],
"left": {
"csv": "order_id,amount,status\n1001,42.50,shipped\n1002,19.99,pending\n1003,7.00,shipped\n",
"name": "source_export"
},
"right": {
"csv": "orderId,amount,status\n1001,42.5,shipped\n1002,19.99,PENDING\n1004,3.00,shipped\n",
"name": "warehouse"
}
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"left": {
"name": "source_export",
"read_row_count": 3,
"joinable_key_count": 3,
"supplied_row_count": 3,
"empty_key_row_count": 0,
"duplicated_key_count": 0
},
"right": {
"name": "warehouse",
"read_row_count": 3,
"joinable_key_count": 3,
"supplied_row_count": 3,
"empty_key_row_count": 0,
"duplicated_key_count": 0
},
"limits": {
"maxColumns": 64,
"maxCsvBytes": 262144,
"maxCellLength": 4096,
"maxKeyColumns": 4,
"maxListedKeys": 200,
"maxRowsPerSide": 5000,
"maxNumericExponent": 6000,
"maxListedDifferences": 500,
"maxSignificantDigits": 50
},
"complete": true,
"warnings": [],
"comparison": {
"numeric": "exact",
"duplicate_keys": "multiset",
"numeric_tolerance": "0",
"max_numeric_exponent": 6000,
"max_significant_digits": 50
},
"reconciled": false,
"request_id": "example-request",
"service_id": "dataset_reconciliation",
"assumptions": [
"Equality is decided exactly on the decimal text, never through floating point, so 42.50 and 42.5 agree while 9007199254740992 and 9007199254740993 do not.",
"Values are otherwise compared as the text supplied. No locale, thousands separator or ambiguous date order is inferred.",
"An empty key column makes a row unjoinable rather than grouping it with other empty keys, because that would invent matches."
],
"cardinality": "1:1",
"differences": [
{
"key": "1002",
"column": "status",
"left_row": 3,
"right_row": 3,
"left_value": "pending",
"right_value": "PENDING",
"right_column": null,
"numeric_delta": null,
"numeric_delta_text": null
}
],
"key_columns": [
{
"left": "order_id",
"right": "orderId"
}
],
"limitations": [
"Join integrity and field-level agreement only. Which side is correct, why they disagree, and whether the key is the right key are not assessed.",
"Row, column, cell and listing bounds are applied as the sides are read. Anything left unexamined is named in not_examined, and reconciled is false whenever complete is false.",
"Exact numeric comparison holds within the declared envelope of significant digits and exponent. A value outside it is counted in not_comparable_count and reported unexamined rather than compared."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"only_in_left": [
{
"key": "1003",
"rows": [
4
]
}
],
"only_in_right": [
{
"key": "1004",
"rows": [
4
]
}
],
"service_version": "1.0.0",
"compared_columns": [
{
"left": "amount",
"right": "amount"
},
{
"left": "status",
"right": "status"
}
],
"difference_count": 1,
"matched_key_count": 2,
"only_in_left_count": 1,
"ambiguous_key_count": 0,
"only_in_right_count": 1,
"not_comparable_count": 0,
"differences_by_column": {
"status": 1
},
"matched_row_pair_count": 2,
"multiset_matched_key_count": 0
}
}
}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, "dataset reconciliation on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-dataset-reconciliation-83199e. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-dataset-reconciliation-83199e-2026-10-13,
author = {TOLL},
title = {dataset reconciliation on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-dataset-reconciliation-83199e}},
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.