One endpoint gives your AI agent 20+ real-world capabilities. Take screenshots. Generate PDFs. Search the web. Validate data. Process documents. No API keys, no accounts — just describe the action and pay in USDC.
// One request. Any action. POST https://api.pylonapi.com/do { "task": "take a screenshot of stripe.com/pricing" } // → Returns a PNG screenshot. $0.01. 200ms. // Or chain multiple actions POST https://api.pylonapi.com/do/chain { "steps": [ { "api": "web-scrape", "params": {"url": "..."} }, { "api": "md-to-pdf", "params": {"markdown": "{{steps.0.output}}"} } ] }
The Problem
Your agent can write a business plan, but it can't take a screenshot, generate a PDF, validate an email address, or look up a domain. Every agent builder ends up duct-taping together a dozen APIs with different auth flows, failure modes, and billing systems.
The AI stack has three layers: Brains (OpenAI, Anthropic, Google), Hands (Pylon), and Money (stablecoins via x402). Pylon is the missing middle — the layer that turns reasoning into real-world results.
How it works
Your agent sends a task in plain English. Pylon matches it to the right capability, executes it, and returns the result. Payment happens automatically via USDC micropayments on Base.
Send a task to /do — natural language or explicit capability. No docs to read, no SDKs required.
The gateway matches, routes, and executes — with automatic retries, circuit breakers, and quality tracking.
USDC micropayment on Base via x402. Pennies per action. You get the result in one round-trip.
Use /do/chain for multi-step workflows: "screenshot this page, extract the text, generate a report."
What Your Agent Can Do
Every capability your agent needs to interact with the real world. Screenshots, documents, search, data validation, file processing — all through one endpoint.
"Screenshot stripe.com" — Full-page captures in PNG or JPEG. Your agent can see any webpage.
$0.01 / action"Convert this markdown to PDF" — Create PDFs from markdown or HTML. Parse existing PDFs. OCR scanned images.
$0.01 / action"Search for x402 protocol news" — Real-time web search results. No API keys needed from the agent.
$0.003 / action"Validate hello@stripe.com" — Email validation, domain intelligence, WHOIS lookups, DNS records, IP geolocation.
$0.002 / action"Convert this CSV to JSON" — Format conversion between JSON, CSV, XML, YAML. Resize images. Generate QR codes.
$0.005 / action"Scrape the pricing page" — Extract readable content from any URL. Returns clean markdown with full browser rendering.
$0.01 / actionInstant Integration
Install the Pylon MCP server and give Claude, Cursor, or any MCP-compatible assistant instant access to every capability.
// Claude Desktop or Cursor config { "mcpServers": { "pylon": { "command": "npx", "args": ["-y", "@pylonapi/mcp"] } } }
That's it. Your assistant now has screenshots, PDFs, search, scraping, and 16 more tools.
Flexible Interface
Two ways to call any capability — describe what you need, or specify exactly.
{
"task": "validate the email ceo@stripe.com"
}
Pylon figures out which capability to use and extracts parameters automatically.
{
"capability": "email-validate",
"params": { "email": "ceo@stripe.com" }
}
Or specify the exact capability and parameters when you know what you want.
Capability Discovery
When an agent requests an action Pylon doesn't natively support, it searches the x402 ecosystem for a service that can fulfill it — and routes the request automatically.
Agent asks Pylon to send an email. Pylon doesn't have email natively.
Pylon searches the x402 bazaar for services that can handle it. Finds an email API at $0.005.
Pylon activates the service, adds reliability tracking, and fulfills the request — one round-trip.
Transparent pricing. Every response shows the full cost breakdown — what the provider charges and what Pylon adds for discovery and routing.
"pricing": { "source": "discovered", "providerCost": "$0.005", "pylonFee": "$0.005", "totalCost": "$0.010" }
Why not just use the LLM?
Your agent's reasoning time is expensive. Don't waste it on tasks that should be deterministic API calls.
The Agent Stack
Three layers are emerging in the AI agent economy. Pylon is the action layer.
Why Pylon
Traditional APIs require accounts, dashboards, and billing cycles. Pylon requires one thing: payment.
No registration. No OAuth. No tokens to rotate. Just HTTP + USDC.
Circuit breakers, automatic retries, quality tracking. Every action goes through the reliability layer.
Anyone can add capabilities. More providers → more actions → smarter agents.
Plug your API into Pylon and every agent in the ecosystem gets access. You keep 85% of revenue. Zero customer acquisition cost.
Ecosystem
Drop Pylon into your existing stack. MCP server, framework SDKs, or raw HTTP — however your agents work.
Agent Frameworks
Works with MCP Clients
Listed On
Built On
Install the MCP server, or point your agent at api.pylonapi.com/do. That's the entire integration.