API keys
A personal API key lets your code call the Model Gateway. Keys start with vcpk_, belong to the person who created them, and never carry the admin role.
These endpoints need a Keycloak access token. An API key cannot be used to list, create or revoke keys, including itself.
Create a key
/api-keysCreates a key that belongs to you and returns it. This is the only time the full key is returned. Orchestrate stores only its hash.
Body
namestringoptionalResponse fields
idstringoptionalnamestring or nulloptionalprefixstringoptionalcreated_atstringoptionalkeystringoptionalResponses
List your keys
/api-keysYour own keys, newest first, with id, name, prefix, created_at and revoked_at. The key itself is never returned.
Revoke a key
/api-keys/{key_id}Revokes a key. It stops working on the next request. The key's record is kept, with the time it was revoked. You can revoke your own keys. A platform admin can revoke anyone's.
Responses
id and revoked_at.Rotate a key
POST /api-keys/{key_id}/rotate with {"overlap_hours": 24} (0 to 720) gives your key a new secret, returned once, and keeps its id, name, limits and scopes. The old secret works until the overlap ends. See Usage, limits and prices.
Project keys for the Agent API are on the Agent API page, and agent keys on A2A and agent keys.