Platform architecture
How discovery, provider configuration, gateway execution and payment orchestration fit together.
On this page
Components
- Web appThe public directory, these docs, and the provider dashboard. It reads and writes through the dashboard API.
- Dashboard APISign-in, API registration, test calls, launch, earnings and payouts for providers; plus the public directory and pricing endpoints.
- GatewayThe public edge agents call. Issues quotes, accepts payments, forwards requests to providers, and returns answers with receipts.
- Payment coreOwns every payment's state. Verifies authorizations, reserves them, and settles them on Solana.
- SignerA separate service holding the fee payer key. It re-checks every transaction against strict rules before co-signing it.
- Splitter programThe on-chain program that owns each API's vault and splits payouts between the provider and the platform.
Discovery
The directory lists only APIs that are live and listed. Every listing is an API launched through NODRA with its own vault, so every listing is payable. There are no imported or discovery-only listings.
Usage numbers (paid calls, success rate, paying agents, median latency) are recomputed every few minutes from settled payments. They're public at GET /v1/directory/apis; see the Directory API reference.
Provider configuration
An API's configuration is a single upstream URL (a public https:// base), an optional upstream key sent as one request header, one price per call, a billing rule and a category. Upstream keys are encrypted with AES-256-GCM before they're stored, and they're never returned by any API.
Gateway execution
The gateway serves only APIs whose status is live. For each paid call it appends the caller's path and query to the upstream URL, forwards only the Content-Type and Accept request headers plus the provider's key, and waits up to 20 seconds for an answer. It doesn't follow redirects, accepts only https upstreams, and caps request and response bodies at 1 MiB.
The caller gets back the provider's status code and body, with the provider's Content-Type and Content-Language headers. Other provider headers aren't passed through.
Payment orchestration
The payment core moves every payment through a fixed set of states: received, validated, reserved, calling upstream, upstream succeeded, submitted, settled; or one of the end states rejected, expired, upstream failed or settlement failed. Each change is recorded, and providers see the history on each payment.
Duplicate protection is durable: the same signed transfer can be used once, enforced by a unique key in the database, not just an in-memory cache. See Verification and settlement.