Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.veri.studio/llms.txt

Use this file to discover all available pages before exploring further.

​
Create API Key

Create a new API key for SDK or direct API access. The full key is returned once — save it immediately.

​
Request

curl -X POST https://api.veri.studio/v1/api_keys \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "production"}'

​
Response

{
  "id": "abc123def456",
  "object": "api_key",
  "name": "production",
  "key_prefix": "vk_a1b2c3d4",
  "key": "vk_a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2",
  "created_at": "2026-04-21T12:00:00Z",
  "last_used_at": null
}
The key field is only included in the creation response. It cannot be retrieved again. If lost, revoke the key and create a new one.

​
List API Keys

List all active (non-revoked) keys for the current user.
​
limit
integer
default:"20"
Maximum number of keys to return.
​
after
string
Cursor for pagination. Pass the ID of the last item from the previous page.

​
Request

curl https://api.veri.studio/v1/api_keys \
  -H "Authorization: Bearer YOUR_API_KEY"

​
Response

{
  "object": "list",
  "data": [
    {
      "id": "abc123def456",
      "object": "api_key",
      "name": "production",
      "key_prefix": "vk_a1b2c3d4",
      "created_at": "2026-04-21T12:00:00Z",
      "last_used_at": "2026-04-21T14:30:00Z"
    }
  ],
  "has_more": false
}
The full key is never returned in list responses — only the prefix for identification.

​
Revoke API Key

Revoke a key immediately. It will stop working on the next request.

​
Request

curl -X DELETE https://api.veri.studio/v1/api_keys/abc123def456 \
  -H "Authorization: Bearer YOUR_API_KEY"

​
Response

{
  "id": "abc123def456",
  "object": "api_key",
  "deleted": true
}

​
Security

  • Keys are prefixed with vk_ for easy identification
  • Only the SHA-256 hash is stored — plaintext is never persisted
  • last_used_at is updated on every API request
  • Revoked keys are kept in the database for audit but immediately stop authenticating
  • Store keys in environment variables or ~/.veri/credentials.json (created by veri login)