Skip to main content
Agents use standard Pureframe AI API keys. The permissions on the key determine which operations the agent can request.

​
Use a read-only key

Create a separate read_only key for an agent that only needs to search. A read-only key can use search_videos, list_collections, get_collection, and get_video. It cannot use upload_video or other write operations. Create the key from Settings → API Keys. Key management requires an authenticated dashboard session.

​
Understand the scope

An API key can access the resources permitted for its account. You cannot currently restrict a key to selected collections. If an agent must see only a subset of content, place that content in a separate Pureframe AI account and issue a key for that account.
A read-only key limits writes, but it does not prevent an agent from reading sensitive content available to that account.

​
Revocation is immediate

If a key is exposed or an integration behaves unexpectedly, revoke the key from Settings → API Keys. Replace it with a new key only after you identify and correct the exposure.

​
Rate limits apply the same way

Agent tool calls count toward per-key rate limits. Handle 429 responses and cap the number of tool calls your agent can make for one user request. See Rate limits.

​
Remote MCP authentication

The remote MCP endpoint uses a Bearer token in the Authorization header. Store the token in your client’s secret or environment configuration. Do not place it in prompts, logs, or source control.