Framework

Two-Sided Agentic Marketplace Framework

Mitchell Jones's model for building infrastructure that serves two distinct customers simultaneously: end users who want frictionless access to paid services without credential management, and merchants who want to monetize API traffic from agents without building new infrastructure. The gateway layer is the value — it solves a real problem on both sides at once.

How it works

  1. 1End-user problem: API keys, subscriptions, and credential management create cognitive tax that slows builders down
  2. 2Merchant problem: valuable APIs have no native way to meter, monetize, or convert autonomous agent traffic
  3. 3The gateway sits between both sides — handling auth, routing, and payments without requiring either party to change their stack
  4. 4Network effects compound: more merchants attract more end users; more end users attract more merchants
  5. 5Pricing flexibility is a feature: merchants set per-call, per-token, or outcomes-based pricing; the gateway enforces it
  6. 6This model works for any category where credential plumbing creates friction between supply (services) and demand (builders)

Hear it on the podcast

Your API Keys Are Killing Your ProductivityListen to the episode

More from this episode

Get the next framework first

One email a week with the frameworks, tools, and founder stories from the podcast. Free.

More frameworks for AI & Automation

Every Decision Is a Prediction ProblemBen Turtle's foundational reframe: every business decision is a prediction. You choose A over B because you predict A leads to a better outcome. Science is prediction - a theory only holds if it forecasts the next observation. This reframe has tactical implications for founders: the company with the most accurate model of the future compounds the fastest. Building systematic prediction capability - not just execution speed - is the real AI-era strategic advantage.Chronological Grounding MethodLightningRod AI's core training innovation: use the natural time structure of real-world data as a supervisory signal, without human labels. Given data up to timestamp A, predict what happens at timestamp B. Repeat across all messy data. The model that gets good at this game learns genuine causal patterns - not surface correlations - and produces domain expertise that no frontier model has, because it came from data unique to your context.Vision-First AI DesignBuild AI interfaces around the primary human sense — vision — rather than defaulting to text chat. AI products that take screen share as their primary input can respond to what users actually see and do, not just what they describe, enabling a fundamentally more contextual and effective interaction model.Two-Bucket Training Data FrameworkEvery organization building AI falls into one of two buckets, each with a mirror-image problem. Bucket 1 has too much data in the wrong format - dense, unstructured, chronological internal data that contains enormous value but resists standard training pipelines. Bucket 2 has no data at all and needs a domain-specific corpus created from public sources. LightningRod's chronological grounding method solves both with the same underlying engine.Disneyland Quality StandardThe quality bar for AI voice products: everything must work perfectly because the moment the magic breaks — like Mickey Mouse taking his head off in the park — users don't lower their expectations. They leave. Trust in AI voice products, once broken, doesn't recover.Zero Hallucination ArchitectureDesigning AI systems for high-stakes environments by requiring every agent output to have traceability, auditability, and human-in-the-loop checkpoints wherever hallucination risk is non-zero.