Resolve LLM Credential (M2M)
Resolve a registered LLM provider's config plus a decrypted API key for it. Authenticated with a BundleAccessToken - the same deployment token agent-runtime already mints for MCP tool access - never a Keycloak JWT. Decrypted key material must never be reachable from a browser-held user token. When agent_id is given, the credential is resolved for that agent's own org and its own binding (never the deployment token owner's personal key) - a member's personal key must never authenticate an org-owned agent's conversation. Omitting agent_id resolves for the deployment token owner instead, for callers that have no agent context (e.g. bundle router-config LLM resolution).
Authorization
BundleAccessToken AuthorizationBearer <token>
In: header
Path Parameters
provider_name*Provider Name
Query Parameters
agent_id?|null
Response Body
application/json
application/json
curl -X GET "https://example.com/v1/bundler/llm-credential/string"{ "provider_id": "fe3d49af-4061-436b-ae60-f7044f252a44", "name": "string", "type": "openai-compatible", "model": "string", "endpoint": "string", "api_key": "string", "temperature": 0, "max_tokens": 0, "timeout_ms": 0, "metered": false}Empty
Empty
{ "detail": [ { "loc": [ "string" ], "msg": "string", "type": "string" } ]}