Two lines, and both are legible. The subscription pays for the gateway itself — routes, keys, analytics retention, support. Metered usage tracks the tokens that actually travelled through it. Provider charges stay on your own upstream accounts.
Subscription + metered usage
NotePrices below are the published list rates for the current commercial review. Upstream provider charges are billed by your provider on your own account and are not included.
$0per month
For a single application and one or two upstreams, while you decide whether the routing layer earns its place.
$49per month
For a product team running real traffic across regions, with more than one person answering for the bill.
Customannual agreement
For sustained production volume, private upstreams and contractual requirements on residency and retention.
Metering is deliberately simple: it follows the tokens that actually reached an upstream provider through the gateway. Anything the gateway answered on its own is not billed as routed usage.
No. Upstream charges are billed to you by your provider on your own account. RouteMind charges the subscription and the routing fee on metered tokens, and shows both next to your provider usage so the numbers reconcile.
Nothing breaks. Metered usage continues and appears on the same invoice. Plan limits govern routes, retention and support, not whether your traffic is served.
Yes, and that is the point. A cache hit never reaches an upstream, so it costs no provider tokens and is not billed as routed usage. Hit rate is reported so the saving is visible rather than claimed.
That is the default. You delegate upstream credentials to the gateway and keep your existing provider agreements, quotas and discounts.
Run the Developer plan against a slice of production traffic. The usage record it produces is the same one the metered line is computed from, so the estimate is arithmetic rather than a guess.
