Standards
Agent-native standards
The open standards KeeperHub speaks fluently today. MCP for tool discovery, x402 and MPP for payments, ERC-8004 for on-chain identity. Together, they are how autonomous agents find, invoke, and pay for execution infrastructure without a vendor directory in the middle.
Why we invest here
Agents that can be discovered, invoked, and paid without bespoke integration work are worth more than agents locked to a specific vendor stack. KeeperHub commits to the open standards that make that possible. Our goal is that an agent anywhere in the ecosystem can call KeeperHub over a protocol it already speaks, without a sales call or an API key, and pay only for what it runs.
The stack
Four standards, one agent
MCP Server
Tool discoveryThe Model Context Protocol is how agents discover and invoke tools. KeeperHub's MCP server exposes our triggers and actions natively to Claude, GPT, LangChain, CrewAI, ElizaOS, and any MCP-compatible runtime. Live today at docs.keeperhub.com/ai-tools/mcp-server.
Read full integrationx402
HTTP payment railHTTP payment protocol authored by Coinbase and Cloudflare, now under the Linux Foundation. KeeperHub emits spec-compliant 402 challenges for every workflow execution. Live since 2026-04-13 and registered on x402scan.com.
Read full integrationMPP
Machine payment protocolMachine Payments Protocol co-authored by Tempo and Stripe for pay-per-execution micropayments. KeeperHub is registered on mppscan.com. First external agent payment settled 2026-04-14 with no human in the loop.
Read full integrationERC-8004
On-chain identityEmerging Ethereum standard for agent and service identity on-chain. KeeperHub is registered so agents can discover and verify our declared execution capabilities without a centralized directory.
Read full integrationBuilding an agent?
Your agent probably already speaks at least one of these. KeeperHub is reachable through all four.
