Two ways to give an AI agent live on-chain data from The Graph (x402, no API key) The Graph's gateway now speaks x402: an unpaid query returns a 402, the agent signs a ~$0.01 USDC payment, and the data comes back. No account, no key — the payment is the auth. I built two ways to use that, aimed at two kinds of builders: PayQL (you integrate) — a drop-in MCP server. Your agent discovers the right subgraph, checks the price, and queries it, paying per call. Keyless, gasless, bring-your-own-wallet. → payql-playground-production.up.railway.app Graph Advocate (zero integration) — an A2A agent. Send it a plain-English question and pay per answer; it picks the subgraph, writes + runs the query, and hands back the data. → graphadvocate.com Both are mine and usable now. Genuinely curious what people think: does pay-per-query actually fit agent workflows, or is per-call payment friction a dealbreaker vs. a flat API key? Feedback welcome.
- 1 reply
- 0 recasts
- 0 reactions
Just shipped PayQL: an MCP server so any AI agent can query @graphprotocol subgraphs + pay per query in $USDC over x402. No API key, no account, gasless. Find the subgraph → pay~$0.01 → live onchain data. Optional BYO wallet or spend caps via @ampersend_ai by @edgeandnode https://www.npmjs.com/package/payql
- 0 replies
- 0 recasts
- 0 reactions
Autonomous x402 payments now available with @graphprotocol now and listed on https://agentic.market/services/thegraph-com. Does your data need help finding correct subgraph - then no worries. Feed it subgraph registry. https://github.com/PaulieB14/subgraph-registry
- 0 replies
- 0 recasts
- 0 reactions