Cross-Format Crosscheck
Compare one logical record declared in two or three of Avro, protobuf and GraphQL, and report where the representations disagree. Names are matched with case and underscores set aside, since snake_case and camelCase across these formats is convention rather than disagreement. Reports a field present in one format and not another, a type class mismatch, disagreeing optionality or repeatedness, and enum symbol sets that differ.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.25 USDC on Base to 0x25e8…a9608. The signed payment is good for 1 minute.
- Paid to
- 0x25e8…a9608
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 250000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "250000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"avro": {
"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"
},
"graphql": "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",
"protobuf": "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",
"record_name": "Order"
},
"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": false,
"findings": [
{
"code": "FIELD_ABSENT_FROM_FORMAT",
"field": "id",
"detail": "id is declared in graphql and not in avro or protobuf, so the two representations of the same record do not carry the same data."
},
{
"code": "FIELD_ABSENT_FROM_FORMAT",
"field": "order_id",
"detail": "order_id is declared in avro and protobuf and not in graphql, so the two representations of the same record do not carry the same data."
},
{
"code": "OPTIONALITY_DISAGREES",
"field": "status",
"detail": "status is required in avro and optional in protobuf, so one side accepts a record the other rejects."
}
],
"consistent": false,
"request_id": "example-request",
"service_id": "cross_format_record_crosscheck",
"assumptions": [
"Field names are compared with case and underscores set aside, because snake_case in protobuf and camelCase in GraphQL is the convention rather than a disagreement. The convention difference is noted i...",
"Types are compared by class - integer, binary float, text, binary, boolean, enum, named - rather than by exact type, because int64 and Int are the same intent while double and a decimal are not.",
"Optionality in proto3 is read from the schema as written: a singular field has implicit presence and is reported as optional, which is a real difference from a GraphQL non-null field and not an artefa..."
],
"limitations": [
"One record in each supplied document. Nested records are not followed, so a disagreement inside a nested type is outside this.",
"consistent is true only when every supplied document was compared and the fields agreed on presence, class, repeatedness, optionality and enum symbols."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"field_counts": [
{
"fields": 4,
"format": "avro"
},
{
"fields": 5,
"format": "protobuf"
},
{
"fields": 4,
"format": "graphql"
}
],
"not_examined": [
"NAMING_CONVENTIONS_DIFFER: The documents use different field naming conventions (camelCase and snake_case), which is normal across these formats. Names are therefore compared with case and underscores..."
],
"record_names": [
{
"name": "shop.v1.Order",
"format": "avro"
},
{
"name": "shop.v1.Order",
"format": "protobuf"
},
{
"name": "Order",
"format": "graphql"
}
],
"finding_count": 6,
"service_version": "1.0.0",
"findings_by_code": {
"ENUM_SYMBOLS_DISAGREE": 1,
"OPTIONALITY_DISAGREES": 2,
"FIELD_ABSENT_FROM_FORMAT": 3
},
"formats_compared": [
"avro",
"protobuf",
"graphql"
],
"distinct_field_count": 6
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [],
"properties": {
"avro": {
"type": [
"object",
"string"
]
},
"graphql": {
"type": "string",
"maxLength": 262144
},
"protobuf": {
"type": "string",
"maxLength": 262144
},
"record_name": {
"type": "string",
"maxLength": 256
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-04 08:18Z
- Last indexed by Roundhouse
- 2026-10-05 00:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-05 10:45Z
- x402 version
- 2
- Max timeout
- 60s
- Liveness probe
- HTTP 0
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Cross-Format Crosscheck and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Cross-Format%20Crosscheck' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.zfinia.com/x402/v1/cross-format-record-crosscheck, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.