Authentication

There are two ways in. Use OAuth when your client supports it, and an API key when it doesn't.

#OAuth

Add the server URL to your client. It opens ReelFarm, you sign in with Google and click Allow.

https://reel.farm/api/v2/mcp

#For client developers

ReelFarm follows the MCP authorization spec, so standard MCP clients discover everything on their own.

• A request without credentials gets 401 with a WWW-Authenticate header pointing to /.well-known/oauth-protected-resource.
• Authorization server metadata is at /.well-known/oauth-authorization-server.
• Dynamic client registration at /api/oauth/register, or a client ID metadata document.
• Authorization code flow with PKCE (S256). Public clients only, no client secret.
• The access token is sent as a Bearer token, like an API key.

#API key

For clients without MCP sign-in. Keys start with rf_.

#Get your key

1. 1

   Sign in to ReelFarm

   reel.farm/a/setup
2. 2

   Pick your agent

   Agents that need a key show it, ready to copy, in their steps.
3. 3

   Or manage keys yourself

   Settings → API Keys lists your keys. Create or revoke them there.

#As a Bearer header

The preferred way, when your client can send headers.

POST https://reel.farm/api/v2/mcp
Authorization: Bearer rf_your_api_key
Content-Type: application/json

#In the URL

For clients that only take a URL.

https://reel.farm/api/v2/mcp?key=rf_your_api_key

#Plans and the free trial

• Connecting and listing tools work on any account.
• Tool calls need the free trial or a plan. Without one they fail with NO_ACTIVE_PLAN, and your agent tells you why.

See Limits and pricing.