Create and rotate API keys

Use JWT bearer auth to manage API keys. Use the created API keys for most API, SDK, and MCP workflow calls.

Prerequisites

• A user session that can call the JWT-only API key endpoints.
• A clear scope plan for the integration, such as read, write, search, or admin.

Create a key

curl -X POST https://playground-api-stg-udk7d32fva-uc.a.run.app/api/v2/api-keys \
  -H "Authorization: Bearer <jwt>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Search integration",
    "scopes": ["read", "search"],
    "expires_in_days": 90
  }'

Choose scopes deliberately

• search: search and retrieval workflows
• read: list and inspect public resources
• write: create and update workflow resources
• admin: destructive or higher-privilege operations

For MCP configuration generated from the public /mcp/config flow, the platform prefers an active key with at least read-level capability and will create one when needed.

Rotate a key

Rotate a key when:

• the secret may be exposed
• the integration owner changes
• you are following a regular credential rotation policy

Rotation returns a new full secret and revokes the old one.

curl -X POST https://playground-api-stg-udk7d32fva-uc.a.run.app/api/v2/api-keys/key_123/rotate \
  -H "Authorization: Bearer <jwt>"

Revoke or delete

• Revoke when you want the key to remain visible but inactive.
• Delete when the key should be removed entirely.

Use the key in clients

Python SDK:

from videovector import VideoVector

with VideoVector(api_key="sk_live_...") as client:
    runs = client.prompt_runs.list(limit=20)

MCP server:

VIDEOSEARCH_API_KEY=sk_live_... videosearch-mcp