API keys

Pullfrog runs on your own API key (BYOK, bring your own key) for every supported provider, and for providers with no console card through GitHub Actions secrets. You keep your provider relationship, rate limits and billing, and pay the provider directly at its prices. To run on a Claude, ChatGPT, Grok, Kimi or OpenCode Go plan you already pay for, see your existing subscription. To skip keys entirely, see Pullfrog Router.

Key storage

Where	Set it in	Scope
Pullfrog secrets (recommended)	The Pullfrog console	The account, or one repository
GitHub Actions secrets	GitHub, then the workflow `env:` block	The workflow

You can mix the two per provider. If a key is set in both, the workflow value wins, so a workflow can override a stored key.

Pullfrog secrets

Pullfrog encrypts stored keys at rest, injects them into each run, and never writes them to your repository or workflow files. No workflow edits are needed.

Open pullfrog.com/console/<account> and find the Providers section of the Billing card.
Select the BYOK tab.
Click Set up on the provider’s card and follow its credential instructions.

The Providers section of the Billing card on the BYOK tab

The Add secret modal scopes a secret to the whole account or to one repository:

Add secret modal in the Pullfrog console

Every repository inherits the account’s secrets. A repository secret with the same name overrides the account one for that repository only. On an organization, only owners can open the Billing card. Repository admins manage keys for their repository in the Secrets section of the repository console, where inherited account secrets appear read-only:

GitHub Actions secrets

Keep keys in GitHub when you already rotate secrets there. Pullfrog reads them from the workflow env: block.

Add the secret in GitHub, at the organization (github.com/organizations/<org>/settings/secrets/actions, New organization secret) or the repository (github.com/<org>/<repo>/settings/secrets/actions, New repository secret).

Map it into pullfrog.yml:

 jobs:
   pullfrog:
     runs-on: ubuntu-latest
     steps:
       - name: Run agent
         uses: pullfrog/pullfrog@v0
         with:
           prompt: ${{ inputs.prompt }}
+        env:
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}

Any variable in env: reaches the agent, so a provider with no console card runs from a GitHub Actions secret too. See custom providers.

Cloud providers and custom endpoints

These routes are BYOK only and have their own setup pages:

Route	Use it for
Amazon Bedrock	Inference through your AWS account, with pinned model IDs
Google Vertex AI	Inference through your Google Cloud project, with pinned model IDs
Azure OpenAI	Your Azure deployments, billed to your Azure subscription
OpenAI-compatible endpoints	A LiteLLM proxy, a self-hosted vLLM server, or any gateway that speaks chat completions

Multiple subscriptions and fallback

Connect several Claude, Codex or Grok subscriptions by running the provider’s auth command again. Choose Add another to keep the existing connections as fallbacks, or Replace to swap one out once the new connection succeeds.

npx pullfrog auth claude --org my-org
npx pullfrog auth codex --repo my-org/my-repo
npx pullfrog auth grok --org my-org

Each subscription card lists its connected accounts; Claude connections show the end of the setup token, and Codex and Grok connections show the account email when available. The pencil removes a connection or copies the command to add another. After a run checks a connection, its card shows Rejected if the provider refused it, or Limit reached with the reset time when the provider gives one. Before the agent starts, Pullfrog tries the credentials for the run’s model and provider in this order:

Subscriptions: the workflow’s, then the repository’s, then the account’s, then shared personal ones
API keys: the workflow’s, then the repository’s, then the account’s

Within a scope, the most recently connected subscription goes first. A rejected or exhausted credential moves the run to the next one, so a fallback to an API key can incur API charges. If a provider cannot answer the check, Pullfrog keeps the current credential. Once the agent has started, Pullfrog does not switch credentials or models.

Checks for some providers send a small inference request. A passing check does not reserve quota or guarantee the whole run fits within the limit.

Personal subscriptions on organization repositories

The owner of a personal account can share one of its subscriptions with an organization or repository they also manage:

