Anything an agent
pays for.

x402 turns any HTTP endpoint into something an agent can pay for autonomously. stealthPAY makes that spend feeless, fast, private, and governed. Seven places it lands first.

01

Use Cases

Seven, with the shape of each
01

Pay-per-call APIs

The canonical x402 loop — 402 → pay → data, in ~1 second. stealthPAY gates the route and governs the spend.
Integration · Server SDK middleware
02

Telegram pay-per-stream

A bot streams its AI response only after a confirmed micropayment — the whole loop finishes before the user feels a delay. No signup, no card.
Integration · Mini App wallet + bot
03

Agent-to-agent marketplace

An orchestrator routes a query to a specialist agent and pays it automatically, with a markup — a marketplace inside the conversation.
Integration · Sidecar + capped creds
04

Private consultations

Health, legal, financial questions answered by a bot — with the on-chain record revealing nothing about who paid whom or how much.
Integration · Shielded (XSS) routing
05

Gated content streaming

Preview → pause → micropayment → resume. Research, trading signals, premium newsletters — metered by the call, not the month.
Integration · Server SDK + receipts
06

B2B support bots

White-label AI support charging per resolved query, with full operator spend visibility and zero blockchain knowledge required.
Integration · Console + Server SDK
07

Programmable allowances

Streaming budgets, auto-replenish, per-agent caps, anomaly alerts, instant kill-switch. Agent payroll, governed.
Integration · Sidecar policy engine

Build one.

Gate a route, point your agents, and watch the spend in the console. Never touch a private key.
02

The Common Shape

Why these fit, others don’t
The test

When it fits

High-frequency, low-value, machine-initiated — and better off private. Score all four and the case is a fit.
The anti-pattern

When it doesn’t

One-off, high-value, human-in-the-loop payments are a worse fit — that’s what cards and invoices already do well.
Every case above shares a profile: many small payments, made by software, where the metadata is sensitive. That’s exactly the gap legacy rails leave open — fees too high, finality too slow, ledger too public, and no governance over an autonomous spender. stealthPAY closes all four at once, which is what makes these viable rather than merely possible.

Build one.

Gate a route, point your agents, watch the spend. Never touch a private key.