Field Coverage Audit
Find out which fields your real payloads actually populate. Across a batch of documents it reports, per location, how often it is present, how often it holds anything, and every type it appears as. A location that is a string in some documents and a number in others is named, which no schema check on a single payload would reveal.
Dataofflineeip155:8453Exactvia cdp
Field coverageData profilingJsonData qualityDeveloper tooling
Settlements · 30d
219↓ 38%
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.090
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 07:50Z
—
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.09USDC≈ $0.09 USD
on Base · exact scheme
Pay 0.09 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
- 90000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "90000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"documents": [
{
"id": "a",
"email": "a@example.com",
"profile": {
"phone": "+61400000000"
}
},
{
"id": "b",
"email": "",
"profile": {}
},
{
"id": 3,
"profile": {
"phone": null
}
}
],
"expect_pointers": [
"/id",
"/email",
"/profile/phone"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxLines": 2000,
"maxHeaders": 100,
"maxFindings": 500,
"maxPointers": 2000,
"maxTextBytes": 262144,
"maxBatchItems": 500,
"maxDocumentBytes": 262144
},
"passed": false,
"complete": true,
"coverage": [
{
"types": {
"string": 2
},
"pointer": "/email",
"present_in": 2,
"type_count": 1,
"populated_in": 1,
"presence_rate": 0.666667,
"population_rate": 0.333333
},
{
"types": {
"string": 2,
"integer": 1
},
"pointer": "/id",
"present_in": 3,
"type_count": 2,
"populated_in": 3,
"presence_rate": 1,
"population_rate": 1
},
{
"types": {
"object": 3
},
"pointer": "/profile",
"present_in": 3,
"type_count": 1,
"populated_in": 2,
"presence_rate": 1,
"population_rate": 0.666667
}
],
"findings": [
{
"code": "INCONSISTENT_TYPE",
"detail": "/id appears as string and integer across the batch, so a typed consumer cannot rely on it.",
"pointer": "/id"
},
{
"code": "INCONSISTENT_TYPE",
"detail": "/profile/phone appears as string and null across the batch, so a typed consumer cannot rely on it.",
"pointer": "/profile/phone"
},
{
"code": "EXPECTED_POINTER_PARTIAL",
"detail": "/email is present in only 2 of 3 documents.",
"pointer": "/email",
"present_in": 2
}
],
"request_id": "example-request",
"service_id": "json_field_coverage_audit",
"assumptions": [
"A location counts as present when it exists and as populated when it holds something. An empty string, an empty array and an empty object are present but not populated, and null is absent by default.",
"Rates are over the documents actually examined, which is reported separately from the number supplied."
],
"limitations": [
"Observed population across the batch supplied. Whether the batch represents real traffic is not knowable here.",
"passed is true only when every expectation held and every document was fully examined."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [],
"finding_count": 4,
"always_present": [
"/id",
"/profile"
],
"document_count": 3,
"never_populated": [],
"service_version": "1.0.0",
"findings_by_code": {
"INCONSISTENT_TYPE": 2,
"EXPECTED_POINTER_PARTIAL": 2
},
"distinct_pointer_count": 4,
"examined_document_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": [
"documents"
],
"properties": {
"documents": {
"type": "array",
"items": {},
"maxItems": 500,
"minItems": 1
},
"expect_pointers": {
"type": "array",
"items": {
"type": "string",
"maxLength": 512
},
"maxItems": 500,
"minItems": 1
},
"treat_null_as_absent": {
"type": "boolean"
}
},
"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 07:50Z
- Last indexed by Roundhouse
- 2026-10-05 00:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-04 11:16Z
- 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 Field Coverage Audit 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=Field%20Coverage%20Audit' 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/json-field-coverage-audit, 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.