Not yet. The Hono-based API powers the VenturOS web app today. External access — API keys, rate limits, a developer portal — ships with the next major release. Sign up for early access on this page to get notified the day it opens.

What's MCP and why do you mention it?

MCP — Model Context Protocol — is the emerging open standard for connecting AI assistants to external tools and context. MCP integration is on the VenturOS roadmap, planned to ship alongside public API access in the next major release. When it lands, AI clients like Claude Desktop, Cursor, and custom agents will be able to call your Team and the Venture Map as a context source.

What does VenturOS do with my GitHub repo?

GitHub access is scoped to read. We never push, branch, comment, or open PRs. Ren and the rest of the Team read your code to ground their reasoning — architecture, dependencies, recent changes — and that context flows into every executive. Disconnect any time and your repo context is purged within 24 hours.

Can I integrate VenturOS into my own product?

That's the design intent — once public access ships. You'll be able to call any of the eight executives, query the Venture Map, and stream outputs into your own surface (Slack, Linear, your own UI). Until then, the API is internal-only.

What endpoints will be available?

The planned public surface mirrors the internal one: /v1/exec/{name}/chat for one-on-one conversations with any executive, /v1/team/coordinate for Venos-led syntheses, /v1/venture-map for read/write access to the canvas, and /v1/context for repo/URL/document ingestion. Webhooks for cadence events are on the roadmap. The full reference will live at /api/reference once public access ships.

What does an API key cost?

API access will be bundled into Builder, Scale, and Custom tiers when public access ships. Free, Spark, and Grow tiers will get metered access with conservative limits. Final pricing — including per-call rates for high-volume use — will be published on /pricing alongside the public release.

When does the public API ship?

Public preview ships with the next major release of VenturOS. We'll announce the date here and on the blog with at least 30 days notice for any breaking change. Email partners@ventur-os.com to be on the early-access list.

Is VenturOS just a wrapper around an LLM?

No. VenturOS is a multiagent system on a context graph with agent orchestration — three of the four architecture patterns Gartner's April 2026 Agentic AI Hype Cycle calls out as the real shape of agentic AI. Per Gartner, 70%+ of agentic AI initiatives will fail by 2029 from "agent washing." We are built to be in the 30% that won't.

How are deliverables and decisions versioned?

Every deliverable carries a stable ID and a version. Every conversation is timestamped. You can replay how a decision was made, see which executive authored which revision, and audit what your Team knew at any point in time. Stable identifiers mean you can reference deliverables across your stack without breaking when content changes.

API & Architecture

Built API-first.

Last updated May 4, 2026

VenturOS is built API-first. Every AI executive, every deliverable, and every Venture Map state lives behind a Hono-based API with an OpenAPI spec. The web app is the first client; future clients — your tools, agents, and AI assistants — will call the same surface when public access ships.

VenturOS is a platform, not a sealed app. The architecture is shaped to expose every executive — eight named AI executives (Ezra joining as CFO soon) — every deliverable, and every Venture Map state to your code, your IDE, and any future MCP-aware client we add support for.

API-first by design

Every executive's reasoning, every deliverable, every Venture Map state lives behind a clean Hono-based API with an OpenAPI spec. The web app is one client. Your tools will be too — public access opens with the next major release.

GARTNER-ALIGNED BY ARCHITECTURE

Multiagent system. Context graph. Agent orchestration.

VenturOS maps to four technologies on Gartner's April 2026 Hype Cycle for Agentic AI: Multiagent Systems and Model Context Protocol (peak of inflated expectations), Context Graphs and Agent Orchestration (innovation trigger), Human-Agent Collaboration Workspace (innovation trigger). Per Gartner, over 70% of enterprise agentic AI initiatives will fail by 2029 due to 'agent washing' — automation tools rebranded as agents. We're built to be in the 30% that won't.

MCP-ready

VenturOS will expose its executives as Model Context Protocol servers — so your IDE, terminal, or LLM client can call Ren, Lyra, or Vivi directly. Same context, same memory, your tooling.

Read-only repo access

GitHub access is scoped to read. We never push, branch, comment, or open PRs. Disconnect any time and your repo context is purged within 24 hours.

Event surface (planned)

Subscribe to executive activity: PRD created, runway model updated, competitive scan finished. Wire it into Slack, Linear, or your own system.

Stable identifiers

Executives, deliverables, and decisions all carry stable IDs. Reference them across your stack without breaking when the underlying content changes.

Versioned everything

Every deliverable is versioned. Every conversation is timestamped. You can replay how a decision was made — and audit what your Team knew, when.

What's available, and when

Surface	Status
REST API (read)	Early access
REST API (write)	Q3 2026
MCP server (Ren, Lyra, Vivi)	Q3 2026
Webhooks	Q4 2026
GraphQL	Under evaluation

Want early API access or to influence the MCP shape? Email hello@ventur-os.com.

Frequently asked questions

Build with your Team, not around it.

Start with the app today. Plug into the API and MCP as they ship.

Start Free

No credit card required.