TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
32,435

json object reconciliation derived

api.zfinia.comOtherderived

POST https://api.zfinia.com/x402/v1/json-object-reconciliation

passabsent from every registry#7 by calls of 15 on this host

0.18 USDC

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

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-04 21:22 UTC · method

Validation state
pass
as of 2026-10-04 12:56 UTC · method · sweep daily-2026-10-04
Uptime, 7 / 30 / 90 days
— / 50% / 50%
as of 2026-10-04 12:56 UTC · method · 0 of 0 in 7d, 1 of 2 in 30d, 1 of 2 in 90d
Calls, trailing 30 days
1
as of 2026-10-04 21:22 UTC · method
Unique payers, trailing 30 days
1
as of 2026-10-04 21:22 UTC · method
Last called
2026-10-04 07:51 UTC
as of 2026-10-04 21:22 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.18 USDC
as of 2026-10-04 21:22 UTC · method · on eip155:8453
Networks
1
as of 2026-10-04 21:22 UTC · method

Counters

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

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 3,825 endpoints in Other 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: 2,938 in the category are counted higher and 886 lower.

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.

In words

Among the 15 endpoints on api.zfinia.com, json object reconciliation is tied 7th by calls with 9 others.

json object reconciliation takes a json body with the fields left, right and key_pointers.

A response from json object reconciliation, as declared, includes limits, passed, complete, findings, reconciled, request_id and 2 others.

json object reconciliation drew a single call from a single payer in the trailing 30 days.

The last call to json object reconciliation came 9 days before the snapshot, 2026-10-04.

Each call is priced at 0.18 USDC, payable on Base.

json object reconciliation takes 4% of the calls counted across api.zfinia.com.

api.zfinia.com serves json object reconciliation, a POST endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.

json object reconciliation answered the sweep of 2026-10-04 with a valid 402, passing 1 of 2 sweeps since 2026-10-04.

Closest in price to json object reconciliation within the "other" category: tiers prototype at api.run402.com and research newsfeed at win.oneshotagent.com.

json object reconciliation is near the top of prices in the "other" category; 98% of comparable listings are cheaper.

The wallet paid by json object reconciliation is the payee of 179 endpoints across 5 hosts.

Seller tags: reconciliation, json, data quality and join integrity.

json object reconciliation 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.

Payment options as declared

the payment options, as of 2026-10-04 21:22 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.18 USDCexact0x25e824…6a9608

Preflight checks at the last sweep

the checks, as of 2026-10-04 12:56 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, UTCstatefailed checkssweep
2026-10-04 12:56 UTCpass0daily-2026-10-04
2026-10-04 12:22 UTCfail1new-after-daily-2026-10-04

Registry presence

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

  1. absence from Coinbase confirmed, rule v1
  2. absent from Coinbase at this pull
  3. listed 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:51 UTC · method

The input and output block
{
  "input": {
    "body": {
      "left": [
        {
          "id": "o-1",
          "total": 42.5,
          "labels": [
            "a",
            "b"
          ],
          "status": "shipped"
        },
        {
          "id": "o-2",
          "total": 19.99,
          "labels": [],
          "status": "pending"
        },
        {
          "id": "o-3",
          "total": 7,
          "labels": [],
          "status": "shipped"
        }
      ],
      "right": [
        {
          "id": "o-1",
          "total": 42.5,
          "labels": [
            "b",
            "a"
          ],
          "status": "shipped"
        },
        {
          "id": "o-2",
          "total": 19.99,
          "labels": [],
          "status": "PENDING"
        },
        {
          "id": "o-4",
          "total": 3,
          "labels": [],
          "status": "shipped"
        }
      ],
      "key_pointers": [
        "/id"
      ]
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "limits": {
        "maxLines": 2000,
        "maxHeaders": 100,
        "maxFindings": 500,
        "maxPointers": 2000,
        "maxTextBytes": 262144,
        "maxBatchItems": 500,
        "maxDocumentBytes": 262144
      },
      "passed": false,
      "complete": true,
      "findings": [
        {
          "key": "o-2",
          "code": "RECORD_DIFFERS",
          "detail": "Key o-2: 1 difference(s) between the two records.",
          "changes": [
            {
              "to": "PENDING",
              "code": "VALUE_CHANGED",
              "from": "pending",
              "pointer": "/status"
            }
          ]
        },
        {
          "key": "o-3",
          "code": "ONLY_IN_LEFT",
          "detail": "Key o-3 is present on the left and absent on the right."
        },
        {
          "key": "o-4",
          "code": "ONLY_IN_RIGHT",
          "detail": "Key o-4 is present on the right and absent on the left."
        }
      ],
      "reconciled": false,
      "request_id": "example-request",
      "service_id": "json_object_reconciliation",
      "assumptions": [
        "Records are joined on the values at key_pointers. A record missing part of its key is reported unjoined rather than grouped with other keyless records.",
        "A key appearing more than once on a side is reported as a duplicate rather than compared, because there is no single record to compare against.",
        "Arrays inside records are compared as multisets by default, since element order in a record is rarely meaningful."
      ],
      "limitations": [
        "Agreement between the two sets only. Which side is correct is not assessed.",
        "reconciled is true only when every record was joined and compared and nothing differed."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "key_pointers": [
        "/id"
      ],
      "not_examined": [],
      "finding_count": 3,
      "service_version": "1.0.0",
      "array_comparison": "multiset",
      "findings_by_code": {
        "ONLY_IN_LEFT": 1,
        "ONLY_IN_RIGHT": 1,
        "RECORD_DIFFERS": 1
      },
      "left_keyed_count": 3,
      "compared_pointers": null,
      "left_record_count": 3,
      "matched_key_count": 2,
      "right_keyed_count": 3,
      "only_in_left_count": 1,
      "right_record_count": 3,
      "only_in_right_count": 1,
      "duplicated_key_left_count": 0,
      "duplicated_key_right_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, "json object reconciliation on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-json-object-reconciliation-15386c. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-json-object-reconciliation-15386c-2026-10-13,
  author = {TOLL},
  title = {json object reconciliation on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-json-object-reconciliation-15386c}},
  year = {2026},
  month = {10},
  note = {Frozen at its last observation, 2026-10-13 14:08 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 json object reconciliation, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 15386ca77bb27a9792c671e0edc1a8afa9cc2df5dc3a397c72b4bff9e4a7bb9f from wallet 0x25e8245f07d5e4873987293dad666afbe56a9608

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.