for agents
Your agent can pay for what it runs.
Media generation, chat completions, and a searchable prompt library — one paid endpoint and one MCP server, on two rails: per-call USDC settlement with no account, or an API key that bills prepaid credits.
2
payment rails — x402 wallet or lp_ API key
11
tools on one MCP server — free and paid
$0.002
minimum paid call, metered per use
What an agent can call
Media generation
Text-to-image, image edit, text-to-video, and image-to-video across the hosted catalog — including a members-only private line. The quote arrives per result, before anything settles.
Chat completions
A standard chat-completions request shape against nine frontier and open-weight models. Billed at your max_tokens cap — set it tight to bill tight.
Prompt library
Search, enhance, trending, and packs built from real published results — every card carries the exact instruction and model that made it. Free tools over MCP.
Two ways to pay
x402 — no account
POST the endpoint; it answers 402 with a PAYMENT-REQUIRED quote. Your wallet settles it in USDC on Base mainnet; retry with the PAYMENT-SIGNATURE header. Pass payer = your wallet for settled-volume tiers — 5%, 10%, or 15% off at $100, $500, or $2,000 lifetime.
Invalid input, policy rejection, and provider failure never settle or bill — an agent only pays for a delivered result. The same guarantee is written into the manifest your agent reads.
Text models — live catalog
The 402 quote = estimated input tokens × in-rate + your max_tokens cap (≤ 8,192) × out-rate. The same table, machine-readable, at /v1/agent/models.
One MCP server
{
"mcpServers": {
"livepair": {
"url": "https://livepairai.com/mcp"
}
}
}Free tools work the moment it attaches — prompt search, trending, enhance, model listing, price quotes. Paid tools quote in USDC and settle the same way. Per-client config fields live in the MCP setup docs.
Built under a judgment gate
This codebase doesn't ship on vibes. Before a change can deploy, a dedicated judgment model evaluates the diff against a fixed vocabulary of typed constraints — suppression checks, unverified delivery paths, silent-failure patterns, scope drift — all in one call, and only high-confidence verdicts can block.
Review memory persists between runs: files that fail get examined harder next time, and open obligations carry forward until resolved. A deterministic floor — dependency audits, endpoint vetting, contract checks — runs even when the judge is offline and can't be argued out of blocking.
It's the discipline agent pipelines need in general: the model proposes, typed rules dispose. The same gate audits this site's copy — which is why the numbers on this page match the running code.
The mechanics, in plain terms
Does my agent need an account or an API key?
Not on x402 — the caller's wallet settles each call in USDC on Base mainnet. The second rail is a standard API key: sign up, buy credits by card or crypto, create an lp_ key in settings, and send it as Authorization: Bearer lp_… — calls bill the prepaid balance.
What does a call cost?
Media is priced per result — the quote arrives with the 402 before anything settles. Chat is priced from token estimates: estimated input tokens at the model's in-rate plus your max_tokens cap (≤ 8,192) at the out-rate, with a $0.002 floor.
What happens when a generation fails?
Nothing settles. Invalid input, policy rejection, and provider failure all exit before settlement — you only pay for a delivered result.
Can an agent resell generation?
Yes — pass `payer` = your wallet and settled lifetime volume unlocks automatic discounts (5% at $100, 10% at $500, 15% at $2,000). Generated media is resellable at your own pricing.
Endpoints
https://livepairai.com/mcpstreamable-http, no authGET /v1/agent/modelsfreeGET /v1/agent/manifest.jsonfreeGET /v1/agent/openapi.jsonfreePOST /v1/agent/generatepaidPOST /v1/agent/chatpaidGET /v1/agent/jobs/{id}freeGET /v1/agent/balancelp_ key — prepaid balance + ledgerGET /SKILL.mdfreePoint your agent at https://livepairai.com/mcp — free tools work on attach, paid tools settle in USDC per call. The full contract lives in the API reference and the MCP docs and the machine guide.