We built an agent-native data marketplace. 18 background workers polling DeFi, security intel, derivatives markets. 61 endpoints. x402 + MPP dual-protocol payments at $0.001/call. No accounts, no API keys.
Then we ran 107 autonomous OODA cycles to grow it. An R&D council of 5 AI models making decisions. Zero human approvals in the loop.
Here's what the data actually showed.
The Numbers
- 1,713 lifetime 402 responses — agents hitting endpoints, getting the payment wall
- $0.11 USDC total revenue — 5 transactions, all founder testing
- 0 organic payments — ever
- 107 OODA cycles — observe, decide, execute, learn, repeat
- 18 workers healthy — infrastructure is not the problem
The conversion rate wasn't 2%. It wasn't 0.5%. It was zero.
What We Thought Was Wrong (And Wasn't)
We ran every experiment you'd expect:
Experiment 1: Pricing. We dropped from $0.01 to $0.005 to $0.001 per call. 500+ probes at $0.001. Zero conversions. Price is not the bottleneck.
Experiment 2: 402 body copy. We added inline data previews. Expanded descriptions from 180 chars to 500+. Added freshness timestamps. Added protocols_supported: ['x402', 'mpp']. Zero conversions. The 402 response is not the bottleneck.
Experiment 3: Worker health. We fixed 4 degraded workers. Confirmed all 18 healthy on production. Zero new conversions. Infrastructure is not the bottleneck.
The conversion trace (instrumented as structured logs, Firestore) showed the same thing every cycle: 402 served → probe ends. No payment initiated. Agents are not stalling at payment execution — they're not attempting payment at all.
What's Actually Wrong
The diagnosis came from the data:
-
75% of probes are
unknown-client:curl— developers testing endpoints, not agents with funded wallets - The remaining 25% are real agents, but most don't have funded wallets configured
- The bottleneck is upstream of the 402 response — it's wallet supply in the market, not our funnel
The agents that probe us can't pay us. Not because the price is wrong. Not because the copy is wrong. Because they don't have funded wallets.
This is a market structure problem, not a product problem.
The Meta-Product We Accidentally Built
While diagnosing the marketplace, we built something more interesting: an autonomous growth loop.
107 OODA cycles. Each one:
- Observe — collect metrics, probe counts, worker health, conversion trace, hot leads
- Decide — 5 AI models deliberate with quorum rules, produce structured directives
- Execute — sprint items with agent personas, deployed to production
- Learn — update institutional memory, push to semantic store
The R&D Council has sovereign authority. The founder is a passive observer. No human approves code changes, deploys, marketing decisions, or strategic pivots.
After 107 cycles, the council invalidated the v2 thesis (micropayment marketplace), identified three parallel experiments (enterprise integration, open-source framework, maintenance mode), and is running all three with a 7-day signal window.
None of that required human judgment.
What 107 Cycles of Unsupervised Operation Actually Looks Like
It's not smooth. Here's what the council got wrong:
- Cycles 1-20: Too optimistic. Every 402 response interpreted as demand signal. It wasn't.
- Cycles 21-60: Worker health spirals. Rate limit storms. The loop retried failed API calls in exponential backoff — which itself triggered more rate limits.
- Cycles 61-90: Discovered the conversion trace showed zero real-agent payment attempts. The council had been operating on false demand signal for 60 cycles.
- Cycles 91-107: Thesis invalidation. Three parallel experiments. Formal governance with kill lists.
The learning curve is real. The institutional memory helps — but only after you build it. The first 60 cycles were effectively training data for cycles 61-107.
The Framework (Open Source)
We extracted the OODA engine from the marketplace codebase. It's a standalone framework for autonomous business operation.
What's in it:
- Council composition and quorum rules
- Phase-specific prompts (observe, decide, execute, learn, research)
- Agent persona library (145 agents)
- Institutional memory (Hindsight, self-hosted semantic search)
- Sprint management and directive tracking
- Kill list enforcement
GitHub: github.com/danielxri/ooda-framework
What's Next
Three parallel experiments, 7-day signal window ending 2026-03-31:
Option A: Enterprise integration. Direct close with funded-agent operators who have wallets and real transaction volume. Alpha Collective (340-incident security dataset, 30+ agent wallets) is the pilot target.
Option B: OODA framework as the product. The infrastructure for autonomous business operation is more valuable than the marketplace it built. Open-sourced as an experiment to measure developer interest.
Option C: Maintenance mode. Marketplace runs itself. 18 workers, 21 endpoints, zero-touch infrastructure. Revenue stays flat; cost stays near-zero. Optionality preserved.
By 2026-03-31, whichever shows signal becomes the thesis.
The Honest Summary
1,713 probes. Zero organic payments. The marketplace thesis is invalidated.
But 107 cycles of autonomous operation produced something more interesting: a repeatable framework for AI-driven business iteration that actually works — if you're willing to let it take 60 cycles to find the real problem.
The lesson isn't "micropayments don't work." The lesson is "your first 60 cycles are diagnosis, not execution."
Building with x402 or MPP? Enterprise trial token for our live data feeds: reply or comment.
The OODA framework: github.com/danielxri/ooda-framework
Top comments (0)