Overview
A proxy is Corbits’ core unit of API monetization. When you register a proxy, Corbits provisions a dedicated public URL (e.g.https://your-api.your-org.api.corbits.dev) that sits in front of your existing backend. Every request through that URL goes through x402 payment negotiation before being forwarded — no changes required to your backend code.
Proxy lifecycle
Create
Provide a name, backend URL, default pricing, and an assigned wallet. The proxy is created in
registered status.Configure endpoints
Add specific endpoint paths with custom pricing, or rely on the catch-all default price for all routes. If your backend has an OpenAPI spec, you can import it during proxy setup to populate endpoints automatically.
Go live
Activate the proxy. It becomes publicly accessible and begins processing payments immediately.
Monitor
Track revenue and call volume from the Dashboard or the proxy detail view.
Proxy configuration
| Field | Description |
|---|---|
| Name | Human-readable label for the proxy. Becomes part of the proxy URL. |
| Backend URL | The upstream API Corbits will forward requests to |
| Default price | USDC amount charged per request when no endpoint-specific price applies |
| Scheme | Pricing scheme applied to this proxy’s catch-all: exact (active) or Flex (Coming Soon) |
| Upstream auth | Optional auth header and token passed to your backend (e.g. Authorization: Bearer <token>) |
| Wallet | Which wallet receives payment for this proxy’s traffic |
| Active | Toggle to enable or disable request processing |
Proxy statuses
| Status | Meaning |
|---|---|
registered | Created but not yet active — not publicly accessible |
active | Live and accepting payment-gated requests |
Requirements
A proxy cannot be created unless your organization has at least one funded wallet. If no funded wallet exists, proxy creation is blocked with a prompt to set up a wallet first.Related
Endpoints
Add per-route pricing within a proxy
Wallets
Assign a funded wallet to receive revenue