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

protobuf schema compatibility derived

api.zfinia.comIdentityderived

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

failabsent 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
fail
as of 2026-10-05 05:12 UTC · method · sweep daily-2026-10-05
Uptime, 7 / 30 / 90 days
— / 67% / 67%
as of 2026-10-05 05:12 UTC · method · 0 of 0 in 7d, 2 of 3 in 30d, 2 of 3 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 2,150 endpoints in Identity 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: 1,412 in the category are counted higher and 737 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

On 2026-10-05 it did not answer at all; TOLL records that as a failure.

At api.zfinia.com, protobuf schema compatibility takes POST requests, is listed in neither registry at the last pull, and falls under identity by TOLL's rules.

protobuf schema compatibility is priced at 0.22 USDC on Base.

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

protobuf schema compatibility returns json; the example shows limits, passed, complete, findings, compatible, request_id and 2 others.

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

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

Among the 15 endpoints on api.zfinia.com, protobuf schema compatibility is tied 7th by calls with 9 others.

protobuf schema compatibility takes 4% of the calls counted across api.zfinia.com.

Most comparable listings in identity, 95%, ask less.

protobuf schema compatibility sits nearest in price to sanctions check (api.strale.io) and reviews (www.cultos.dev) among listings in identity.

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

The seller's tags on protobuf schema compatibility are protobuf, grpc, wire compatibility and contract testing.

protobuf 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-05 05:12 UTC · methodendpoint answered HTTP none

  • endpoint_reachable · the endpoint answered at all

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-05 05:12 UTCfail1daily-2026-10-05
2026-10-04 12:55 UTCpass0daily-2026-10-04
2026-10-04 12:21 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": "syntax = \"proto3\";\npackage shop.v1;\n\nenum Status {\n  UNKNOWN = 0;\n  OPEN = 1;\n  CLOSED = 2;\n}\n\nmessage Order {\n  string order_id = 1;\n  uint64 total_cents = 2;\n  Status status = 3;\n  string tags = 4;\n  int32 discount_cents = 5;\n}\n",
      "before": "syntax = \"proto3\";\npackage shop.v1;\n\nenum Status {\n  STATUS_UNSPECIFIED = 0;\n  OPEN = 1;\n  CLOSED = 2;\n}\n\nmessage Order {\n  string order_id = 1;\n  int64 total_cents = 2;\n  Status status = 3;\n  repeated string tags = 4;\n  string note = 5;\n}\n"
    },
    "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": "VALUE_SEMANTICS_CHANGED",
          "field": "total_cents",
          "detail": "shop.v1.Order.total_cents = 2 went from int64 to uint64, which share the varint wire type, so old bytes decode without error and a value above the signed maximum reads as negative, or a negative value...",
          "number": 2,
          "message": "shop.v1.Order"
        },
        {
          "code": "CARDINALITY_CHANGED",
          "field": "tags",
          "detail": "shop.v1.Order.tags = 4 went from repeated to singular. The bytes still parse and the decoded shape changes, so a reader keeps only the last value or sees a one-element list.",
          "number": 4,
          "message": "shop.v1.Order"
        },
        {
          "code": "FIELD_RENAMED",
          "field": "discount_cents",
          "detail": "shop.v1.Order field 5 went from note to discount_cents. The wire format is unchanged because the number is the identity, and every generated accessor, JSON name and text-format name changes.",
          "number": 5,
          "message": "shop.v1.Order"
        }
      ],
      "compatible": false,
      "request_id": "example-request",
      "service_id": "protobuf_schema_compatibility",
      "assumptions": [
        "The field number is the identity, as protobuf defines it, and the name is not. A rename is therefore reported as wire-compatible and a source break, and reusing a number is reported as a silent reinte...",
        "Removing a field is only safe when the number cannot come back, so a removal without a matching reserved entry is a finding even though the removal itself parses.",
        "A type this file does not define, typically an imported one, is reported as not compared rather than assumed compatible. Services, extensions and groups are recognised and listed as not modelled."
      ],
      "limitations": [
        "The two .proto sources supplied, as a documented subset: messages, enums, fields, oneofs, maps and reserved ranges. Imports are recorded and not followed.",
        "compatible is true only when everything was compared and nothing changed in a way that affects a reader, a writer or generated code."
      ],
      "observed_at": "2026-10-02T00:00:00.000Z",
      "after_syntax": "proto3",
      "not_examined": [],
      "before_syntax": "proto3",
      "finding_count": 6,
      "service_version": "1.0.0",
      "after_enum_count": 1,
      "findings_by_code": {
        "FIELD_RENAMED": 1,
        "WIRE_TYPE_CHANGED": 1,
        "ENUM_VALUE_RENAMED": 1,
        "CARDINALITY_CHANGED": 1,
        "ENUM_ZERO_VALUE_CHANGED": 1,
        "VALUE_SEMANTICS_CHANGED": 1
      },
      "before_enum_count": 1,
      "after_message_count": 1,
      "before_message_count": 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, "protobuf schema compatibility on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-protobuf-schema-compatibility-01ef3b. Accessed [access date].

BibTeX

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

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

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