npx pullfrog auth list --org my-username
npx pullfrog auth share CREDENTIAL_ID --from my-username --repo my-org/my-repo
npx pullfrog auth unshare CREDENTIAL_ID --from my-username --repo my-org/my-repo

The list prints a binding ID for auth remove and a credential ID for auth share and auth unshare. Removing the connection from the personal account revokes its shares. Nothing is shared automatically because someone triggered a run.

Gateways and proxies

Route a provider’s requests through your own host, such as a LiteLLM proxy, a corporate egress proxy or an AI gateway, while keeping your normal model selection. Set the base URL under Set up a proxy or gateway on the provider’s setup card, or in your workflow env::

Provider	Variable
Anthropic	`ANTHROPIC_BASE_URL`
OpenAI	`OPENAI_BASE_URL`

Put only the host in the base URL; a credential embedded in it is not treated as one. Pullfrog skips its pre-run credential check for a gateway, so a gateway that refuses the credential reports its own error in the run.

Other providers take other routes. Azure OpenAI builds its endpoint from AZURE_RESOURCE_NAME, and a gateway with its own model list belongs on OpenAI-compatible endpoints.

Anthropic

Anthropic models run through Claude Code, which honors ANTHROPIC_BASE_URL natively and talks to the gateway in Anthropic’s own format, so prompt caching and extended thinking survive the hop.

env:
  ANTHROPIC_BASE_URL: https://gateway.internal.example.com
  ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}

Pick the credential variable by the header your gateway reads. The ANTHROPIC_API_KEY variable is sent as x-api-key, and ANTHROPIC_AUTH_TOKEN as Authorization: Bearer. A gateway that reads the other header answers 401.

env:
  ANTHROPIC_BASE_URL: https://gateway.internal.example.com
  ANTHROPIC_AUTH_TOKEN: ${{ secrets.GATEWAY_TOKEN }}

This route serves Claude models only. Anthropic doesn’t support routing Claude Code to non-Claude models through a gateway, so use OpenAI-compatible endpoints for a provider’s /anthropic endpoint that serves its own models.

OpenAI

The OPENAI_BASE_URL variable re-points the OpenAI provider, which speaks the Responses API (POST /v1/responses). Point it at a gateway that serves that endpoint.

env:
  OPENAI_BASE_URL: https://gateway.internal.example.com/v1
  OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}

Most third-party gateways speak the older Chat Completions API (POST /v1/chat/completions), which is what “OpenAI-compatible” usually means. For one of those, use OpenAI-compatible endpoints instead.

Troubleshooting

”Missing API key” error in GitHub Actions

The agent found no valid key at runtime. Check, in order:

The selected model’s env var is set in Pullfrog secrets or in a workflow env: mapping.
The secret name matches the provider’s env var exactly: ANTHROPIC_API_KEY, not CLAUDE_API_KEY.
A GitHub secret is mapped in the env: block of pullfrog.yml. GitHub Actions injects only what the workflow lists.

”Missing API key” warning in the console

The console found no stored key for the selected model. Add one under Providers on the Billing card, or switch to a model whose key you already have.

Get started

Working with Pullfrog

Models and billing

Administration

Reference

Key storage

Pullfrog secrets

GitHub Actions secrets

Cloud providers and custom endpoints

Multiple subscriptions and fallback

Personal subscriptions on organization repositories

Gateways and proxies

Anthropic

OpenAI

Troubleshooting

”Missing API key” error in GitHub Actions

”Missing API key” warning in the console

​Key storage

​Pullfrog secrets

​GitHub Actions secrets

​Cloud providers and custom endpoints

​Multiple subscriptions and fallback

​Personal subscriptions on organization repositories

​Gateways and proxies

​Anthropic

​OpenAI

​Troubleshooting

​”Missing API key” error in GitHub Actions

​”Missing API key” warning in the console

Key storage

Pullfrog secrets

GitHub Actions secrets

Cloud providers and custom endpoints

Multiple subscriptions and fallback

Personal subscriptions on organization repositories

Gateways and proxies

Anthropic

OpenAI

Troubleshooting

”Missing API key” error in GitHub Actions

”Missing API key” warning in the console