https://preview.redd.it/an7i46opx50h1.png?width=680&format=png&auto=webp&s=d5c52f7757ac1cd986643ba096685468013f9416

No API key. No signup. The wallet does the auth.

The Graph's x402 gateway is live in production. Pay-per-query subgraph access, settled in USDC on Base, with no account required. Pair it with discovery tooling and an AI agent can go from a natural-language question to onchain data in two steps.

🛠 What's new: x402 gateway in production

gateway.thegraph.com/api/x402/subgraphs/id/{id} accepts pay-per-query access via the x402 protocol.

The official docs frame the use case plainly: x402 is for "autonomous agents and short-lived processes that can't store long-term credentials" and "per-query workloads where pre-purchased credits don't fit the access pattern."

That's exactly the agent shape, and it's now a first-class access pattern on the gateway.

🧭 Pairing it with discovery

x402 handles payment. Discovery — "which of 15K subgraphs do I even hit?" — is what I've been building

subgraph-registry-mcpfor. It's my own project, not a Graph product. It classifies the registry by domain / network / protocol-type and exposes a recommend_subgraph tool that agents can call directly.

The registry SQLite blob is hash-pinned against a SHA-256 baked into the npm package, so agents can verify integrity before loading.

The two pieces compose. Together, the agent workflow runs in two steps.

⚡ The combined workflow

markdown

Agent: "Best subgraph for Uniswap V3 on Arbitrum?"

Step 1 — discovery (no key, no payment):
  call subgraph-registry-mcp.recommend_subgraph
  → returns id=HMuAwufqZ1YCRmzL2SfHTVkzZovC9VL2UAKhjvRqKiR1
    + reliability score + suggested entities

Step 2 — execute (no key, $0.01 USDC):
  POST gateway.thegraph.com/api/x402/subgraphs/id/HMuAwufqZ1...
       { query: "{ _meta { block { number } } }" }
  → 402 + payment-required header
  → client signs EIP-3009 transferWithAuthorization for $0.01 USDC on Base
  → re-POST with Payment-Signature header
  → 200 + GraphQL data

No API key. No signup form. No paid plan.

The wallet does the auth.

🧾 Live receipt

I ran the flow against the gateway, paying $0.01 USDC from a Base wallet, and got back:

json

{ "_meta": { "block": { "number": 45743214, "timestamp": 1778275775 } } }

Real subgraph data. Real onchain settlement. Total wall-clock ~3 seconds. The settlement reference lives in the response's x-payment-response header, auditable on Base.

From code, it's about as much ceremony as a normal fetch:

json

import { createGraphQuery } from '@graphprotocol/client-x402'

const query = createGraphQuery({
  endpoint: 'https://gateway.thegraph.com/api/x402/subgraphs/id/HMuAwufqZ1YCRmzL2SfHTVkzZovC9VL2UAKhjvRqKiR1',
  chain: 'base',
})
const result = await query('{ tokens(first: 5) { symbol } }')

The client handles the 402 → sign → resend dance. Your code only sees the data.

🚀 What this unlocks

Pay-per-query is the foundation. The interesting layer is what gets built on top of it:

• An autonomous wallet-profiling agent can query 50 protocols' subgraphs in a session for ~$0.50 — settled per-call, no monthly minimums.
• A trading agent doing pre-trade research pays only for the queries it actually runs.
• Agent-priced products become composable end-to-end. The upstream subgraph cost is now itself x402, so margins are calculable from query to user.

Agents that operate on metered USDC — discovery free, execution paid — are a different shape of consumer than humans on monthly plans, and the infrastructure for them is now here.

🛑 When to use which

x402 is for the agent-shaped slice of the workload: short-lived processes, per-query economics, no long-term credentials.

For sustained, high-volume application use, the existing API-key flow is the right shape — bulk pricing, no per-call signing overhead, established billing flow.

Two access patterns. Two payment shapes. Same data.

📚 Further reading

• Official x402 docs on The Graph — endpoints, USDC token addresses, SDK options
• u/graphprotocol/client-x402 on npm
• x402 protocol spec
• subgraph-registry-mcp on npm — my discovery layer—u/PaulieB14, operator of graphadvocate.com (ERC-8004 #734) and subgraph-registry-mcp

Big drop from Pinax Network today. Hyperliquid joins EVM and Solana as a top-level data domain on the Token API, with full HyperCore order-flow coverage. If you're building anything against HL data, this is a serious step up.

---

🟢 What's new with Hyperliquid

The new /v1/hyperliquid/* family covers core perps, spot pairs (@N), and builder-deployed DEXs (<dex>:<symbol>) under one consistent coin parameter.

Grouped into four areas:

📊 Markets

Discover markets, pull candles, open interest, the full trade-fill stream, and liquidation history.

• /dexes
• /markets
• /markets/ohlc
• /markets/oi
• /markets/activity
• /markets/liquidations
• /markets/liquidations/ohlc

👤 Users

Per-trader stats (volume, fees, realized PnL, funding, liquidations) in profile mode (one address) or leaderboard mode (top traders), plus a unified balance-event feed across bridge deposits, withdrawals, vault flows, liquidations, and funding payments.

• /users
• /users/positions
• /users/activity

🏦 Vaults

Lifetime deposit / withdrawal / distribution stats per vault and per depositor.

• /vaults
• /vaults/depositors

🌐 Platform

Cross-market, cross-DEX time series of platform-wide volume, fees, trade counts, and liquidations.

• /platform

> New builder DEXs auto-appear via /v1/hyperliquid/dexes — no API release needed on Pinax's side when new ones launch.

---

🚀 The bullish part

Market discovery (/dexes and /markets) is free and unauthenticated. You can build a Hyperliquid market browser without provisioning a key. That's a low floor for anyone wanting to ship.

---

🛠 Other wins in v3.17.0

• 🐛 Fixed an OHLC duplicate-row bug on /v1/evm/pools/ohlc and /v1/tvm/pools/ohlc. Un-merged historical token-metadata versions were multiplying candles. Confirmed end-to-end on USDC/WETH mainnet.
• ☀️ 5 new Solana DEXs in protocol filters on /v1/svm/swaps and /v1/svm/pools: meteora_daam, meteora_amm, byreal, moonshot, pancakeswap.
• 🤖 AI-agent-ready docs: /llms.txt (llms.txt convention), /SKILLS.md (table-driven endpoint catalog by domain), and /openapi is now self-documented. Coding agents can discover capabilities without scraping HTML.

---

🔭 The bigger picture

EVM. Solana. TVM. Polymarket. And now Hyperliquid — all behind one API surface, with a docs layer designed for LLMs and agents to consume directly.

The data graph keeps widening.

---

📖 Full release notes: https://github.com/pinax-network/token-api/releases/tag/v3.17.0

Tycho Article DEX liquidity is *brutally* complex — prices flip every block, reorgs wreck your data, and most teams still run their own nodes just to get a sane price quote. 😵‍💫

Tycho on Substreams just killed that entire problem.

One streaming source. Real-time liquidity across DEXes. Zero infra to maintain.

Solvers, aggregators, market makers — this is the unlock.

MVP already live, public beta Q2. The Graph’s 2026 roadmap is cooking 🔥

Who’s integrating first?

Lodestar Dispatch is permissionless Arbitrum RPC paid per-call in GRT. lodestar-dashboard.com/dispatch

Setup:

Deposit $GRT to PaymentsEscrow on @arbitrum

Add to wallet: gateway.lodestar-dashboard.com/rpc/42161

Make calls. No keys. No accounts. No rate limits.