Distribution & DevRel
Future GTM outline — how we'd find the API's first users once it exists. "Build it and they will come" is a fallacy even in the agent economy. Nothing here is running yet; it's the plan we're shaping alongside the product concept.
Will agents just find it via registries?
Partly, we think. Agents would query MCP registries directly, so good registry presence would matter — but registries enforce scopes and trust, humans allowlist tools for high-stakes tasks, and visibility tracks documentation and metadata quality. So the play would be: optimize the listings and market proactively — but only after there's a tool worth listing.
The DevRel engine (already running)
The biggest asset is trust, and the website generates it today:
- Proof-of-work halo — interactive fork breakdowns prove competence and should de-risk the API in a developer's eyes once it ships.
- Founder brand — an open-source, ex-core-dev track record converts skeptics far better than ad-style marketing.
- Education as top-of-funnel — capture developers while they're learning a fork; the API would be the natural next step. The website is the textbook; the API is the lab equipment.
Channels (planned)
| Channel | Play |
|---|---|
| Agentic proof-of-value outreach | An agent monitors target teams' testnet deployments, simulates them under upcoming-fork rules, and sends a specific, useful result (not a generic pitch). |
| "Trojan-horse" GitHub | Open issues / PRs on relevant repos containing real simulation data showing how an EIP affects their code — value first, footprint back to the API. |
| Visual Twitter/X funnel | Teardowns of trending contracts/events simulated old-rules vs. new-fork; the visual hooks humans, the link plugs into their agents. |
| Registry SEO & metadata | Meticulous MCP listings — exact EIP numbers, keywords ("MEV simulation"), thorough docs — so the right tool surfaces for the right task. |
Likely first users (hypothesis)
The earliest adopters would probably be programmatic and high-incentive: MEV searchers, DeFi/security auditors, and L2 / infra teams needing to understand upcoming forks before mainnet (see target users). To be validated with real outreach once a PoC exists.
Cadence
The roadmap and organization evolution are documented in the open, with a regular Twitter/X cadence — the same channel that carries the founder-notes / principles material.
Channel priorities and an outreach plan to be refined once the Agent API concept stabilizes.