TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-07 05:57 UTC
Sweep
daily-2026-10-06 · finished 2026-10-06 16:43 UTC
Listed
36,126

json schema compatibility derived

api.zfinia.comInferencederived

POST https://api.zfinia.com/x402/v1/json-schema-compatibility

passlisted in Coinbase#8 by calls of 27 on this host

0.15 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-07 05:57 UTC · method · pinnable

Validation state
pass
as of 2026-10-07 07:59 UTC · method · pinnable · sweep daily-2026-10-07
Uptime, 7 / 30 / 90 days
80% / 80% / 80%
as of 2026-10-07 07:59 UTC · method · pinnable · 4 of 5 in 7d, 4 of 5 in 30d, 4 of 5 in 90d
Calls, trailing 30 days
1
as of 2026-10-07 05:57 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-10-07 05:57 UTC · method · pinnable
Last called
2026-10-04 07:49 UTC
as of 2026-10-07 05:57 UTC · method · pinnable
First observed by TOLLderived
2026-10-04
as of 2026-10-04 12:19 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.15 USDC
as of 2026-10-07 05:57 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-10-07 05:57 UTC · method · pinnable

Counters

8 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 12,443 endpoints in Inference 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: 4,893 in the category are counted higher and 7,549 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 8 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

TOLL's first observation of json schema compatibility was 2026-10-04.

json schema compatibility, a POST endpoint on api.zfinia.com, appears in the Coinbase registry; TOLL's taxonomy puts it in inference.

On Base, json schema compatibility asks 0.15 USDC per call.

Requests carry a json body with the fields role, after and before.

json schema compatibility answered the sweep of 2026-10-07 with a valid 402, passing 4 of 5 sweeps since 2026-10-04.

A response from json schema compatibility, as declared, includes role, limits, complete, findings, compatible, request_id and 2 others.

api.zfinia.com lists 27 endpoints; json schema compatibility is tied 8th by calls with 19 others.

3% of the host's counted calls go to it.

json schema compatibility drew a single call from a single payer in the trailing 30 days.

The last call to json schema compatibility came 3 days before the snapshot, 2026-10-04.

Closest in price to json schema compatibility within inference: agent call at api.losbeto.xyz and llm pro at agent402.tools.

json schema compatibility is near the top of prices in inference; 99% of comparable listings are cheaper.

The wallet paid by json schema compatibility is the payee of 179 endpoints across 5 hosts.

The seller's tags on json schema compatibility are schema compatibility, breaking change, api contract and release safety.

Payment options as declared

the payment options, as of 2026-10-07 05:57 UTC · method · pinnable

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

Preflight checks at the last sweep

the checks, as of 2026-10-07 07:59 UTC · method · pinnableendpoint 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-07 07:59 UTCpass0daily-2026-10-07
2026-10-06 08:49 UTCpass0daily-2026-10-06
2026-10-05 08:02 UTCfail1daily-2026-10-05
2026-10-04 13:03 UTCpass0daily-2026-10-04
2026-10-04 12:30 UTCpass0new-after-daily-2026-10-04

Registry presence

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

  1. 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:49 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "role": "consumers",
      "after": {
        "type": "object",
        "required": [
          "id"
        ],
        "properties": {
          "id": {
            "type": "string"
          },
          "total": {
            "type": "number",
            "maximum": 100000
          },
          "status": {
            "enum": [
              "open",
              "closed",
              "disputed"
            ],
            "type": "string"
          }
        }
      },
      "before": {
        "type": "object",
        "required": [
          "id"
        ],
        "properties": {
          "id": {
            "type": "string"
          },
          "note": {
            "type": "string"
          },
          "total": {
            "type": "number",
            "maximum": 1000
          },
          "status": {
            "enum": [
              "open",
              "closed"
            ],
            "type": "string"
          }
        }
      }
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "role": "consumers",
      "limits": {
        "maxLines": 2000,
        "maxHeaders": 100,
        "maxFindings": 500,
        "maxPointers": 2000,
        "maxTextBytes": 262144,
        "maxBatchItems": 500,
        "maxDocumentBytes": 262144
      },
      "complete": true,
      "findings": [
        {
          "code": "ENUM_WIDENED",
          "added": [
            "disputed"
          ],
          "breaks": [
            "consumers"
          ],
          "detail": "1 value(s) were added, so a reader with an exhaustive switch may not handle them.",
          "pointer": "/status",
          "severity": "breaking"
        },
        {
          "to": 100000,
          "code": "BOUND_LOOSENED",
          "from": 1000,
          "breaks": [
            "consumers"
          ],
          "detail": "maximum moved from 1000 to 100000, so a reader may receive a value outside the old range.",
          "keyword": "maximum",
          "pointer": "/total/maximum",
          "severity": "risky"
        },
        {
          "code": "PROPERTY_REMOVED",
          "breaks": [
            "consumers"
          ],
          "detail": "note was declared and is now gone, so a reader expecting it will not find it.",
          "pointer": "/note",
          "property": "note",
          "severity": "breaking"
        }
      ],
      "compatible": false,
      "request_id": "example-request",
      "service_id": "json_schema_compatibility",
      "assumptions": [
        "producers are the clients that construct the payload and consumers are the clients that read it. A request body makes your clients producers; a response body makes them consumers.",
        "Whether one pattern accepts a subset of another is regex subsumption and is not decided here; such a change is reported unclassified.",
        "nullable true and a union with null are treated as the same constraint, so migrating between the two spellings is not a change."
      ],
      "by_audience": {
        "consumers": 3,
        "producers": 0
      },
      "by_severity": {
        "risky": 1,
        "breaking": 2,
        "compatible": 0,
        "unclassified": 0
      },
      "limitations": [
        "Schema-level reasoning only. Whether any real client actually relies on a field is not knowable from the schemas.",
        "A property removal is reported as breaking for readers because that is the conservative reading; the schemas cannot say whether anything still sent it."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "risky_count": 1,
      "not_examined": [],
      "finding_count": 3,
      "breaking_count": 2,
      "service_version": "1.0.0",
      "unclassified_count": 0
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-10-07 05:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "json schema compatibility on api.zfinia.com", snapshot of 2026-10-07 05:57 UTC. https://tollindex.com/e/api-zfinia-com-x402-v1-json-schema-compatibility-59219e/at/2026-10-07T05-57Z. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-json-schema-compatibility-59219e-2026-10-07T05-57Z,
  author = {TOLL},
  title = {json schema compatibility on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-json-schema-compatibility-59219e/at/2026-10-07T05-57Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 2026-10-07 05:57 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 schema compatibility, 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 59219ec7eeadf0cd9af67f4a47a7d3b985add6c3272ab81c1ca7bc5c6f46f67e from wallet 0x25e8245f07d5e4873987293dad666afbe56a9608

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

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