GraphQL Client Impact
Decide which named consumers a GraphQL schema change affects. Each consumer declares the parts of the schema it depends on, as Type.field and Type.field(argument), and the response says per consumer whether it is affected and exactly which dependency broke. A declared dependency the previous schema does not define is reported as not compared, not as unaffected. A new required input field is reported once against the schema, since it affects every consumer sending that input.
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.2 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
- 200000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "200000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"after": "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 tenant: ID!\n}\n\ntype Order {\n id: ID!\n status: Status!\n totalCents: Int\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",
"consumers": [
{
"name": "mobile-app",
"arguments": [
"Query.order(id)"
],
"selections": [
"Order.id",
"Order.note",
"Order.totalCents"
]
},
{
"name": "reporting-job",
"selections": [
"Order.id",
"Order.status"
]
},
{
"name": "legacy-widget",
"selections": [
"Order.legacyField"
]
}
]
},
"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": "CONSUMER_SELECTION_REMOVED",
"detail": "mobile-app depends on Order.note and the field is gone, so its query stops validating.",
"consumer": "mobile-app",
"selection": "Order.note"
},
{
"code": "CONSUMER_SELECTION_MADE_NULLABLE",
"detail": "mobile-app depends on Order.totalCents, which was Int! and is now Int, so code that assumed a value must handle null.",
"consumer": "mobile-app",
"selection": "Order.totalCents"
},
{
"code": "REQUIRED_INPUT_FIELD_ADDED_AFFECTS_EVERY_CONSUMER",
"detail": "OrderInput.tenant is new, non-null and has no default, so every consumer sending OrderInput is rejected regardless of what it selects.",
"selection": "OrderInput.tenant"
}
],
"consumers": [
{
"affected": [
"Order.note",
"Order.totalCents"
],
"consumer": "mobile-app",
"unaffected": false,
"affected_count": 2,
"dependency_count": 4
},
{
"affected": [],
"consumer": "reporting-job",
"unaffected": true,
"affected_count": 0,
"dependency_count": 2
},
{
"affected": [],
"consumer": "legacy-widget",
"unaffected": true,
"affected_count": 0,
"dependency_count": 1
}
],
"compatible": false,
"request_id": "example-request",
"service_id": "graphql_client_impact_audit",
"assumptions": [
"A consumer declares the parts of the schema it depends on as Type.field and Type.field(argument). That is a dependency list rather than a query document, which keeps the input small and makes the answ...",
"A declared dependency the previous schema does not define is reported as not compared rather than as unaffected, because a caller wrong about their own dependency should hear that instead of a pass.",
"A new required input field affects every consumer that sends that input whatever it selects, so it is reported once against the schema rather than silently attributed to nobody."
],
"limitations": [
"The dependencies declared, against the two SDL documents supplied. A consumer that under-declares gets an answer about what it declared, and a query document is never parsed or validated here.",
"compatible is true only when every declared dependency was compared and none of them was affected."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"not_examined": [
"SELECTION_NOT_IN_BEFORE_SCHEMA: legacy-widget declares a dependency on Order.legacyField, which the previous schema does not define, so nothing was compared for it."
],
"finding_count": 3,
"consumer_count": 3,
"service_version": "1.0.0",
"findings_by_code": {
"CONSUMER_SELECTION_REMOVED": 1,
"CONSUMER_SELECTION_MADE_NULLABLE": 1,
"REQUIRED_INPUT_FIELD_ADDED_AFFECTS_EVERY_CONSUMER": 1
},
"affected_consumer_count": 1,
"unaffected_consumer_count": 2
}
}
},
"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",
"consumers"
],
"properties": {
"after": {
"type": "string",
"maxLength": 262144
},
"before": {
"type": "string",
"maxLength": 262144
},
"consumers": {
"type": "array",
"items": {
"type": "object",
"required": [
"name",
"selections"
],
"properties": {
"name": {
"type": "string",
"maxLength": 64
},
"arguments": {
"type": "array",
"items": {
"type": "string",
"maxLength": 256
},
"maxItems": 200,
"minItems": 1
},
"selections": {
"type": "array",
"items": {
"type": "string",
"maxLength": 256
},
"maxItems": 200,
"minItems": 1
}
},
"additionalProperties": false
},
"maxItems": 50,
"minItems": 1
}
},
"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:20Z
- Last indexed by Roundhouse
- 2026-10-05 00:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-05 02: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 GraphQL Client Impact 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=GraphQL%20Client%20Impact' 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/graphql-client-impact-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.