Made for the way you work
Use subscription credits first
Make use of the plan you already have. Pumpkin can use supported subscriptions first and keep configured alternatives ready.
In practice
A useful place to start
Your preferred model is available through a subscription and your own API key. The subscription gets first use. If it reports exhausted quota, the same turn can continue through the next ready route.
Use your signed-in account
Pumpkin works through your installed, signed-in Codex or Claude Code app. It uses that app's subscription access rather than asking you to turn a subscription login into an API key.
Set the order yourself
Provider order defaults to subscriptions first. Move routes up or down to fit your accounts. Models reached by several routes stay grouped, with the current route shown in the picker.
Handle quota changes
When a subscription reports its limit, Pumpkin can move to the next ready route for the same model. The exhausted route becomes eligible again after its reset. Usage is attributed to the route that served the request.
Get started
Install and sign in to the supported provider app. Add its subscription models in Settings, then Models, and review Provider order. Add an API route only if you want it available too.
Good to know
Your provider's plan terms and limits apply. API fallback can cost money. Subscription quota is not a cash balance or unlimited use, and subscription routes currently support text only.