Skip to main content
Pullfrog runs on your API keys — you bring a key from any supported provider, and Pullfrog uses it to power agent runs in your GitHub Actions environment. You control the provider, the spend, and the data.

​
Setup

Add your key as a GitHub secret, then map it into the pullfrog.yml workflow so the agent can access it at runtime.

​
1. Add the secret to GitHub

We recommend org-level secrets — add the key once and every repo in the org can use it. For personal accounts or single-repo setups, a repo secret works too. Org secret (recommended):
  1. Go to github.com/organizations/your_org/settings/secrets/actions
  2. Click New organization secret
  3. Set the name to your provider’s env var (see supported providers)
  4. Paste your API key as the value
  5. Under Repository access, choose which repos can use it
  6. Click Add secret
Repo secret (single repo):
  1. Go to github.com/your_org/your_repo/settings/secrets/actions
  2. Click New repository secret
  3. Set the name to your provider’s env var
  4. Paste your API key and click Add secret

​
2. Map the secret in pullfrog.yml

The secret must be explicitly passed to the action via the env: block. If it’s only in GitHub secrets but not in the workflow env, the agent won’t be able to access it. 
 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 }}
Comment out or remove any providers you don’t use. You only need one key.

​
Free models

Several models are completely free and work out of the box with zero configuration:
  • Big Pickle (OpenCode)
  • GPT Nano (OpenAI)
  • MiMo V2 Pro (Moonshot AI)
  • MiniMax M2.5 (MiniMax)
  • Nemotron 3 Super (NVIDIA)
Select any of these in the model selector and skip the key setup entirely.

​
Open source program

Open source maintainers can apply for free access to premium models. 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.

​
Troubleshooting

“Missing API key” error in GitHub Actions The agent couldn’t find a valid key at runtime. Check that:
  1. The secret exists in your repo or org settings
  2. The secret name matches the provider’s env var exactly (e.g. ANTHROPIC_API_KEY)
  3. The secret is mapped in your pullfrog.yml env: block
“Missing API key” in the Pullfrog console The console checks whether the required secrets exist in your repository. Click Re-check after adding secrets, or verify the secret names match.