Pay for what's actually expensive.
Local-routed traffic is effectively free. You pay for tokens that actually went to a frontier API, plus a small margin on hosted local. Bring-your-own everything is always free.
Self-host ModelMeld. Bring your own frontier keys and your own GPU. Everything works on a snapshot of the routing data; the live curated feed is the upgrade.
- Self-host ModelMeld
- Bring your own frontier API keys
- Bring your own local GPU
- Bundled seed routing data (stale but functional)
- GitHub Issues + Discussions support
Same engine, but we host the local model. No DevOps, no GPU procurement. Live curated routing feed bundled in. Your frontier keys stay on your machine.
- We host the local model — no GPU required
- Pay-as-you-go: top up in $20 / $50 / $100 packs
- Your frontier keys stay on your machine
- Live curated routing feed (Pro tier — bundled)
- Start in 5 minutes — no DevOps
For self-hosters who want the live curated routing feed without our hosted model. Always up-to-date model selection data, same engine.
- Always up-to-date routing feed
- Same OSS engine
- Self-host on your own hardware
- Cancel anytime
- Email support
Your hardware, your cloud, or hosted by us — pricing flexes to the deployment. SSO + RBAC, audit logs, custom SLAs, direct engineering support.
- Deploy on your hardware, your cloud, or ours
- SSO (OIDC) + RBAC
- SOC 2-grade immutable audit log
- Custom SLAs
- Direct engineering support
Top up your account in seconds.
Credits never expire. Optional auto top-up with a monthly cap — set it and forget it, just like Claude API.
How the meter works
- →Local-routed requests: $0.30 per million tokens on Hosted. Free if you self-host on your own GPU.
- →Frontier-routed requests:billed by the frontier provider directly, against the API key you provided. We never see the cost; we don't mark it up.
- →Routing decision itself: always free.
- →Auto top-up:set a monthly budget cap and we'll keep your balance funded inside it. Turn it off and you're back to manual top-ups.
- →No prompt-content storage: request metadata + SHA-256 prompt hash only.