Skip to content

API Keys

API keys route your requests through TrustedRails's proxy layer, which forwards them to the inference network and returns responses in OpenAI-compatible format.

Your app → Proxy → GPU Network → Response
  1. Your application sends a request using the OpenAI API format
  2. TrustedRails receives it and forwards it to the GPU network
  3. The inference runs on available GPUs
  4. The response is returned to your app in standard OpenAI format

From your application's perspective, this is identical to calling the OpenAI API.

API keys support the OpenAI Chat Completions API, including:

  • Chat completions (/v1/chat/completions)
  • Streaming responses (stream: true)
  • System, user, and assistant messages
  • Temperature, top_p, max_tokens, and other standard parameters
  • Tool calling (tools, tool_choice)

See API Compatibility for the full list of supported endpoints and parameters.

All requests go to:

https://proxy.trustedrails.com/v1

Set this as the base_url (Python) or baseURL (JavaScript) in your OpenAI client configuration.

| Use case | Works? | |---|---| | Replacing OpenAI in existing code | Yes | | Using LangChain, LlamaIndex, or similar frameworks | Yes | | Using Cursor, Continue, or other AI-powered dev tools | Yes | | Any tool that supports OpenAI-compatible API | Yes |

  • Your key secret starts with tr-prx- and should be treated like any API credential
  • TrustedRails does not log or store your prompts and completions
  • If a key is compromised, rotate it immediately — this invalidates the old secret and issues a new one