distribute.you Authentication

1. Create an account

Sign up at dashboard.distribute.you to get started.

2. Get your API key

After signing in, go to API Keys and create a new key. A key looks like this:

distrib.usr_xxxxxxxxxxxxxxxxxxxxxxxx

Keep this key secret. It grants full access to your organization. Issue and revoke keys at https://dashboard.distribute.you/api-keys.

3. Send it

The key is a Bearer token in the Authorization header. It already carries your org and your user, so no other identity header is needed.

Authorization: Bearer distrib.usr_YOUR_KEY

REST API

curl https://api.distribute.you/v1/me \
  -H "Authorization: Bearer distrib.usr_YOUR_KEY"

MCP server

The MCP server is hosted at https://mcp.distribute.you/mcp and takes the same header. From Claude Code:

claude mcp add --transport http distribute https://mcp.distribute.you/mcp --header "Authorization: Bearer distrib.usr_YOUR_KEY"

Command line

The CLI authenticates once with the same key and then reads and changes brands, campaigns, leads, audiences, workflows, runs and billing. It is on npm as @distribute.you/cli.

npx @distribute.you/cli --help

4. Verify

Test the key with one call:

curl https://api.distribute.you/v1/me \
  -H "Authorization: Bearer distrib.usr_YOUR_KEY"

You should see your user id and organization id. A 401 means the header is missing, the scheme is not Bearer, or the key is not one of yours: a key always starts with distrib.usr_, and a placeholder such as distrib.usr_YOUR_KEY is not a key.

Security

• A key is scoped to one organization
• Never commit a key to version control
• Use environment variables for local development
• Rotate keys periodically from the dashboard
• You can create several keys and revoke them individually

Every developer surface is named together at https://distribute.you/developers.