Orqen Docs

API Reference

Provider keys

Provider endpoints store and manage encrypted upstream LLM credentials. Authenticate these requests with your Orqen API key.

List providers

curl https://api.orqen.app/v1/account/providers \
  -H "Authorization: Bearer sk-orq-YOUR_KEY"

Save a provider key

curl https://api.orqen.app/v1/account/providers \
  -X PUT \
  -H "Authorization: Bearer sk-orq-YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "provider": "openai",
    "api_key": "sk-proj-..."
  }'

Delete a provider key

curl https://api.orqen.app/v1/account/providers/openai \
  -X DELETE \
  -H "Authorization: Bearer sk-orq-YOUR_KEY"

Forwarding behavior

When a chat request uses a model from a connected provider, Orqen decrypts the matching key, injects it into the upstream request, then forwards through the upstream gateway. Your agent only sends the Orqen API key.

For per-request Bedrock credentials, see aws_bearer_token_bedrock, aws_access_key_id, and related fields in the Chat API reference. Those fields are for OpenAI-compatible chat requests, not native boto3converse(). Saving a provider key is the cleaner production path because your agent only needs its Orqen API key.