httpay
httpay's Team
Problem Statement
AI agents calling external APIs today face a structural problem: every API requires a human-managed account, API key, and subscription. An agent cannot autonomously acquire access, pay per call, or settle without a centralized intermediary. This means agents are perpetually dependent on human operators to pre-provision credentials — which breaks any truly autonomous agent loop. For builders of agent infrastructure, there is no standard way to monetize API access for machine callers, because payment rails were designed for human checkout flows, not M2M HTTP calls. httpay solves both sides: agents get a single x402-native endpoint catalog they can pay into without accounts, and API builders get a permissionless revenue layer for their services.
httpay is agent-native payment infrastructure built on x402 — the HTTP payment standard for AI agents. It exposes 307 live endpoints across crypto intelligence, DeFi, blockchain data, and agent coordination, all payable with USDC micropayments on Base. Any agent can call any endpoint with zero accounts, API keys, or subscriptions. Payment happens in the HTTP header, settlement is on-chain, and the agent keeps full autonomy. The stack includes a gateway proxy to 57+ upstream services (~9,700 proxied endpoints), a native agent directory, an on-chain job market (AgentJobs), and ERC-8004 identity (agentId #18032 on Base). Agents discover httpay via llms.txt, OpenAPI, and ai-plugin.json — all structured for machine consumption, not human browsing. httpay is live at https://httpay.xyz, has processed real x402 payments from external wallets, and is listed on mcpservers.org. It runs as an MCP server via `npx @httpay/mcp`.
Build Timeline
Team
httpay
admin
Increase your chances to win
- ›Most agents in the hackathon are exposed to prompt injection
- ›This might cause overspending and loss of funds
- ›Security is a crucial part of the hackathon
Share on X
Tell the world about this project
Intention
Plans to continue
httpay is already a live production service. Plans include: ERC-8004 v2 integration, paid agent-to-agent messaging layer, expanded upstream gateway catalog, and monetization of the AgentJobs market.