Supported providers
Choose a supported Pi provider, model, and authentication method for an audit.
Loading documentation…
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 type | auth-type | Credential |
|---|---|---|
| Pi API-key provider | api-key | Provider API key in auth-token. |
| GitHub Copilot | oauth | A valid Copilot access token in auth-token. |
| OpenAI Codex | oauth | A valid Codex access token in auth-token. |
| Amazon Bedrock | aws | Ambient AWS credentials on the runner. |
| Amazon Bedrock | bedrock-bearer | Bedrock bearer token in auth-token. |
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.
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.
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.
Every normal audit must include:
auth-token is optional only for auth-type: aws. See the full
input reference for all
options.