failabsent from every registry#7 by calls of 15 on this host
0.22 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-04 21:22 UTC · method
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- — / 50% / 50%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:19 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.22 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 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.
On 2026-10-04 it did not answer at all; TOLL records that as a failure.
api.zfinia.com serves graphql schema compatibility, a POST endpoint that TOLL places in the "other" category, listed in neither registry at the last pull.
Per call, graphql schema compatibility declares 0.22 USDC on Base.
Its declared inputs are a json body with the fields after and before.
graphql schema compatibility returns json; the example shows limits, passed, complete, findings, compatible, request_id and 2 others.
graphql schema compatibility drew a single call from a single payer in the trailing 30 days.
The last call to graphql schema compatibility came 9 days before the snapshot, 2026-10-04.
With 15 endpoints listed on api.zfinia.com, graphql schema compatibility is tied 7th by calls with 9 others.
graphql schema compatibility takes 4% of the calls counted across api.zfinia.com.
Most comparable listings in the "other" category, 98%, ask less.
graphql schema compatibility sits nearest in price to intelligence address (api.arkm.com) and services vulnerability audit (www.cultos.dev) among listings in the "other" category.
The wallet paid by graphql schema compatibility is the payee of 179 endpoints across 5 hosts.
The seller's tags on graphql schema compatibility are graphql, breaking changes, api contracts and release gate.
graphql 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.
the payment options, as of 2026-10-04 21:22 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.22 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 13:07 UTC · methodendpoint answered HTTP none
endpoint_reachable· the endpoint answered at all
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 13:07 UTC | fail | 1 | daily-2026-10-04 |
| 2026-10-04 12:33 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 08:19 UTC · method
The input and output block
{
"input": {
"body": {
"after": "type Query {\n order(id: ID!, tenant: ID!): Order\n orders(first: Int = 50): [Order!]!\n}\n\ntype Mutation {\n createOrder(input: OrderInput!): Order!\n}\n\nenum Status { OPEN ARCHIVED }\n\ninput OrderInput {\n status: Status\n note: String\n tenant: ID!\n}\n\ntype Order {\n id: ID!\n status: Status!\n totalCents: Int\n channel: String!\n}\n",
"before": "type Query {\n order(id: ID!): Order\n orders(first: Int = 20): [Order!]!\n}\n\ntype Mutation {\n createOrder(input: OrderInput!): Order!\n}\n\nenum Status { OPEN CLOSED }\n\ninput OrderInput {\n status: Status\n note: String\n}\n\ntype Order {\n id: ID!\n status: Status!\n totalCents: Int!\n note: String\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": "REQUIRED_ARGUMENT_ADDED",
"type": "Query",
"field": "order",
"detail": "Query.order(tenant) is new, non-null and has no default, so every existing query on order stops validating.",
"argument": "tenant",
"audience": "clients"
},
{
"code": "ARGUMENT_DEFAULT_CHANGED",
"type": "Query",
"field": "orders",
"detail": "Query.orders(first) default went from 20 to 50, so a query that omits it gets a different answer without changing.",
"argument": "first",
"audience": "clients"
},
{
"code": "ENUM_VALUE_REMOVED",
"type": "Status",
"value": "CLOSED",
"detail": "Status.CLOSED is gone and Status is returned to clients, so a client with a case for CLOSED now receives a value it has no branch for, or none at all.",
"audience": "clients"
}
],
"compatible": false,
"request_id": "example-request",
"service_id": "graphql_schema_compatibility",
"assumptions": [
"Every finding names the audience it affects. A GraphQL schema is a contract in two directions: clients consume it and servers implement it, and the same edit breaks opposite audiences. Removing an out...",
"Nullability is directional. An output field made non-null is safe for clients and new work for servers; an input field made non-null is the reverse. Both are reported under the audience that bears the...",
"An enum value removed is attributed by where the enum actually flows, computed from the roots of the previous schema, because the same removal breaks clients when the enum is returned and callers when..."
],
"limitations": [
"The two SDL documents supplied, as a documented subset. Type extensions and directive definitions are recognised and listed as not compared, and no query document is validated.",
"compatible is true only when everything was compared and neither audience was affected. The two audience flags are published separately so a caller who only ships clients can read theirs."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 9,
"service_version": "1.0.0",
"after_type_count": 5,
"findings_by_code": {
"FIELD_ADDED": 1,
"FIELD_REMOVED": 1,
"ENUM_VALUE_REMOVED": 1,
"REQUIRED_ARGUMENT_ADDED": 1,
"ARGUMENT_DEFAULT_CHANGED": 1,
"ENUM_VALUE_ADDED_TO_OUTPUT": 1,
"OUTPUT_FIELD_MADE_NULLABLE": 1,
"REQUIRED_INPUT_FIELD_ADDED": 1,
"ENUM_VALUE_REMOVED_FROM_INPUT": 1
},
"before_type_count": 5,
"clients_unaffected": false,
"servers_unaffected": false,
"client_finding_count": 7,
"server_finding_count": 2
}
}
}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, "graphql schema compatibility on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-graphql-schema-compatibility-6d9e94. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-graphql-schema-compatibility-6d9e94-2026-10-13,
author = {TOLL},
title = {graphql schema compatibility on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-graphql-schema-compatibility-6d9e94}},
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.