Verified data for AI agents, paid per byte.
First-party feeds and oracles where every paid response carries a signed provenance receipt the payment-taker can’t self-issue — so your agent verifies the exact bytes before it acts. Pay per call in USDC over x402 on Base: a wallet, not an API key. No token.
last updated 2026-07-25 13:25 UTC · counts and receipts, never revenue
Three steps. Verify before you act.
Find a feed, pay per call in USDC over x402 — settled on Base mainnet — and check the signed receipt before your agent acts on the data. No API key, no token.
Discover
01Browse the catalog — or list feeds straight from the MCP server.
#every feed is a first-party PayPerByte publisher.$agent.callTool('byte_list_feeds')→address-reputation · sanctions-screen · threat-intel→evidence-pack · pkg-verdict · liquidation-stream · …→breadth: weather · earthquakes · runtime-eol · …→11 feeds + oracles · from $0.003 a call
Pay per call
02One x402 call — USDC settles on Base mainnet, no subscription needed.
#an unpaid request returns the 402 challenge.$curl -i -X POST x402.payperbyte.io/feeds/address-reputation \-H 'Content-Type: application/json' \-d '{"address":"0x…","domain":"example.com"}'→HTTP 402 · pay $0.10 USDC on Base (eip155:8453)→sign EIP-3009 + replay → 200 + signed verdict#GET-able feed? curl /feeds/weather → 402 too.
Verify
03Recompute the hash and recover the signer before acting.
#every paid 200 carries a signed receipt.→keccak256(responseBody) == payloadHash ✓→recoverSigner == BYTE attester ✓→byte_verify_payload → { verified: true }#if it doesn't match, don't act on it.
Buy the data. Verify it before you act.
Buy verified feeds
First-party feeds and oracles, paid per call in USDC over x402 — no account, no API key. Every paid response carries a signed receipt. Browse the catalog and per-call prices.
Verify before you act
Whatever judges or scores the data, someone still has to prove which bytes were actually delivered and who signed them — that layer is ForeSeal, and the payment-taker can't self-issue it. Recompute the hash, recover the signer over the exact bytes; change one byte and the signature no longer matches.
Running a data API? hello@payperbyte.io — the Gate makes your feed verifiable by every agent on the Kit.
Verify before your agent acts.
ForeSeal is the verify-before-act layer for agent data. The Gate stamps a cryptographic receipt over the exact bytes you serve; the Kit lets the agent recompute the hash and recover the signer before it acts on a single byte. Watch it act on genuine bytes and refuse four attacks in about a second.
A few lines. Paid per call.
Drop the MCP server into any agent. Discover a feed, pay per call over x402 — settled in USDC on Base mainnet — and verify the signed receipt before acting.
#npm i byte-mcp-serverimport { Client } from "@modelcontextprotocol/sdk";const c = new Client({ name: "agent" });const r = await c.callTool("byte_buy_data", { feed: "address-reputation" });await c.callTool("byte_verify_payload", { txHash: r.txHash });→{ verdict: "ALLOW", verified: true, tx }
Boring stack. Bored on purpose.
A lean first-party contract core. USDC for settlement on Base mainnet. No new chain, no token.
Public artifacts, not testimonials.
The demand and the standards work are happening in the open. These are links you can open — public venues, not endorsements, and nothing here is a customer claim.
also on npm · byte-mcp-server ↗
Live now. Start in one line.
No signup, no API key, no token — your agent pays per call in USDC on Base, a wallet instead of an account. The read-only tools need no wallet at all, so you can try it dry in seconds.
#see verify-before-act — no install, no wallet$npx @foreseal/demo#the 15-tool agent interface$npx -y byte-mcp-server#buyer — verify before acting$npm i @payperbyte/sdk#seller — stamp receipts on your endpoint$npm i @foreseal/gate
Starter kit · optional
The npm packages above are free MIT and stay that way — the kit sells the assembled afternoon.
Live on Base today. Mainnet anchor next.
Pay-per-call is live on Base mainnet now — start in one line above. The on-chain attestation anchor moves to Arbitrum One after an external security audit; leave an email and we'll send one note when it clears.