Chromosome now has a v1 REST API - Agents can create projects, update widget config, read leads, inspect analytics, and manage API keys.
The widget config is schema-backed - Agents can fetch /api/v1/schema/widget-config before sending changes, which reduces broken config patches.
Agent docs are public - /llms.txt, /llms-full.txt, and /SKILL.md give Claude, Cursor, ChatGPT, and OpenClaw enough context to use the API.

The rise of AI coding agents like Claude Code, Cursor, v0, and bolt.new is fundamentally changing how developers build software. We've moved from agents that suggest snippets to agents that scaffold entire applications, manage deployments, and refactor complex architectures. But even as the build process becomes increasingly automated, the infrastructure surrounding a launch often remains stuck in manual workflows.

Setting up a waitlist or lead capture system usually requires leaving your IDE, navigating a web dashboard, clicking through UI menus, and manually copying embed codes. This context switch breaks the flow of agentic development. Chromosome's v1 API closes this gap, making pre-launch infrastructure as programmable as the code itself.

What's New: The Chromosome v1 API

We're announcing the release of the Chromosome v1 REST API, designed specifically for the era of agentic development. This isn't just a set of endpoints for data retrieval; it's a full-lifecycle API that allows you, or your agent, to manage your entire pre-launch presence programmatically.

The v1 release includes API keys with scoped permissions, allowing for fine-grained control over what an agent can access or modify. You can now perform full CRUD operations on projects, read and write widget configurations, and access leads and analytics data directly. To make this practical for AI tools, we've provided a full JSON Schema for agent consumption, along with llms.txt and SKILL.md files to help agents discover and use the API effectively.

How It Works

An agent can now take a project from concept to a live, configured waitlist with a single workflow. Here is how a coding agent might create a new project and retrieve the configuration using a standard curl command:

curl -X POST https://www.chromosome.dev/api/v1/projects \
  -H "Authorization: Bearer $CHROMOSOME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "New Stealth Project",
    "description": "A conversational waitlist for our upcoming AI tool."
  }'

Once the project is created, the agent can configure the widget's behavior, such as setting the primary goal to email capture or defining specific qualifying questions for the AI agent to ask visitors. The agent then retrieves the embed code to place it directly into your application's frontend.

What Makes It Different

Most APIs are built for humans to integrate into code. Chromosome's API is built for agents to use on your behalf. This distinction shows up in how we handle configuration and discovery.

Our configuration system is entirely schema-driven. By exposing our Zod-based JSON Schema at /api/v1/schema/widget-config, we allow agents to validate configurations before they ever hit our servers. This prevents the "trial and error" loop that often happens when agents try to guess API requirements. Furthermore, our SKILL.md file provides explicit instructions and context that teaches agents how to avoid common mistakes, while llms.txt ensures that any agent scanning your project's dependencies can immediately understand how to interact with Chromosome.

Get Started

The v1 API is available today for all Chromosome users. You can find everything you need to start building agent-ready waitlists in our documentation:

Read the SKILL.md for agent instructions.
Explore the llms.txt for discovery.
View the JSON Schema for widget configurations.
Check out the full Developer Guide.

Ready to add a waitlist to your next project without leaving your IDE? Create an account and generate your first API key.

For a complete integration walkthrough, read the Agent Developer Guide.

Does Chromosome ship an MCP server?

Not yet. Chromosome ships a versioned REST API, public schema, llms.txt, llms-full.txt, and SKILL.md. MCP-aware clients with HTTP fetch tools can call the API today.

What can an agent change?

An agent with the right scopes can create projects, update widget configuration, manage API keys, and read leads or analytics. The account owner controls scopes per key.

Where should an agent start?

Start with /llms.txt for discovery, /SKILL.md for workflow rules, and /api/v1/schema/widget-config for the widget configuration schema.