Private beta · live on Base

Get paid whenagents use your API.

Put your API behind Xaetha and every agent that calls it pays first — in USDC, with a spending limit and a receipt, before a single request reaches your code.

See how it works

For developers and teams who ship an API, model, or tool — and want agents to pay for it.

CappedSigned receiptsUSDC on Base

sentiment API

Live

Earned today

$1,284.50USDC

Rails

x402 · MPP

Calls today

1,938

Receipts

signed

x402Basex402Base

What you get

One gateway, everything you need to get paid.

Accept

Agents pay per call over x402, or top up prepaid credits. One request pays and calls.

Govern

Every call clears the payer's caps before it runs. Over-limit or unfunded requests are rejected — you never serve traffic you won't be paid for.

Prove

Every charge returns a signed receipt — proof, not your word against theirs.

Get paid out

USDC lands in your wallet on Base. Cash out to your local bank, coming soon.

How it works

Four steps. No payments code.

POST /v1/sentimentregistered

price$0.05 / call

your codeunchanged

Step 1 / 4

Front your endpoint.

The agent pays first.

It hits the route and Xaetha collects the payment in USDC before your handler ever runs.

Only paid calls reach your code.

An agent that can't pay — out of funds, or past the limit its operator set — is turned away before your handler runs. You never serve a request you won't be paid for.

You get paid.

USDC lands in your wallet with a signed receipt of the charge. Reconciliation is a download.

The product

A meter on your API, not a payments project.

Everything between an agent's request and your payout — acceptance, spend caps, idempotency, signed proof, and money in your own wallet.

Settle before your code runs

An agent pays first. No payment, no compute — your handler only runs on a charge that already cleared.

→ GET /v1/route402

← X-Payment 0.05 USDCpaid

→ handler runs200

Spend caps — 8 scopes

Per agent, per payer, per day, per workflow. Enforced before settlement, fail-closed.

payer cap$19.90 / $20.00

agent · payer · day · workflow next blocked

Signed proof, end to end

Every charge returns a signed receipt; every workflow exports a statement anyone can verify. 100% receipted.

Idempotent by default

Retry ten times, charged once. Network flakiness never double-bills a payer.

Accept any rail

x402 today, MPP negotiated with a signed offer — built to add ACP, AP2 and L402.

Two ways to integrate

One await pay() with the SDK, or paste one MCP config into Claude or Cursor.

awaitpay(url)· or ·npx @xaetha/mcp

Your money, your wallet

USDC settles to your own wallet on Base — no platform float. Local cash-out coming next.

USDC · Base→ local cash-out · soon

Integrate

Three ways to integrate.

From a typed SDK call to one MCP paste to raw HTTP — pick whatever fits your stack. The gateway does the rest.

agent.ts

import { pay } from "@xaetha/client";

const { data, receiptUrl, txHash } = await pay({
  providerSlug: "acme",
  endpointSlug: "sentiment",
  body: { text: "ship it" }
});

One call from your agent

Back comes the data, a signed receipt URL, and the on-chain settlement hash — in a single await.

Best for

TypeScript & Node agents

npm i @xaetha/client

Why Xaetha

Agents aren't the customer your billing was built for.

An agent shows up, calls your endpoint, and leaves — no card, no checkout, no human watching the spend. Charging it takes more than a payment form.

A buyer with no credit card

An agent finds your endpoint and calls it — no signup, no checkout, no human at the keyboard. It pays over x402 from a wallet, per call, before your handler runs.

→ GET /v1/route402

← X-Payment 0.05 USDCpaid

→ handler runs200

Fail closed, not open

Spend caps across 8 scopes — agent, payer, day, workflow — enforced before settlement. A call over the limit is rejected, not absorbed into a surprise bill.

payer cap$19.90 / $20.00

agent · payer · day · workflow next blocked

Your wallet, your proof

USDC settles straight to a wallet you control — no platform float. Every charge returns a signed receipt anyone can verify.

receipt · 8f3a… signed

0.05 USDC · Base→ your wallet

Or build it yourself

A payment rail for agents isn't a weekend's work.

Card billing can't charge an agent, so the alternative is to build the rail yourself. That's six separate disciplines — one of them a regulated business — and the part of the stack a non-crypto team has nobody on staff to own.

Security

Wallets and key custody

Hot-wallet custody, key rotation, signing infrastructure. One leaked key empties the account — and on a product team it's nobody's job.

Infra

A new build per chain

Base, Solana, Tempo, and whatever rail comes next are each their own RPC, gas handling, and reorg edge cases. “Accept anywhere” means maintain everywhere.

Protocol

Every payment standard

x402 and MPP today; ACP, AP2 and L402 tomorrow. Each is a spec to implement, test, and keep current as it shifts underneath you.

Compliance

The local-currency off-ramp

Turning USDC into dirhams or dollars in your bank means a licensed broker, KYC/AML, and treasury ops. That's a company, not a feature.

Billing

Caps that fail closed

Metering every scope before settlement, atomic and race-safe. Get it wrong and one runaway agent loop drains the account before a dashboard catches up.

Proof

Receipts you can verify

Idempotent settlement so retries never double-bill, plus a signed receipt and a verifiable statement per workflow. More keys to hold safely.

With Xaetha it's a paywall, not a payments company you have to become.

Any chain, any protocol, settled to your own wallet — and cashed out where you bank.

xaethahandled

railsx402 · MPP

chainsBase · Solana · Tempo

settles toyour wallet

cash outlocal currency

Is this just crypto?

The rail is USDC — a dollar stablecoin, not a speculative token. To you it's a balance that lands in a wallet you control. The agent handles the wallet; you handle an endpoint and a price.

Will agents actually pay?

They already do. x402 is an open payment standard — an agent that hits a 402 responds with payment and retries, no human prompt. The buyer that can't use a card can use this.

What happens when a call fails?

It fails closed. No payment, no compute. Over a cap, the call is rejected before it runs. A retried request is charged once — and every charge leaves a signed receipt.

Use cases

If an agent can call it, it can pay for it.

Inference, data, a tool over MCP, or a whole multi-step job — price it once and agents pay per use.

Inference APIs

Sentiment, embeddings, vision — whatever you serve. Put a price on it and agents pay per call.

POST /embeddings· $0.001 / call

Data & search

Search, scraping, market data. Agents pay to query, you never chase an invoice.

GET /search· $0.004 / query

AI tools over MCP

Expose a tool to Claude or Cursor and every call is paid automatically — no checkout.

tool: summarize· $0.02 / run

Whole workflows

Meter a multi-step job under one budget, with a signed statement of everything it spent.

job budget· $5.00 cap

Anything with a URL

If it's an HTTP endpoint, an agent can pay for it. That's the whole idea.

any HTTPS route· 402 → 200

FAQ

Questions, answered.

An API endpoint and a wallet. Register the endpoint, set a price, point traffic at the gateway. You don't change your handler.

No. Any agent with a wallet can pay over x402 — or top up prepaid credits. There's no signup step in the payment path.

Minutes. Add one await pay() call on the agent side, or paste one MCP config into Claude or Cursor.

Start charging the agents already calling your API.

Private beta on Base. Live in minutes — one call, or one config paste.