> ## 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.

# Agent Runtimes

> Choose a long-running agent runtime and connect its main model to RedPill

OpenClaw and Hermes run persistent, tool-using agents. [Private AI Proxy](/get-started/private-ai-proxy)
connects both from its Agents screen; the pages below also show the manual provider configuration,
which differs per runtime.

| Runtime                                            | Provider name    | Selected model         |
| -------------------------------------------------- | ---------------- | ---------------------- |
| [OpenClaw](/guides/integrations/runtimes/openclaw) | `redpill`        | `redpill/z-ai/glm-5.2` |
| [Hermes](/guides/integrations/runtimes/hermes)     | `custom:redpill` | `z-ai/glm-5.2`         |

<CardGroup cols={2}>
  <Card title="OpenClaw" icon="robot" href="/guides/integrations/runtimes/openclaw">
    Add a RedPill provider to the OpenClaw gateway configuration.
  </Card>

  <Card title="Hermes" icon="robot" href="/guides/integrations/runtimes/hermes">
    Define and select a named RedPill provider in Hermes.
  </Card>
</CardGroup>

## Shared boundary

These configurations route the main text and tool-calling loop through RedPill. Features that use
separate image, speech, realtime, embedding, search, or browser providers do not automatically use
RedPill.

Choose a model that declares `tools` in [`GET /v1/models`](/api-reference/models). Use
`https://tee.redpill.ai/v1` only with an `is_tee: true` model when every main-model request must
reject standard upstreams.