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

avro schema compatibility derived

api.zfinia.comOtherderived

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

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

0.22 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 13:00 UTC · method · sweep daily-2026-10-04
Uptime, 7 / 30 / 90 days
— / 100% / 100%
as of 2026-10-04 13:00 UTC · method · 0 of 0 in 7d, 2 of 2 in 30d, 2 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 08:19 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.22 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

Of api.zfinia.com's 15 listings, avro schema compatibility ranks tied 7th by calls with 9 others.

Callers of avro schema compatibility supply a json body with the fields after and before.

A response from avro schema compatibility, as declared, includes limits, passed, complete, findings, after_root, compatible and 2 others.

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

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

A call to avro schema compatibility costs 0.22 USDC on Base, as declared.

Of the calls counted across api.zfinia.com, avro schema compatibility takes 4%.

TOLL files avro schema compatibility under the "other" category: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.

avro schema compatibility answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.

Closest in price to avro schema compatibility within the "other" category: research newsfeed at win.oneshotagent.com and page speed test at api.strale.io.

avro schema compatibility is near the top of prices in the "other" category; 98% of comparable listings are cheaper.

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

The seller's tags on avro schema compatibility are avro, schema evolution, kafka and contract testing.

avro schema compatibility 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.22 USDCexact0x25e824…6a9608

Preflight checks at the last sweep

the checks, as of 2026-10-04 13:00 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 13:00 UTCpass0daily-2026-10-04
2026-10-04 12:27 UTCpass0new-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 08:19 UTC · method

The input and output block
{
  "input": {
    "body": {
      "after": {
        "name": "Order",
        "type": "record",
        "fields": [
          {
            "name": "order_id",
            "type": "string"
          },
          {
            "name": "total_cents",
            "type": "int"
          },
          {
            "name": "status",
            "type": {
              "name": "Status",
              "type": "enum",
              "symbols": [
                "OPEN"
              ]
            }
          },
          {
            "name": "note",
            "type": [
              "null",
              "string"
            ],
            "default": null
          },
          {
            "name": "channel",
            "type": "string"
          }
        ],
        "namespace": "shop.v1"
      },
      "before": {
        "name": "Order",
        "type": "record",
        "fields": [
          {
            "name": "order_id",
            "type": "string"
          },
          {
            "name": "total_cents",
            "type": "long"
          },
          {
            "name": "status",
            "type": {
              "name": "Status",
              "type": "enum",
              "symbols": [
                "OPEN",
                "CLOSED"
              ]
            }
          },
          {
            "name": "note",
            "type": [
              "null",
              "string"
            ],
            "default": null
          }
        ],
        "namespace": "shop.v1"
      }
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "limits": {
        "maxFindings": 500,
        "maxSdlBytes": 262144,
        "maxVersions": 25,
        "maxAvroBytes": 262144,
        "maxConsumers": 50,
        "maxProtoBytes": 262144,
        "maxPathsPerConsumer": 200
      },
      "passed": false,
      "complete": true,
      "findings": [
        {
          "code": "TYPE_NOT_PROMOTABLE",
          "detail": "Reading old data with the new schema: The writer writes long and the reader expects int, which is not a permitted promotion.",
          "location": ".total_cents",
          "direction": "backward"
        },
        {
          "code": "ENUM_SYMBOL_NOT_READABLE",
          "detail": "Reading old data with the new schema: The writer may write CLOSED and the reader has no such symbol and no enum default to fall back to.",
          "location": ".status",
          "direction": "backward"
        },
        {
          "code": "READER_FIELD_HAS_NO_DEFAULT",
          "detail": "Reading old data with the new schema: The reader expects channel, the writer does not write it, and it declares no default, so the reader cannot fill it.",
          "location": "(root).channel",
          "direction": "backward"
        }
      ],
      "after_root": "record shop.v1.Order",
      "compatible": false,
      "request_id": "example-request",
      "service_id": "avro_schema_compatibility",
      "assumptions": [
        "Backward means a reader on the new schema can read data already written with the old one. Forward means a reader still on the old schema can read data written with the new one. Both are reported, beca...",
        "Resolution follows the Avro rules rather than a structural comparison: fields match by name with the reader aliases consulted, int promotes to long, float and double one way only, a reader field absen...",
        "Nothing is fetched. No registry is consulted, so a subject name, a registered version or a registry-level compatibility setting plays no part."
      ],
      "before_root": "record shop.v1.Order",
      "limitations": [
        "Whether the resolution rules permit the pair of schemas supplied. Whether application code handles a defaulted field sensibly is outside this.",
        "compatible is true only when both directions resolve cleanly. The two directional flags are published separately so a caller enforcing only one can read it."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "not_examined": [],
      "finding_count": 3,
      "service_version": "1.0.0",
      "after_node_count": 8,
      "findings_by_code": {
        "TYPE_NOT_PROMOTABLE": 1,
        "ENUM_SYMBOL_NOT_READABLE": 1,
        "READER_FIELD_HAS_NO_DEFAULT": 1
      },
      "before_node_count": 7,
      "forward_compatible": true,
      "backward_compatible": false,
      "forward_finding_count": 0,
      "backward_finding_count": 3
    }
  }
}
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, "avro schema compatibility on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-avro-schema-compatibility-42a387. Accessed [access date].

BibTeX

@misc{toll-e-api-zfinia-com-x402-v1-avro-schema-compatibility-42a387-2026-10-13,
  author = {TOLL},
  title = {avro schema compatibility on api.zfinia.com},
  howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-avro-schema-compatibility-42a387}},
  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 avro 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 42a3872d567d63cfef1f8d6ad5518e637b6e0af54b4cb4cb33c1fa914b0aeeed from wallet 0x25e8245f07d5e4873987293dad666afbe56a9608

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

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