Made for the way you work
No token markup
Your model bill should buy model use. Bring your own keys and keep the provider's price, with no Pumpkin token markup.
In practice
A useful place to start
You use one provider for hard tasks and another for quick edits. Each bills your own account. Pumpkin does not add a margin to either direct connection.
Keep the bills clear
Your Pumpkin seat pays for the editor. With your own API keys, model usage is billed separately by the provider. You can choose a model based on what the task needs, with no editor token bundle to spend first.
Use what you already pay for
Connect supported Codex or Claude Code subscriptions and put their available quota first. When you also configure a paid API route, Pumpkin can use it after subscription quota runs out.
Compare before you choose
The public model pricing and capability pages show current catalog facts. In the editor, inline usage helps you see the cost of the work as it happens.
Get started
Add your own provider keys in Settings, or connect a supported subscription. Choose a model and inspect the route shown with it.
Good to know
Optional Pumpkin credits are a separate, hosted payment route with service fees. The no-markup promise applies to your own provider keys; subscription limits and provider charges still apply.