Skip to main content
Glama

byte_buy_data

Buy a single data packet from any PayPerByte feed via the x402 payment gateway. Pay per call in USDC with no subscription or prior on-chain setup.

Instructions

Buy a single data packet from any PayPerByte feed via the x402 payment gateway. No subscription, no allowance, no prior on-chain setup — pay-per-call USDC settlement. The MCP server signs an EIP-3009 transferWithAuthorization on behalf of the wallet whose PRIVATE_KEY is configured, the x402 facilitator submits the tx, and the data comes back inline with the on-chain settlement tx hash. Use byte_subscribe instead if you want a continuous stream of broadcasts from a publisher. The catalog of available feed slugs lives at https://x402.payperbyte.io/feeds (free GET). Requires PRIVATE_KEY env var on the MCP server and USDC on the configured wallet. NOTE: paid feeds settle REAL USDC on Base mainnet (eip155:8453) — the exact price is quoted in the 402 challenge (flagship address-reputation: $0.05/verdict). Use a dedicated wallet holding only what you intend to spend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedYesFeed slug — one of: defi-yields ($0.049), weather ($0.021), earthquakes ($0.0015), space-weather ($0.0024), news-feed ($0.0063), code-pulse ($0.010), runtime-eol ($0.069), threat-intel ($0.026), x402-pulse ($0.015), stablecoin-rails ($0.020), perp-funding ($0.0073), usc-statute ($0.012), evidence-pack ($0.100), address-reputation ($0.050), pkg-verdict ($0.050), sanctions-screen ($0.050), liquidation-stream ($0.0079), positioning-snapshot ($0.037). Full catalog: https://x402.payperbyte.io/feeds (free GET). (For fact-oracle Q&A use byte_query_fact instead — it uses a different request-response flow.)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feedNoEchoed feed slug
paidNoTrue if an x402 payment was made (false on free/cached feeds)
priceNoUSDC paid for this packet (e.g. '$0.001000'); omitted on free feeds
txHashNox402 settlement transaction hash
payerNoWallet that signed the EIP-3009 authorization
statusNoHTTP status of the (post-payment) gateway response
dataNoDecoded feed payload returned by the publisher
errorNoError message if the buy failed
detailNoAdditional error detail, if any
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses signing EIP-3009, x402 facilitator submission, inline return with tx hash, settlement on Base mainnet, real USDC cost. No contradiction with annotations (readOnlyHint=false, etc.).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single dense paragraph covering all aspects without repetition; slightly long but justified by complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers payment flow, requirements, alternatives, and catalog; output schema exists so return values are implied. Minor gap: no error handling mention.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter 'feed' is fully enumerated in schema with prices. Description adds context (catalog URL, alternative for Q&A) beyond schema, validating purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it buys a single data packet from PayPerByte feeds via x402, distinguishes from byte_subscribe (continuous stream) and byte_query_fact (Q&A).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names alternatives (byte_subscribe for streams, byte_query_fact for facts), prerequisites (PRIVATE_KEY, USDC), and the feed catalog URL.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/0rkz/byte-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server