1. Documentation
  2. Providers
  3. Supported providers
ReadmeMarketplaceGitHub
  • Introduction
  • Quickstart
  • Supported providers
  • API-key providers
  • GitHub Copilot
  • OpenAI Codex
  • Amazon Bedrock
  • Action inputs
  • Reporting and severity
  • Audit lifecycle
  • Incremental audits
  • Safety boundaries
  • Troubleshooting

Supported providers

Choose a supported Pi provider, model, and authentication method for an audit.

Loading documentation…

Quickstart< PreviousAPI-key providersNext >

Powered by heyo

On this page

Pi compatibilityChoose an authentication methodRequired inputs

Heyo Code Audit uses the Pi version bundled in the released Action. Choose a Pi provider identifier, an explicit model identifier, and the authentication method required by that provider. The Action does not select a model for you.

Provider typeauth-typeCredential
Pi API-key providerapi-keyProvider API key in auth-token.
GitHub CopilotoauthA valid Copilot access token in auth-token.
OpenAI CodexoauthA valid Codex access token in auth-token.
Amazon BedrockawsAmbient AWS credentials on the runner.
Amazon Bedrockbedrock-bearerBedrock bearer token in auth-token.

Pi compatibility

The Action includes Pi's provider catalog, rather than the local Pi installation on a developer machine. It does not read ~/.pi/agent/auth.json, run /login, load models.json, or load Pi extensions and skills. Configure credentials in GitHub Actions and use a provider supported by the Pi version bundled in the Action release.

Pi publishes the broad catalog and provider-specific model details in its provider documentation. For the exact Action contract, provider, model, and auth-type are checked before the audit starts.

Choose an authentication method

Use API-key providers for standard provider keys, including OpenAI, Anthropic, Google, OpenRouter, Cloudflare AI, Groq, Mistral, xAI, DeepSeek, and Cerebras. Use the dedicated guides for GitHub Copilot, OpenAI Codex, or Amazon Bedrock.

Keep credentials in GitHub Secrets

Pass credentials from secrets, never literal workflow values. Do not print the token, include it in a model prompt, or store it in the repository.

Required inputs

Every normal audit must include:

yaml
with:  provider: openai  model: gpt-5.4  auth-type: api-key  auth-token: ${{ secrets.OPENAI_API_KEY }}  github-token: ${{ github.token }}

auth-token is optional only for auth-type: aws. See the full input reference for all options.