One key for every model on Moth
One wallet, one balance and one moth_ key reach 34 chat, image, video and music models, each priced beside the list price its maker publishes.
01
Five models, five accounts
Say your team uses one chat model for code review, another for long documents, an image model for mockups, a video model for a launch clip and a music model for its soundtrack. Done the usual way, that is five accounts, five keys, five invoices and a card on file with each maker.
Todayone account, one key and one bill per maker
- Anthropicaccountkeybill
- Googleaccountkeybill
- OpenAIaccountkeybill
- xAIaccountkeybill
- Kuaishouaccountkeybill
With Mothone balance and one key for every maker
- Anthropicbelow list
- Googlebelow list
- OpenAIbelow list
- xAIbelow list
- Kuaishoubelow list
On Moth the account is your wallet. You sign one message on Robinhood Chain, with no email and no form, and the server keeps only a keyed hash of the address.
02
One key reaches every model
From there one balance pays for everything, and one key that starts with moth_ reaches every model on the network. Changing models is a change to the model field, never a new account.
- 34
- models on one moth_ key
- 14
- chat models, priced per million tokens
- 20
- image, video and music models, priced per image, second or song
The key is the only thing your code needs to know about Moth, and it stays the same whichever model answers.
03
Priced beside the list price
Every price on Moth starts from the list price the model's maker publishes, checked on the maker's own page and dated. Our price sits beside it, and so does the real saving, which is large on many models and small on the few that sit close to list.
- 01$3.00
The maker's list price
per million input tokens, as published - 0217 Oct 2026
Checked at the source
on the maker's own page, and dated - 03$1.50
Our price beside it
what your call is charged - 0450%
The saving, shown
below list, on every page that prices it
Chat14 models
Image, video and music20 models
The same numbers come back from the API, so the figure you read on the pricing page is the figure your call is charged at.
04
Held, then settled
Before a model runs, the call reserves its worst case on your balance. When it ends, it is charged only for what it used and the rest comes back. A call that fails before any output releases its hold in full, so the balance can't go below zero.
- 01Readya call arrives
- 02Heldworst case reserved
- 03Chargedwhat it really used, never more than the hold
- 04Releasedthe rest goes back
- 05Settledthe balance never below zero
Or, from Held, if the call errors
- Failedthe call errors
- Released in fullnothing is charged
Images, clips and songs run the same way as jobs. A job holds its unit price times its units, and a job that fails or never finishes is charged nothing.
05
Keys you can limit
Make as many keys as you need in Moth Console, one for each project or teammate, and give each its own rules, so a script that runs away stops at the limit you set rather than at the end of your balance.
- A spending cap stops a key once it has spent what you allowed, counting the holds still open.
- Allowed models keep a key to the models a project needs.
- Rate limits apply to every key and to the account across all its keys.