> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redpill.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Coding Agents

> Choose a RedPill coding-agent integration and understand its verification boundary.

Pi and OpenCode have native RedPill providers. Other coding agents can call the API through their
standard provider configuration, but do not verify ACI locally.

| Tool                                                         | Integration                 | Local ACI verification         |
| ------------------------------------------------------------ | --------------------------- | ------------------------------ |
| [Pi](/guides/integrations/coding-tools/pi)                   | `pi-provider-redpill`       | Yes, automatic and fail closed |
| [OpenCode](/guides/integrations/coding-tools/opencode)       | `opencode-provider-redpill` | Yes, automatic and fail closed |
| [Claude Code](/guides/integrations/coding-tools/claude-code) | Messages base URL           | No                             |
| [Codex CLI](/guides/integrations/coding-tools/codex-cli)     | Responses provider          | No                             |
| [Cline](/guides/integrations/coding-tools/cline)             | OpenAI-compatible provider  | No                             |

## Native providers

Pi and OpenCode use the same ACI provider core while leaving installation, credentials, model
selection, persistence, and lifecycle to the host. Both integrations:

* verify a fresh TDX attestation and bind TLS to the attested keyset before model traffic;
* discover the live TEE model catalog;
* require verified upstream serving;
* verify each signed receipt and cited session before the response completes; and
* fail closed when a required check fails.

RedPill currently accepts API keys. Use the host's login command to persist a key, or set
`REDPILL_AI_API_KEY` for one process.

The latest 32 receipt-bearing exchanges are retained in memory for inspection and cleared when the
agent exits. Gateway receipts and sessions follow the server's retention policy.

## API-compatible providers

A custom base URL sends requests through RedPill, but cannot inject an attested TLS transport. Use
this path when API compatibility is sufficient:

```bash theme={null}
export REDPILL_AI_API_KEY="YOUR_API_KEY"

curl -s https://api.redpill.ai/v1/models \
  | jq -r '.data[] | select((.supported_features // []) | index("tools")) | .id'
```

For autonomous coding, choose a live model that declares `tools` and test one tool call before
unattended use. Use `tee.redpill.ai` only with an `is_tee: true` model when standard upstreams must
be rejected.

## Supporting another agent

A native adapter needs official hooks for a provider-scoped `fetch`, credentials, dynamic models,
and lifecycle. Without those hooks, changing the base URL cannot bind TLS to an attested workload.