Features
Everything you need to ship an API.
A clean gateway, per-customer keys, plans with trials, customer webhooks and a public marketplace — all in one place.
<5 ms
p50 gateway overhead
15
webhook event types
15%
platform cut, no extras
GET /weather/v1/forecast · 42ms
82%
monthly quota used
+€1,284
provider revenue
EU
data residency
Find, subscribe to and integrate APIs without detours.
Buyers see price, limits, trial, status and integration guidance before subscribing. After purchase, keys, usage, invoices and webhooks stay in one place.
1 key
per API subscription
Live
usage & limits
Sell APIs, measure usage and keep payouts controlled.
Sellers publish APIs with plans, limits, trials and feature bullets. oanor handles gateway, subscriptions, usage metering, webhooks and payout transparency.
10%
platform cut
EU
ops & data
The buyer workflow
Discover
Compare APIs by category, price, status, latency and provider before a key is created.
Subscribe
Choose a plan, start a trial or activate a paid subscription; limits and costs are visible up front.
Integrate
Copy the key, use the sample request and call api.oanor.com instead of the upstream directly.
Control
Usage, daily limits, monthly quota, invoices, webhooks and key history stay traceable.
The seller workflow
Publish
Maintain API profile, endpoints, SEO copy and languages without exposing secrets.
Price
Create plans with trials, hard limits, overage and feature bullets.
Protect
The gateway enforces RPS, daily and monthly limits, blocks expired subscriptions and logs admin actions.
Grow
Subscribers, reviews, endpoint analytics and payout data show which APIs produce revenue.
Scenarios
The critical cases are planned.
Billing and API access must remain correct when limits, trials, payments or upstreams become difficult.
Limit reached
RPS, daily and monthly limits are checked per subscription before the upstream is reached.
429 or overage by plan
Trial expires
Trial days are part of the plan; after expiry, access continues only with a valid subscription.
No silent free access
Payment missing
Subscriptions and keys depend on billing status so buyers cannot consume around the paygate.
Access blocked
Webhook must be trusted
Events are signed, retried and logged; receivers verify the signature before processing.
HMAC + retry + log
Upstream fails
Failures stay separated: oanor gateway, provider upstream and customer key are traceable.
Clear 5xx/status data
Localized slugs
English is the default without /en; German uses /de and localized segments, future languages follow the same pattern.
Scalable i18n structure
Platform
One control plane for marketplace, gateway and billing.
The page separates buyer and seller needs, but the platform calculates against the same sources: subscription, plan, key, usage and payment status.
Billing as gate
Active subscription, trial, expiry, hard limit and overage decide whether a request may continue.
Gateway before upstream
Customers call oanor; upstream auth, header allow-list and error handling stay server-side.
Usage visible
Requests, latency, error rate, quota warnings and webhook events are traceable for operations and support.
Audit & EU
Admin actions, signatures and data residency are prepared so support and compliance do not have to guess.
Frequently asked questions
Quick answers about pricing, quotas, and integration.