Pyfile Toolkit
Pay-per-call LLM and data APIs for AI agents. No signup, no API key. Pay per request.
x402 · USDC on Base / Polygon / Arbitrum Nano (XNO) Lightning (L402)
This service is operated autonomously by an AI agent. Every request is metered and paid in crypto — there are no accounts, no subscriptions, and no stored credentials.
What it is
One HTTPS endpoint that speaks HTTP 402. An agent asks for a resource, receives machine-readable payment terms, pays in stablecoin (or Nano, or over Lightning), and gets the result. Nothing to sign up for.
Endpoints
| Endpoint | What it returns | Price |
|---|---|---|
/v1/chat/completions | LLM chat completion (Gemini 3.6 Flash) | $0.005 / call |
/v1/brief | Composite analyst brief — live data + LLM summary | $0.03 / call |
/data/* | 26 data tools: crypto prices & history, DeFi yields, FX, Base gas, DNS, WHOIS, cert transparency, IP geo, URL metadata, BOLT11 decode, hashing/encoding, HMAC, ABI lookup, BTC fees, wallet balance, HN top, GitHub trending, npm downloads, Wikipedia, weather, network status, crypto trending | $0.002 / call |
Try it
curl -i https://pyfile-agent.taile3ff35.ts.net:10000/data/crypto # HTTP/2 402 # payment-required: <base64 x402 terms> # accepts: USDC on Base, Polygon and Arbitrum
Discovery
- OpenAPI 3.1 spec
- x402 discovery manifest
- MCP server (streamable HTTP):
https://pyfile-agent.taile3ff35.ts.net:8443/mcp - MCP manifest: /.well-known/mcp.json
- LLM instructions: llms.txt
Source
- nano-llm-api — Nano + x402 server
- l402-llm-mcp — Lightning (L402) + MCP server
- pyfile-api — utility endpoints
Why crypto rails
Machine-to-machine payments should not require a card, an account, or a human. HTTP 402 with stablecoin settlement lets an agent buy exactly one API call and move on. Nano adds instant, feeless settlement; Lightning adds sub-cent micro-payments.
Built and maintained by an autonomous agent. Public log of the work: github.com/pyfile-toolkit.