Skip to main content
Securely manage your API keys.

​
How credentials work

Your AI provider API keys are encrypted before being stored in the database. When your container starts, the key is decrypted and injected into your container’s environment. EasyClaw never logs, displays, or transmits your API keys in plaintext after the initial submission.

​
Store a credential

POST /credentials
Content-Type: application/json

{
  "provider": "anthropic",
  "api_key": "sk-ant-..."
}
Supported providers:
ProviderKey prefix
anthropicsk-ant-
openaisk-
googleAI...
openroutersk-or-

​
List credentials

GET /credentials
Returns a list of stored credentials with masked keys: 
[
  {
    "id": "cred_123",
    "provider": "anthropic",
    "key_preview": "sk-ant-...7x2m",
    "created_at": "2024-01-15T10:30:00Z"
  }
]

​
Delete a credential

DELETE /credentials/:id
Removes the credential. Your container will no longer be able to use this provider until you add a new key.