Enterprise feature
Enterprise admins can issue team-scoped gateway keys, restrict provider access, and log LLM API calls under the right organization and team.
Control point
Issue a key to a backend team, data team, or product service without exposing the upstream provider secret.
Allow a team to use all configured providers, or narrow access to one provider and a small model set.
Keep OpenAI, Azure OpenAI, Anthropic, and Gemini credentials controlled by the organization.
Store request metadata, response status, model, duration, token counts, and gateway key metadata as proxy sessions.
How it is used
01
An enterprise admin stores provider credentials once for the organization.
02
The admin creates gateway keys for teams and chooses which providers or models each key can use.
03
Applications call https://proxy.reclaimllm.com/<org-slug>/v1 with the team gateway key instead of a provider key.
04
Gateway calls are logged under the organization and team for enterprise admins and team leads.
Setup path
The team key is not an OpenAI, Anthropic, Gemini, or Azure OpenAI key. It is a ReclaimLLM gateway key that authorizes access according to the organization's configured provider policy.
That keeps provider credentials server-side while still giving developers and services a normal API-shaped integration path.
Model naming contract
Clients must send LiteLLM-prefixed model IDs. gpt-5.6-luna alone returns 422; use openai/gpt-5.6-luna. The org catalog and key allowlist store the bare name after the prefix.
Error responses use FastAPI's {"detail":"..."} body.
Request examples
Use the gateway like an OpenAI-compatible endpoint. The model string must carry the LiteLLM provider prefix — gpt-5.6-luna alone is rejected; use openai/gpt-5.6-luna.
curl https://proxy.reclaimllm.com/acme/v1/chat/completions \
-H "Authorization: Bearer rclm-gw-your-team-key" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-5.6-luna",
"messages": [
{ "role": "user", "content": "Summarize this incident report." }
]
}'Same contract for Moonshot: request moonshot/kimi-k2.6 while the org allowlist stores bare kimi-k2.6.
curl https://proxy.reclaimllm.com/reclaim/v1/chat/completions \
-H "Authorization: Bearer rclm-gw-your-team-key" \
-H "Content-Type: application/json" \
-d '{
"model": "moonshot/kimi-k2.6",
"messages": [
{ "role": "user", "content": "Compare FCF of amazon and microsoft?" }
]
}'Embedding traffic can use the same team gateway key, so retrieval and search pipelines follow the same org policy.
curl https://proxy.reclaimllm.com/acme/v1/embeddings \
-H "Authorization: Bearer rclm-gw-your-team-key" \
-H "Content-Type: application/json" \
-d '{
"model": "azure/text-embedding-small",
"input": ["Searchable context from an LLM session."]
}'Logging
The gateway is not only a pass-through. It creates proxy session records that enterprise admins and team leads can use for review, investigation, and usage analysis.
Current limits
Team-owned provider credentials and separate provider billing by team are not part of the first version.
The gateway becomes part of customer LLM traffic, so uptime and retry behavior matter more than passive capture paths.
Provider APIs differ around streaming, token reporting, responses, and embeddings. Feedback from production edge cases will shape the next pass.
Use team-scoped keys for provider access, then keep request history visible in the same enterprise workspace as the rest of your captured AI activity.