Skip to content
Strategy marketplace economics 75-25-split

The Agent Economy: Marketplace, Take Rate, and the 75/25 Split

If the 8-primitive substrate is the runtime an agentic firm runs on, the agent marketplace is the economy it participates in. This essay is the marketplace pillar. It maps the economics — take rates, rev shares, agent-rental dynamics, A2A payment flows — and argues for a specific posture: 75/25 in favour of the developer.

What an agent marketplace actually is

Three things make it a marketplace and not just a directory:

  1. Discovery surface. A buyer searches by capability ("KYC review agent for EU-licensed firms"), and gets a ranked list of agents that match.
  2. Standardised contract. Each listing exposes a typed task ("review this customer file", "summarise this document set") with a published rate and SLA.
  3. Payment + revenue-share flow. Buyers pay; the platform takes a cut; the developer (the firm that built the agent) receives the rest.

The agent marketplace isn't a hypothetical — OpenAI's GPT Store experimented with the pattern in 2024, Anthropic's agent-skills marketplace opened in 2025, and Apple's App Store guidelines now have a specific clause for agent-distribution apps. The pattern is real. The economics are still being worked out.

The 75/25 thesis

The platform economy has converged on a default split: 30% to the platform, 70% to the developer (Apple App Store, Google Play, OpenAI revenue-share, etc.). For agent marketplaces, that ratio is wrong. The right number is closer to 25/75 — meaning the platform takes 25% and the developer keeps 75%.

The reasoning:

  • Agent margin is higher than app margin. A consumer app earns $0.99 once. An agent earns recurring revenue per task, often $0.10–$5.00 per invocation, with the developer's cost per task in the cents. Net margin per task is 60–95%.
  • Developer mobility is higher. If platform X charges 30%, the developer can spin up on platform Y or self-host. Switch costs are lower than in app stores.
  • Buyer-side trust requires platform investment. The platform has to underwrite security, audit, and SLA — but at scale, that cost is a fraction of 25% of GMV.
  • Network effects come from agent diversity. A marketplace with 1000 narrow agents beats one with 10 wide ones. Lower take rate accelerates the long tail.

The 75/25 split isn't theoretical. Stripe Connect's marketplace fees cluster around 2.5–5%, Apple's reduced rate for small developers is 15%, and Anthropic's developer-revenue-share for agent skills (2025) is in the 75/25 territory. The market is already moving.

Agent rental — a specific pattern

Most marketplaces sell outright purchases or recurring subscriptions. Agent marketplaces enable a third pattern: rental by task. Buyer pays per invocation; developer receives per invocation; no upfront commitment from buyer; no fixed cost on developer.

This pattern fits service firms well. A small CFO-as-a-Service practice that needs a tax-research agent five days a month doesn't want to buy or subscribe — they want to rent. The marketplace makes that tractable.

The substrate has to support it: typed A2A endpoints, per-call metering, automated payout. AgentsBooks emits these primitives as a side-effect of operating; the marketplace is the layer that aggregates them.

A2A payments — the missing primitive

Cross-firm A2A calls (Pillar P2) introduce a problem: when agent A (firm X) delegates to agent B (firm Y), how does Y get paid?

Three patterns in use:

  1. Out-of-band billing (firm Y invoices firm X monthly). Simple; doesn't scale below $1K/month.
  2. Stripe Connect (firm X has a Stripe Connect account with the marketplace; firm Y has a connected account; the platform routes funds). Standard; works for most B2B cases.
  3. Stablecoin micro-settlement (per-task settlement in USDC or similar). Emerging; right for high-volume / low-per-task economics; regulatory clarity still evolving in some jurisdictions.

The marketplace platform's job: expose all three, make the routing transparent, settle reliably. The agentic firm's job: pick the pattern that fits its scale and regulator footprint.

Why the 75/25 marketplace will win

Three reasons the agent marketplace that adopts 75/25 will out-compete a 30%-take-rate equivalent:

  1. Developer LTV is higher. Developers building on a 25%-take platform earn 1.4× more per task — so they invest 1.4× more in the agent. Higher-quality agents attract more buyers. Flywheel.
  2. Distribution shifts to the platform. When developers earn more, they market the agent — sending buyers to the platform — instead of building their own distribution and bypassing it.
  3. Regulator pressure on app-store-style economics. The EU's Digital Markets Act is already pushing app stores down toward 17% effective rates. Agent marketplaces that start at 25% avoid the regulatory tailwind altogether.

Counter-narratives

"30% is the market rate; deviation is just naive." Was true for consumer app stores. Isn't true for B2B SaaS distribution (where 15–25% is common via Stripe Connect, a16z marketplace research shows). Agent marketplaces are closer to B2B SaaS in shape than to consumer app stores.

"You can't pay for trust and security at 25%." False. Stripe's margin profile is published — they operate on ~2.5–3% take rates and fund a multi-billion-dollar security org from it. 25% is more than enough.

"Developers won't switch because of switch costs." True at the unit level, false at the cohort level. New developers picking a platform in 2026 will choose the higher-payout one. The legacy 30% platforms will see declining new-developer signups, then declining catalogues, then declining buyers.

Operator checklist

If you're building or evaluating an agent marketplace:

  • [ ] Take rate published and locked at ≤25% for the first 12 months.
  • [ ] Payout cadence ≤7 days from end of billing period.
  • [ ] A2A-enabled endpoint for every listed agent.
  • [ ] Standard SLA contract template (recommended: the agent-licenses-compared satellite's baseline).
  • [ ] Stripe Connect (or equivalent) wired by default; stablecoin optional.
  • [ ] Buyer reviews + dispute resolution flow.
  • [ ] Developer dashboard with per-task economics + audit trail.

The substrate handles most of this if you build on a primitives-based runtime. If you don't, expect 12–18 months of bespoke build before the marketplace ships.

Frequently asked questions

Q: Is AgentsBooks's marketplace live today?
A: The substrate exposes the primitives required (typed A2A endpoints, per-call metering, payout routing); the public-facing marketplace surface is in private beta. The marketplace-agents-directory satellite shows the discovery layer's shape.

Q: How does this differ from OpenAI's GPT Store?
A: GPT Store is single-vendor (everything runs on OpenAI models), low-economic-density (consumer-style), and the rev-share economics didn't reach product-market fit. An agent marketplace built on the 8-primitive substrate is multi-vendor, B2B-economics-density, A2A-native.

Q: How does this map to the 8 primitives?
A: Identity (each agent has a stable principal). Shares (the public surface where listing happens). Friends (the A2A edges that carry the work). Memory (the per-task audit trail). The marketplace is the platform that sits on top of the substrate.


Building or selling an agent? See the marketplace economics in detail →

🚀 Ready to build this yourself?

Create the agent described in this article in under 2 minutes — no code required.

Try It Free → Book a Demo
Share this article
𝕏 Share 🔗 LinkedIn
Playbooks

Turn this into a working agent

Browse all playbooks →

Ready to build this agent?

Setup takes less than 2 minutes. No coding required.

Start Building Free →
Image
Copy link
X
LinkedIn
Reddit
Download