Product Feature Research

CreateOS - Positioning and Wedge

Thesis

CreateOS should reframe from "prompt-to-live-app" (the Bolt lane) to "the only agent sandbox where the agent can earn" — a positioning that uses primitives only CreateOS has and plays in a category no competitor currently owns.

Why the Bolt/Lovable lane is the wrong fight

The agent-economy lane (where no one has the complete stack)

Capability CreateOS E2B Daytona Modal Cloudflare Vercel
Agent code execution (sandbox) ✅ AI Sandbox ✅ ✅ ✅ ✅ (just launched) ✅ Sandbox
Inference routing ✅ router.nodeops.network ❌ ❌ ✅ (for own infra) ✅ AI Gateway ❌
On-chain agent payment rails ✅ MPP Gateway ❌ ❌ ❌ ⚠️ (co-governs x402 but no product rail) ❌
Marketplace with revenue share ✅ ❌ ❌ ❌ ❌ ❌ (v0 templates not the same)
Persistent projects + deployment ✅ ⚠️ ✅ ⚠️ ✅ ✅
💭

Every other agent sandbox is a cost center for the agent that runs there. CreateOS is the only one where the agent can be a revenue center. This is a structural product difference — not a feature claim — because MPP is an assembled stack (inference + payment + marketplace) that competitors would have to rebuild, and at least one of those (payment rails on-chain) is a different business model than Cloudflare or Vercel is willing to enter.

The x402 alignment question (must resolve within 30 days)

x402 is now co-governed by Coinbase, Cloudflare, Google, and Visa. ~$600M annualized volume, 119M transactions on Base. This is emerging standard infrastructure — not a niche protocol.

Three viable positions for MPP (pick one, commit in public):

Position What it means Signal to ecosystem
A. MPP is an x402 facilitator Implement the x402 facilitator interface for NodeOps network "We're inside the standard" — strongest alignment
B. MPP extends x402 Agent identity, marketplace integration, per-agent spend caps as extensions on top of x402 "We're first-class x402 with differentiated extras"
C. MPP is x402-compatible Wire protocol compatibility at the interface layer; NodeOps internals "We interoperate but operate independently"

Do not position as rival protocol. Coinbase + Cloudflare + Google + Visa is too much gravity to fight.

Why the agent-economy position wins

  1. Uses unique primitives. Every sentence of the positioning references something CreateOS has and nobody else has fully assembled.
  2. Aligned with the category-forming moment. Cloudflare Agents Week (April 13, 2026) + OpenAI Agents SDK + x402 $600M volume + LangChain 1B cumulative downloads = agent infrastructure is the 2026 software narrative.
  3. Defensible against Cloudflare. Cloudflare owns 20% of internet traffic and can out-market; but their model is "we charge for compute." Adding payment rails means entering a different business (money movement, KYC, on-chain settlement) that they haven't shown intent to.
  4. Creates new conversations. Every enterprise agent conversation becomes "where does the agent earn?" — a question with one answer today.

The narrow product decision to make right now

Per Addendum 2, do NOT try all three of these simultaneously — pick one keystone event for the next 90 days:

Option Keystone event Strength Weakness
A. Prompt-to-live-app No signup, 60s to shareable URL Proven Bolt pattern, universal appeal Direct competition with Lovable + Bolt
B. Prompt-to-published-marketplace-app Prompt → live app → published to marketplace with revenue share — in one session No competitor has this Harder to deliver reliably
C. Deploy-an-earning-agent Prompt → autonomous agent with spend caps + x402 payments, one click Structurally unique to CreateOS Narrower initial audience

Recommendation (from Addendum 2): lean toward (C) Deploy-an-earning-agent, backed by a public case study of an agent earning real revenue on MPP within 30 days. This is the positioning that unlocks OpenAI Agents SDK inclusion.

Sources