API and MCP · not live yet
Distribution, as a capability your stack can call.
Brands, the network, campaign runs, evidence and results are being built into one system. Today your team works it with us directly. Typed tools your agents can call are not live yet, and you can request early access now. Agents will never get unrestricted access to your money, and autonomous execution will be opt-in, one action class at a time.
In one paragraph
distribution.wtf is a distribution system designed to be called by software as well as people. Once API access opens, a company's agent will be able to create an intent, resolve the audience, request a plan and inventory, create a campaign, route it for approval, execute approved actions, follow status, and retrieve evidence and results. Spend, new terms and publishing will stop for human approval unless policy allows them. Early access requests are open now.
Not live yet: we are building an agent surface of 11 typed tools (per the table below), from create_intent to stop, with approval on spend, terms and publishing. Whoever calls it, the brief is the input: here is what a launch brief should specify, and how teams choose a buying route.
The system
One object model, for people and for agents.
A brand's intent becomes a plan, the plan becomes a campaign run, the run produces evidence, and the evidence rolls up into results. The network supplies and fulfils. Your team works on these objects today; once API access opens, your agents will work on the same ones.
Above the line, not live yet: your agents, through REST, MCP and webhooks, inside your policy.
Brand
Product, ICP, policies
Intent
Audience, objective, budget
Plan
Nodes, allocation, deliverables
Run
State, approvals, actions
Evidence
Asset, timestamp, verified
Results
Delivery and outcome signals
Below the line: the network, which supplies the plan and fulfils the run. Creators, Podcasts, Newsletters, Events, Reddit communities, Media, Partners.
A run, from the agent's side · not live yet
What your agent actually sees.
- 01
Your agent submits the brief: Series A, US AI engineers, $50,000.
- 02
The audience resolves into five distribution categories.
- 03
A ranked plan comes back with an allocation inside the budget.
- 04
Availability and terms are checked for Oct 10 to Oct 24.
- 05
The campaign is created from the plan and the approved assets.
- 06
Spend needs a person. The run waits for jane@company to approve.
- 07
Once approved, placements are booked, briefed and published.
- 08
Every placement returns proof: asset, timestamp, live URL, spend.
The policy it runs under
- Spend limit
- $50,000 per campaign
- Channels
- Creator, podcast, newsletter, event
- Geography
- US only
- Needs a person
- Spend, new terms, publishing
- Runs on its own
- Planning, inventory, status
Where the run is now
- Draft
- Planned
- Approval
- Approved
- Executing
- Live
- Complete
Every run keeps its state. It can pause for approval, resume, block on a person, or stop, and every action lands in an audit log.
Tool surface · not live yet
Eleven tools. Narrow, typed, policy-bound.
Spend, non-standard terms, external publishing and live changes stop for approval; policy pre-authorisation is not live yet.
| Tool | Takes | Returns |
|---|---|---|
| 01Create intent | product, audience, objective, budget, dates, constraints | intent id |
| 02Resolve audience | intent id or audience profile | audience profile + distribution categories |
| 03Plan | intent id + constraints | ranked plan + budget allocation |
| 04Inventory | audience, filter, date, budget | available nodes + terms |
| 05Create campaign | approved plan + assets | campaign id + approval state |
| 06Approve | campaign id + approval token | execution state |
| 07Execute | campaign id | run id + actions |
| 08Status | campaign id or run id | current state + blockers |
| 09Evidence | campaign id | proof bundle |
| 10Results | campaign id | delivery + outcome metrics |
| 11Stop | campaign id | stopped state + reason |
The agent layer
Built for machines, controlled by people.
The same campaign, states and evidence your team sees in the workspace, exposed to your software.
REST API
not live yetStable machine interface for any internal system or agent
MCP server
not live yetDistribution capabilities as tools for compatible agents
Webhooks
not live yetStatus and evidence pushed back to your environment
Agent identity
not live yetKnow which client system started a run
Audit log
not live yetImmutable action and decision history
Example run · not live yet
A brand-side agent ships a launch.
"We are launching Product X. Target US consumers aged 25 to 40 interested in personal productivity. Budget $50K. Launch window October 10 to 24. Use approved creative only. Favour podcast, YouTube, newsletter and creator distribution. Do not spend outside the approved budget."
- 01The agent opens an intent.
- 02distribution.wtf resolves the audience and returns the relevant categories.
- 03The planner assembles inventory and a $50K draft allocation.
- 04Your limits on budget, channels and approved assets are checked.
- 05Only the approvals your policy requires go to a person.
- 06Execution coordinates bookings, assets and publishing.
- 07Every placement records evidence.
- 08Webhooks notify the agent on each state change.
- 09At close, the agent retrieves results and the evidence bundle.
Early access
Connect an agent.
API and MCP access opens to early design partners first. Tell us what your agent does today.