The RoutexAPI gateway
Every call to every listing goes through one data plane. It handles authentication, subscriptions, rate limits, quotas and analytics, so buyers integrate once and publishers never expose an upstream credential.
One key across every API
A buyer calls the gateway with a single RoutexAPI key instead of holding a separate credential per provider. The key is hashed with Argon2id at rest and shown in full exactly once, and it can be rotated with a grace period so a running integration does not break during the swap.
Subscriptions, rate limits and quotas are enforced in one place
Each request is authorized against the caller's subscription and metered in a single enforcement step: per-second rate limits plus daily and monthly quotas. The terms are frozen onto the subscription when it starts or renews, so a mid-period price or limit change never retroactively alters what a buyer already paid for.
Publisher credentials stay behind the gateway
A publisher's upstream credential is envelope-encrypted at rest and decrypted only in request memory to sign the outbound call. It is never returned by an API, written to logs or analytics, or shown in the dashboard beyond a mask. Publishers can also verify that traffic arrived through RoutexAPI rather than direct.
Built to stay up when something downstream is not
Hot routing data is cached so a normal request does not wait on a database, a circuit breaker sheds load from an upstream that has started failing, and the request path degrades step by step rather than failing whole when a supporting service is unavailable.
Usage you can both see
Every proxied call is recorded, so buyers can see their own consumption against their quota and publishers can see traffic, latency and error rates for the APIs they sell. Requests are metered as they are served, not reconstructed from logs afterwards.