Everything distribute.you publishes for a program to read, at an address that does not move: the REST API and its OpenAPI document, the MCP server, the command line client, and the documentation. Every link on this page is a live URL you can request right now.
The API is the surface everything else is built on. The dashboard, the CLI and the MCP server are all clients of it, so there is nothing they can do that you cannot.
operationId and a typed response.Responses carry RateLimit, RateLimit-Policy, RateLimit-Remaining and RateLimit-Reset, and a throttled request answers 429 with Retry-After. Read those headers rather than guessing at a rate.
One scheme: an API key sent as a bearer token. The key begins distrib.usr_ and carries your organisation and user identity, so there is no second header to set and no org id to pass.
Create a key at dashboard.distribute.you/api-keys, or from the API itself with POST /v1/api-keys. A key has no expiry, so revoking it in the dashboard is how you end its access.
Two endpoints need no key at all, because the numbers behind them are published: /v1/costs/platform-prices is the live unit-cost catalogue we buy at, and /v1/public/channels is every acquisition channel that can be sold through, with the sales funnels each one supports.
If you are wiring an agent rather than writing a client, connect the Model Context Protocol server instead of the REST API. It is the supported programmatic surface for acting on a customer's behalf.
Six tools today: distribute_status for who the caller is acting as, distribute_list_brands, distribute_list_campaigns, distribute_campaign_stats for outcomes and cost, distribute_list_workflows, and distribute_suggest_icp to draft an ideal customer profile from a website.
From a shell or a CI job the CLI is the shortest path. It authenticates once with an API key, then reads and changes brands, campaigns, leads, audiences, workflows, runs and billing.
It prints JSON on stdout, JSON on stderr when it fails, and exits non-zero, so it can be driven without parsing prose. distribute ops lists every operation the API has, read from the API itself rather than from a list that can go stale. The package is on npm as @distribute.you/cli.
Start with /llms.txt. It says what distribute.you is, when to reach for it, when not to, and lists every surface on this page in a form you do not have to parse out of HTML.
Every statically served page on this domain also answers as markdown. Send Accept: text/markdown and you get the content without the markup; responses carry Vary: Accept, and a request that accepts neither HTML nor markdown gets a 406 rather than a document it said it could not read.
The common one is reporting: pull campaign outcomes and their cost into whatever your team already looks at, so the acquisition numbers sit beside the rest of the business instead of in another tab. Our own published numbers come from the same endpoints.
The other is starting campaigns from somewhere else. If you already know a customer's website, a brand and a campaign can be created without anyone opening the dashboard. Pricing and how the budget is charged are on the pricing page, and the agency model behind it is on the about page.
If something here is missing or wrong, write to [email protected]. The people who answer are the people who build it.