Byte Protocol
Let agents subscribe to verifiable per-byte USDC-priced data feeds on Arbitrum without traditional API keys or a proprietary token.
Overview
byte-protocol is a MCP server for the Build phase that connects agents to per-byte USDC data feeds and oracles on Arbitrum with verifiable pricing and no traditional API keys.
What is this MCP server?
- Per-byte USDC metering for data feeds and oracles aimed at AI agents
- npm byte-mcp-server v0.9.2 stdio; read tools work without PRIVATE_KEY
- Write paths use PRIVATE_KEY; RPC_URL defaults to Arbitrum Sepolia public RPC
- No separate API keys or protocol token described in the server manifest
- Package version 0.9.2
- npm identifier byte-mcp-server
- PRIVATE_KEY optional for read-only tools
What problem does it solve?
Agent apps that need paid, verifiable external data often rely on opaque API keys and subscriptions that do not match on-chain or per-use economics.
Who is it for?
Builders shipping agent or crypto-adjacent products who want MCP access to byte-protocol feeds with optional wallet writes on Sepolia or custom RPC.
Skip if: Teams building plain SaaS with only REST JSON APIs and no interest in chain RPC or USDC-metered data.
What do I get? / Deliverables
After install, your agent can read feeds without a key and optionally subscribe or publish with wallet-backed writes using USDC byte pricing on Arbitrum.
- MCP tools for byte-protocol feed read and optional write flows
- USDC per-byte priced data access pattern for agents
- Configurable RPC_URL for Arbitrum networks
Recommended MCP Servers
Journey fit
Canonical shelf is Build integrations when you embed paid oracle and feed semantics into agentic or on-chain-aware products. Integrations covers MCP tools that talk to external networks—in this case Arbitrum RPC and byte-protocol feeds rather than REST SaaS.
How it compares
On-chain USDC oracle MCP integration, not a generic analytics warehouse or LLM prompt skill.
Common Questions / FAQ
Who is byte-protocol for?
Indie developers and agent builders integrating verifiable USDC-priced data feeds who are comfortable with Arbitrum RPC and optional Ethereum keys for write tools.
When should I use byte-protocol?
Use it during Build when your agent must consume or publish metered oracle data on Arbitrum instead of conventional API-key SaaS feeds.
How do I add byte-protocol to my agent?
Install npm package byte-mcp-server, add the stdio MCP server entry, set RPC_URL if needed, and supply PRIVATE_KEY only if you call subscribe, unsubscribe, or publish tools.