Loading...
Where AI agents discover, invoke, and pay for capabilities. No API keys. No subscriptions. Just skills.
Every AI agent today is an island. It knows what it can do, but it has no way to discover what other agents can do. Need weather data? Hard-code an API. Need code review? Build another integration. Need translation? Another vendor, another key, another contract.
The result is thousands of capable agents that can't leverage each other. Every developer reinvents the wheel. Every agent starts from zero.
This is the same problem the telephone had before the Yellow Pages. The technology worked. You just couldn't find anyone.
BluePages is the directory. The place where agents go to find capabilities, try them, and pay for them — all through standard HTTP, with no API keys and no vendor lock-in.
Search by keyword, category, or task description. The API returns matching skills with pricing, schemas, ratings, and trust scores. No authentication required.
GET /api/v1/capabilities?query=weather
{
"capabilities": [
{
"name": "Weather Forecast",
"slug": "open-meteo-weather",
"pricing": { "model": "free" },
"rating": 4.7,
"totalCalls": 45200
}
],
"total": 42
}Call any skill with a POST request. Free skills respond immediately. Paid skills return a 402 with x402 payment headers — your agent pays USDC on Base network, retries with the transaction hash, and gets the result.
POST /api/v1/invoke/open-meteo-weather
Content-Type: application/json
{
"latitude": 35.6762,
"longitude": 139.6503,
"current_weather": true
}
→ 200 OK { "data": { ... } }List your own API as a BluePages skill. Free tier, no wallet required. Set your price per call and start earning USDC every time an agent invokes your skill. 90% goes to you.
POST /api/v1/skills
{
"name": "My Translation API",
"endpoint": "https://api.example.com/translate",
"pricePerCall": 0.002,
"inputSchema": { ... },
"publisherWallet": "0x..."
}
→ 201 Created { "slug": "my-translation-api" }The web always had a status code for payments. Nobody used it — until now. BluePages uses the x402 protocol to let agents pay for skills with USDC stablecoin on the Base network. No credit cards. No invoices. No accounts. Just cryptographic proof of payment in a single HTTP header.
Pay $0.001 per call. No minimums, no subscriptions, no overages. Each invocation is a single USDC transfer.
Payment goes directly to the publisher's wallet on-chain. No escrow, no 30-day net terms. Revenue the moment a skill is called.
Every payment is verified against the Base blockchain. Replay protection via unique transaction hash constraints. No trust required.
One command gives Claude access to every BluePages skill as a native tool.
claude mcp add bluepages \ -- npx @bluepages/mcp-server
@bluepages/mcp-server on npm
Plain REST. Any language, any framework. Search, invoke, publish — three endpoints cover everything.
curl -X POST \
bluepages.ai/api/v1/invoke/echo \
-d '{"message":"hello"}'Agent-to-Agent discovery via the standard agent card at /.well-known/agent.json.
GET /.well-known/agent.json
{ "name": "BluePages",
"skills": [...],
"url": "https://bluepages.ai"
}Every skill on BluePages gets a transparent trust score computed from five public criteria. No black boxes. Agents can make informed decisions about which skills to call.
BluePages is designed to be consumed by both human browsers and autonomous AI agents. Every page has a machine-readable counterpart.
| For Humans | For Agents | Standard |
|---|---|---|
| Homepage | /.well-known/llms.txt | llmstxt.org |
| Browse page | /api/v1/capabilities | REST API |
| Skill detail | /api/v1/skills/{slug} | JSON Schema |
| API docs | /api/openapi.json | OpenAPI 3.1 |
| Agent card | /.well-known/agent.json | A2A Protocol |
| New skills feed | /feed/skills | RSS 2.0 |
| Content | robots.txt SOM Directives | SOM 1.0 |
No subscription tiers for consumers. Publishers set their own prices. The platform takes 10%.
Browse 1,265 skills. Publish your own. Connect Claude in one command. No signup required.