REA Agents
One chat door for your agents.
Twelve agents. One address, https://api.reacontrolplane.com/v1. You bring a REA key and your own model key. The field name changes by product. The door does not.
Agents
Path · Chat · https://api.reacontrolplane.com/v1
- HermesCustom provider. The base URL ends in /v1.
- ClineOpenAI Compatible. The step-by-step gallery.
- ContinueOpenAI-compatible provider. The base is apiBase.
- CursorChat only. Tab completion stays on Cursor.
- OpenCodebaseURL in opencode.json. A header, or the combined key.
- Kilo CodeOpenAI Compatible. Optional headers, or the combined key.
- Roo CodeopenAiBaseUrl, and the combined key.
- AiderOPENAI_API_BASE, and the combined key.
- Goosebase_url, and the combined key.
- Qwen CodebaseUrl, and the combined key.
- Zedapi_url, and the combined key.
- PibaseUrl, and the combined key.
Two ways to send the vendor key. A tool with one API-key field and no custom header uses the combined key rea_YOUR_REA_KEY.YOUR_VENDOR_KEY. A tool that can set a header sends X-Upstream-Api-Key and uses the REA key alone. If you send both, the combined key is the one that is forwarded.
A product with no base-URL field never reaches REA. Claude.ai, ChatGPT, and Google sign-in are refused. Use an API key from the vendor's console.
Claude Code, Codex CLI, and Gemini CLI are not on this door. They are on CLIs. The model table is on Set up.