Pullfrog Router
Pullfrog Router reaches every major model provider through one billing account, at provider cost with no markup. Pullfrog mints a short-lived key for each run, so you manage no provider keys.
The Providers section of the console's Billing card switches the whole account between two tabs at any time:
| Tab | Who pays for model usage |
|---|---|
| BYOK (recommended) | Your provider, through your own API key or subscription |
| Pullfrog Router | Your Router credit balance |
A provider key stored with Pullfrog is used for the models it covers even on Router.
Credit balance
Router runs draw on a prepaid Router credit balance. Use Add payment method on the Pullfrog Router tab to save a card, then Add credit in the Top up row for a one-time top-up.
| Balance | Card on file | Router runs |
|---|---|---|
| Positive | Yes | Any model |
| Positive | No | DeepSeek Flash only |
| Zero | Either | Stop, and the PR comment links to the console to add credit |
Free models, models you hold a Pullfrog-stored key for, and BYOK accounts are not affected. View Router history at the foot of the tab lists top-ups and credit grants.
Auto-reload
Auto-reload is off by default. Turn it on once a card is on file, and Pullfrog charges the card whenever the balance drops below your threshold.
| Setting | What it does | Range |
|---|---|---|
| Auto-reload amount | Credit added per reload. The balance lands at its current value plus this amount. | $10 to $100,000 |
| Auto-reload threshold | The balance that triggers a reload | $5 to $10,000 |
Each charge adds an estimated card processing fee on top of the credit amount, with no Pullfrog markup: 2.9% + $0.30 for US cards and 4.4% + $0.30 for international cards.
Monthly spend limit
Monthly spend limit caps how much auto-reload can charge in one UTC calendar month, resetting at 00:00 UTC on the 1st. The field appears with auto-reload: leave it empty for no limit, or set at least $10.
Manual top-ups don't count toward the limit and are never blocked. Once a limit is set, Behavior at limit chooses what happens when the next reload would cross it:
| Behavior | What happens |
|---|---|
| Hard cap | Pullfrog refuses the reload and emails you. Runs keep spending the credit already in the wallet. At $0 they stop until you raise the limit, top up by hand, or the month resets. |
| Alert only | The reload goes through, and Pullfrog emails you |
From the CLI
The CLI sets the same values on the organization:
pullfrog config set billing.auto-reload true --org acme
pullfrog config set billing.reload-threshold-usd 20 --org acme
pullfrog config set billing.reload-amount-usd 100 --org acme
pullfrog config set billing.monthly-limit-usd 500 --org acme
pullfrog config set billing.limit-mode hard_cap --org acme
