Skip to main content
Pullfrog has its own billing system, so you don’t have to wire up Stripe, manage provider keys, or assemble a credit-card setup of your own. Add a card once in the console, and Pullfrog handles runs, model access, and invoicing in one place.

​
The plan

One plan, pay-as-you-go.
  • Free tier — every account gets 30 free runs per month. No card required.
  • Pay-as-you-go — add a card and runs are unlimited at $0.07 each, billed monthly in arrears. Failed runs are free.
If you hit the free-tier cap with no card on file, additional dispatches are paywalled until you add one. Existing runs in the month complete normally.
Beta offer — $10 in free Router credit. While Pullfrog is in beta, every account can claim $10 of Pullfrog Router credit — open the Router tab in the dashboard (no card required). Use it on any supported model — usage is billed at the provider’s rate with no platform markup, and your runs stay free until you exceed the monthly cap.
Router signup credit modal

​
Enabling billing

Open your account or organization console at pullfrog.com/console/<account> and find the Billing card. Click Enable billing to add a payment method via Stripe — you’ll come back to the console with billing turned on.
Pullfrog billing card in the org console
The Billing card shows your plan, runs used this month, payment methods on file, and the billing email Stripe sends invoices to. Use Update billing to manage cards, the billing email, or download invoices via the Stripe Customer Portal.
Billing is configured per account (personal account or GitHub organization). Only org admins can change billing settings; non-admins see a read-only “ask an admin” message.

​
Pullfrog Router

Pullfrog Router is a managed model backend that fronts every major LLM provider through a single billing account. With the Router, you don’t need to manage provider keys at all — Pullfrog mints a short-lived proxy key for each run and bills model usage at raw OpenRouter cost (no markup).
Pullfrog Router tab in the Model costs card
In the Model costs card, switch between two modes at any time:
  • Pullfrog Router (recommended) — Pullfrog handles model access. The agent picks up the right credentials at dispatch; you only see the wallet balance and per-run cost on the dashboard.
  • BYOK — Bring your own provider keys. See BYOK for setup.
The mode is account-wide and can be flipped without changing your runs billing plan.

​
Auto-reload

Auto-reload is opt-in. When enabled, Pullfrog tops up your Router balance automatically whenever it drops below your configured threshold, so you don’t have to babysit credits between runs.
Auto-reload toggle, amount, and threshold in the Model costs card
Two knobs:
  • Auto-reload threshold — the balance that triggers a reload (e.g. $10). When the wallet drops below this, Pullfrog charges your card and tops up.
  • Auto-reload amount — how much to add each time (e.g. $50). The full amount is credited to the wallet; Stripe’s processing fee is grossed up on the charge so your wallet sees the net.
If auto-reload is off and the wallet runs dry, runs that would have used the Router fail with a clear “add credit” message in the PR comment, and the agent surfaces the dashboard link directly.

​
Monthly spend limit

Org admins can configure a per-account ceiling on how much Pullfrog Router will auto-reload in any UTC calendar month. The cap resets at 00:00 UTC on the 1st. Useful as a safety net against runaway agent loops, stuck workflows, or a leaked PR trigger spending more than you meant to. The cap is optional — running without one is the default. Two modes:
  • Hard cap — once the next auto-reload would push past the limit, that reload is refused. Your wallet keeps draining on subsequent runs (you still have access to the credit you’ve already paid for), but new top-ups are blocked until you raise the cap or the next UTC month starts.
  • Alert-only — auto-reloads keep flowing; we email the billing admin the first time a reload pushes you over the limit each month. Treat it as a soft tripwire.
Set the cap from the Monthly spend limit field on the Model costs card, alongside auto-reload amount and threshold. Leave the field empty for no limit. The field is only visible once auto-reload is on (i.e. you’ve enabled billing and turned auto-reload on). Once a number is in the field, a Behavior at limit toggle appears for choosing hard cap vs alert only. The cap can also be set via PATCH /api/account/<owner>/billing/settings with routerMonthlyLimitUsd (number in dollars, or null to clear) and routerLimitMode (hard_cap or alert_only). Manual top-ups at /billing-top-up/<owner> are unrelated to the cap — you’re clicking through Stripe Checkout yourself, so we treat them as deliberate spend and never block them.

​
Free models

A handful of models are available at no cost on either plan:
  • Big Pickle (OpenCode)
Pick it in the model selector and you skip both Router credit usage and BYOK setup entirely. Runs still count against your monthly cap on the free tier.

​
Open source program

Open source maintainers can apply for free access to premium models via Pullfrog Router, with no monthly cap on runs. If you maintain a public repository, reach out to support@pullfrog.com with:
  • A link to your repository
  • A brief description of how you’d use Pullfrog
We review applications on a rolling basis.

​
Enterprise

Pay-as-you-go scales to most teams without a conversation. For enterprise needs — SSO, audit logs, RBAC, SOC 2 / HIPAA, SLAs, committed spend, on-prem — contact sales@pullfrog.com.