Agentic distribution infrastructure
Distribution infrastructure for technology companies.
Tell us what you are shipping, who needs to care and what you want to achieve. We plan it across a curated network, run it, and prove every placement.
Built for humans. Callable by agents next, in V1B, through API and MCP.
What you are looking at
One sentence of intent becomes an audience, a set of network nodes, a budgeted plan and an approval gate. Nothing is booked or spent until you sign off.
- Audience
AI engineers · United States · builders at startups and labs
creatorsnewsletterspodcastseventscommunities - Nodes
- Applied ML explainerYouTube · 180K ML engineers
- AI engineering digestPrimary slot · 64K subs
- Infra founders podcastHost-read · 40K / ep
- AI builders night, SFDemo slot · 300 builders
- Platform engineering communityAMA · 12K members
- Plan
$50,000 · 5 channel types · Oct 10 to Oct 24 · 23 placements proposed
- Executionawaiting approvalpolicy: spend ≤ $50K · approved creative only
In one paragraph
distribution.wtf is distribution infrastructure for technology companies. You describe the product, the audience that needs to care, the objective and the budget. We build a distribution plan across a curated network of creators, podcasts, newsletters, events, communities, media and partners, run it with your approval, and return evidence for every placement. In V1B your own agents will call the same workflow through an API and MCP.
Per our V1 product spec, the network runs across 7 lanes and the agent surface is 11 typed tools, from create_intent to stop.
What happens here
One brief. One budget. One distribution network.
- 01
Your input
product + audience + objective + budget
productaudienceobjectivebudget - 02
Plan
a mix you can read and approve
- 03
Network
the nodes that reach them
- 04
Execution
booked, briefed, published
bookedbriefedlive - 05
Evidence
proof for every placement
✓ asset✓ timestamp✓ live URL✓ spend - 06
Outcomes
what the campaign moved
deliverysignupspipeline
Built for technology companies
Your company is technical. Your audience does not have to be.
SaaS, AI, consumer tech, infrastructure, cybersecurity, fintech, hardware and deep tech. The brief defines who needs to care, and the plan reaches them wherever they are.
Built for the moments that matter
- Funding announcement
- Product launch
- Major release
- Category entry
- Market expansion
- AI agentConsumers, professionals, teams, developers
- Productivity SaaSConsumers, SMBs, startups, enterprises
- Fintech appConsumers, SMBs, finance teams, enterprises
- DevToolDevelopers, engineering teams
- CybersecurityConsumers, security teams, IT teams, CISOs
- RoboticsConsumers, industrial buyers, engineers, researchers
- AI infrastructureDevelopers, ML teams, enterprises
- Consumer AIMass-market consumers, prosumers
- Hardware startupConsumers, enthusiasts, professionals, enterprises
- Deep techResearchers, engineers, industrial buyers, enterprises
The problem is coordination
Channels are everywhere.
Coordinating them is the job nobody has.
Every creator, show, newsletter, community and event runs its own contract, price, timeline and report. A launch across ten of them is ten relationships, and none of the numbers line up.
| Counterparty | Contract | Pricing | Timeline | Reporting |
|---|---|---|---|---|
| Creator one | DM + PDF | Flat fee | 2 weeks | Screenshots |
| Creator two | Talent manager | CPM + usage | 5 weeks | Native stats |
| Podcast | Network IO | CPM, 3-ep min | 6 weeks | Download est. |
| Newsletter | Self-serve form | Per send | Next slot | Open rate |
| Community | Admin intro | Negotiated | Unclear | None |
| Event | Sponsor deck | Tiered package | Event date | Badge scans |
| Agency | Retainer SOW | Monthly + markup | Kickoff first | Monthly deck |
With distribution.wtf
- 1One brief
- 2distribution.wtf
- 3Network
- 4Execution
- 5Proof + outcome
One relationship, one contract, one budget and one report. The network still has many channels. You just stop coordinating them yourself.
The network
Distribution is a graph, not a directory.
Every node is a real distribution property with an audience, a geography, a format, availability, a price and a delivery history. Your brief is matched to the part of the graph that reaches your audience.
AI engineering digest
- audience
- AI engineers, 64K subs
- geography
- Global
- format
- Primary slot
- availability
- Oct 12
- price band
- $$
- history
- campaign + delivery record
- Creators
- Podcasts
- Newsletters
- Events
- Communities
- Media
- Partners
For creators
Build a business around your audience, not just a following.
The creator business layer
We build the businesses behind the network.
We partner with rising creators to turn audience and expertise into durable businesses: shows, lists, events, communities and media IP that the creator owns. Those properties earn on their own and carry brand campaigns through the network.
- 01AudienceExpertise and people who trust youstart
- 02PodcastA show with a sponsor slot+ inventory
- 03NewsletterAn owned list, weekly inventory+ inventory
- 04EventA room your audience pays to be in+ inventory
- 05CommunityMembers who stay between drops+ inventory
- 06Media IPA series or property that outlives a post+ inventory
- 07Sponsorship revenueRecurring, packaged, priced, paidoutcome
You own it
The property and the audience stay yours.
We build and sell it
Formats, packaging, pricing and sponsor demand.
Revenue share
We earn where we help create or commercialise.
For brands
One brief in. A whole distribution network out.
The brand workflow
Tell us what you are shipping. Get a plan you can approve.
No shortlists to curate and no contracts to chase. The brief comes back as a distribution mix with budget, timeline, deliverables and an approval step.
New distribution brief
Example briefWhat are you shipping?
- Product
- Ledgerly, spend management for startups
- Target audience
- Founders and finance leads at seed to Series B startups
- Objective
- Qualified demo requests
- Geography
- United States, United Kingdom
- Budget
- $80,000
- Constraints
- Approved creative only. No gambling or crypto adjacency.
Recommended distribution
draftExample plan12
creators
4
podcasts
7
newsletters
2
communities
1
event
Timeline
Oct 14 to Nov 8 · 4 weeks
Deliverables
26 placements, each with proof of delivery
Approval
Awaiting your sign-off
- Newsletters
- Creators
- Podcasts
- Communities
- Events
For agents
Built for humans. Callable by agents.
Agents, API and MCP · coming in V1B
Your growth agents will call distribution.
In V1B distribution becomes a typed, policy-bound capability. Your agent will submit intent and follow the run; spend, new terms and publishing will stop for approval unless your policy allows them. Early access requests are open now.
- distribution.create_intent({ product: "Series A", audience: "US AI engineers", budget: 50000 })→ intent_id: int_7q2k
- distribution.resolve_audience({ intent_id })→ 5 distribution categories
- distribution.plan({ intent_id, max_spend: 50000 })→ plan_9c1f · ranked plan + allocation
- distribution.inventory({ plan_id, window: Oct 10..24 })→ available nodes + terms
- distribution.create_campaign({ plan_id, assets: approved })→ cmp_2hx8 · state: approval
- distribution.approve({ campaign_id, token })→ waiting on human: jane@company
- distribution.execute({ campaign_id })→ run_5ka1 · executing
- distribution.status({ run_id })→ per-placement state + blockers
- distribution.evidence({ campaign_id })→ proof bundle · one per placement
- distribution.results({ campaign_id })→ delivery + outcome signals
- distribution.stop({ campaign_id, reason })→ available at any state
Policy
- spend limit
- $50,000 per campaign
- channels
- creator, podcast, newsletter, event
- geography
- US only
- needs approval
- spend, new terms, publishing
- auto-allowed
- planning, inventory, status
Campaign state
- 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.
What exists today
Honest about the build.
The network and the planning work today, run by people with software underneath. The API, MCP and creator business tooling come next, in this order.
- V0Live
Brief and plan
Send a brief, get a real distribution plan from our team.
- V1ANext
Brand workspace
Campaigns, approvals, execution status and proof of delivery.
- V1BNext
API and MCP
Your agents create intents, request plans and follow runs, inside your policy.
- V1CNext
Creator business layer
Properties, sponsorship inventory and revenue share for network creators.
- V2Next
Performance graph
Plans learn from delivered campaigns and allocate budget better.
Questions
The short answers.
What is distribution.wtf?+
Distribution infrastructure for technology companies. You tell us what you are shipping, who needs to care and your budget. We build the plan across a curated network of creators, podcasts, newsletters, events and communities, run it, and return proof of every placement.
Is this an influencer marketplace?+
No. You do not browse and hire creators one by one. You give one brief and one budget, and the plan, contracts, execution and reporting come back as one relationship. Creators are part of the network, not the product you shop.
Which companies is it for?+
Technology companies: SaaS, AI, consumer tech, infrastructure, cybersecurity, fintech, hardware and deep tech. Your own customers can be anyone, from developers and enterprise buyers to consumers, SMBs or researchers.
What does agentic mean here?+
In V1B your own software agents will call distribution as a capability: create an intent, get a plan, request approval, execute approved actions, follow status and pull evidence. Spend, new terms and publishing will need approval unless your policy pre-authorises them.
How do creators work with you?+
We partner with rising creators to build businesses around their audience: podcasts, newsletters, events, communities and media IP they own. We help create, operate and sell those properties, and earn a revenue share where we do.
What is live today?+
Briefs and human-assisted distribution plans are live. The brand workspace, API and MCP access, and the creator business layer are being built in that order.