Avro Compatibility
Decide whether two Avro schemas are compatible, in both directions, under the resolution rules rather than by structural comparison. Backward is a reader on the new schema reading data already written with the old one; forward is a reader still on the old schema reading data written with the new one. Fields match by name with reader aliases consulted, int promotes to long, float and double one way only, and an enum symbol the reader lacks needs an enum default.
Dataofflineeip155:8453Exactvia cdp
AvroSchema evolutionKafkaContract testingRelease gate
Settlements · 30d
219↓ 44%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$25.35
Verified settled volume
256 settlements proven x402 by their on-chain EIP-3009 marker.
$0.220
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-10-04 08:19Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x25e8245f07d5e4873987293dad666afbe56a9608The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Provider
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.
0.22USDC≈ $0.22 USD
on Base · exact scheme
Pay 0.22 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
- 220000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "220000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"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
}
}
},
"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": [
"before",
"after"
],
"properties": {
"after": {
"type": [
"object",
"string"
]
},
"before": {
"type": [
"object",
"string"
]
}
},
"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:19Z
- Last indexed by Roundhouse
- 2026-10-05 00:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-05 00:46Z
- 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 Avro Compatibility 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=Avro%20Compatibility' 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/avro-schema-compatibility, 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.