Your coding workflow does not need a new interface to use PrimeRouter. The important change happens before a request leaves your computer: your tool calls an open-source local client, which verifies the remote program and encrypts content.
Keep the tool, change the endpoint
The local client exposes OpenAI- and Claude-compatible API endpoints. Tools that support a custom API URL can keep their familiar workflow:
Codex / Claude Code
-> local PrimeRouter client
-> verified encrypted session
-> PrimeRouter program in a trusted execution environment
-> selected upstream model
Compatibility does not mean every tool uses the same URL or request format. Copy the local endpoint for the protocol your tool supports from the client. Use the port and model names shown by your own client and account.
A reliable setup sequence
- Sign in to PrimeRouter and obtain the companion open-source client.
- Create a local API key in the client for tools on your computer.
- Configure the tool with the client's compatible API URL and that local key.
- Select a model allowed by your account and key policy, then send a minimal request.
- Confirm that remote verification succeeds and the tool receives a model response.
Do not store your platform key or upstream account credentials in a third-party tool's project settings. Connect the tool to the local endpoint with a client-issued local key.
Diagnose the right layer
| Check | First question |
|---|---|
| Tool settings | Does the API URL point to the local client, and is the protocol correct? |
| Local client | Is it running, has verification passed, and is the local key usable? |
| Model policy | Does this account and key permit the selected model and channel? |
| Upstream call | If the first three checks pass, what upstream error does the client show? |
Separating these layers is more useful than repeatedly changing model names or copying someone else's port. See Connect your tools for the setup flow.