Documentation Index
Fetch the complete documentation index at: https://docs.prudra.dev/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Prudra gives any HTTP API server three things: the ability to charge AI agents for each request, a persistent workspace to store the results of that work, and a wallet to receive those payments. You add a few middleware functions, and your API becomes a paid service that any agent can call and pay for autonomously — no billing integration, no user accounts required. The design is API-first. Every feature is available over plain HTTP, which means any agent in any language can interact with Prudra-protected endpoints without installing an SDK. The@prudra/* npm packages are fast on-ramps for TypeScript server developers.
Prudra handles both major agent payment protocols simultaneously. When an agent calls your endpoint without paying, you respond with HTTP 402 containing both an x402 challenge and an MPP challenge. The agent picks whichever protocol its wallet supports. Your code handles neither — the middleware does.
How it works
The agent receives a 402 with both challenge headers and picks the protocol that matches its wallet. Your endpoint code runs only after payment is verified — the middleware handles everything before your handler.The three products
Payments
Add HTTP 402 payment gating to any endpoint. Accept both x402 (Base/USDC) and MPP (Tempo/USDC.e) in a single middleware call. A vault is created automatically on each successful payment.
Storage
Vaults are persistent workspaces created per payment. Store documents, files, and real-time events. Multiple agents can share a vault via session ID. Files are served from the
assets.prudra.dev CDN.Wallets
Receive payments into a managed wallet (Prudra custodies the key) or your own BYO wallet. Transfer tokens, bridge across chains, and withdraw to a bank account.
When to use Prudra
| If you need… | Use… |
|---|---|
| Any paid API endpoint for AI agents | Payments middleware |
| To store agent work output beyond the HTTP response | Vaults |
| Real-time progress streaming for long-running jobs | Vault events (SSE) |
| A wallet to receive crypto payments | Managed wallets |
| To monitor an existing wallet for deposits | BYO wallets |
| Multi-step agent workflows under one payment | Session payments |
Related
- Your first payment in 5 minutes — get a working paid endpoint in under 10 steps
- How Prudra works — the mental model for payments, vaults, and wallets
- Authenticate your requests — API keys and how to use them
- Payments overview — x402 vs MPP, when to use each