
Status
in progress
Client
Internal product
Duration
Ongoing
Overview
Apiosk is an API monetization platform that replaces API keys, subscriptions, and invoicing with per-request USDC payments, turning payment into authentication for open, instantly consumable APIs.
Apiosk started from a simple observation: API keys are mostly a billing primitive disguised as authentication. They force consumers to create accounts, wait for approval, manage secrets, and commit to subscription plans before they can even test a single request. Apiosk removes that entire layer and replaces it with direct pay-per-call access.
At the center of the product is a Rust-based gateway that speaks the x402 payment flow. A client requests a paid endpoint, receives an HTTP 402 response with structured payment requirements, signs the payment with a wallet, and retries the request with proof attached. The gateway verifies the signature, confirms settlement eligibility, and forwards the request to the underlying API. The result is a flow that works for browsers, server-side clients, and AI agents without API keys or manual provisioning.
On the provider side, Apiosk includes a dashboard for turning existing APIs into monetized products. Providers can register endpoints, set per-route pricing, configure wallets, publish free or paid routes, and inspect usage and revenue in real time. Because the system is non-custodial, funds move directly to provider wallets and every settlement can be traced back to an on-chain receipt.
Technically, the platform is built for low latency and operational simplicity. The gateway stays stateless, caches configuration aggressively, and separates payment enforcement from provider business logic so teams can add monetization without rewriting their APIs. Apiosk turns closed, account-gated APIs into programmable, purchasable infrastructure and pushes toward a more open API economy where any request can be paid for instantly.
Gallery

Technologies Used
Key Features
Challenges
- Separating authentication, billing, rate limiting, and analytics from the traditional API key model without losing the control providers expect
- Designing a payment flow that feels as fast and predictable as a normal API request
- Supporting both human users in the browser and autonomous clients such as scripts, backends, and AI agents
- Keeping the gateway stateless and low-latency while still enforcing paid access securely
- Creating trust for providers by ensuring funds never sit inside the platform
- Making web3 payment mechanics understandable for developers who only want a simple pay-per-request experience
Solutions
- Reframed payment proof as the access credential so wallet identity replaces key issuance and account creation
- Built a Rust gateway with aggressive config caching and delegated settlement to keep request handling fast
- Adopted the x402 pattern with structured JSON payment requirements for machines and an interactive wallet paywall for browsers
- Used a non-custodial flow where payments go directly from consumer wallets to provider wallets
- Added provider tooling for endpoint registration, pricing, wallet setup, and real-time analytics
- Focused the product on one clear promise: pay for a request, get a response, and skip the rest of the platform friction