Manifest / API

Manifest API reference

The Manifest API lets an authenticated user manage their own startup ideas and generate draft business documents. Use the REST API or the Streamable HTTP MCP server.

Authentication

Except for GET /api/v1/, send a Manifest API key in Authorization: Bearer manifest_sk_…. Create a key in the signed-in account's API access settings and grant only the scopes needed: ideas.read for reading or ideas.write for creating, editing, deleting, and generating documents. Keys can access only ideas owned by their account.

REST operations

GET /api/v1/ideas lists the key owner's ideas.
POST /api/v1/ideas creates an idea from a title and optional description.
GET /api/v1/ideas/{idea_id} retrieves one owned idea.
PATCH /api/v1/ideas/{idea_id} updates its title or description.
DELETE /api/v1/ideas/{idea_id} permanently deletes an idea; confirm with the user first.
POST /api/v1/ideas/{idea_id}/generate generates a business model canvas, pitch deck, PRD, or provisional patent draft.
GET /api/v1/usage returns account usage and plan limits.

MCP

Connect to https://manifeststartup.com/mcp using Streamable HTTP. Send the same API key as an Authorization Bearer header. The MCP tools mirror the REST operations and use the same key scopes and ownership checks.

Errors and limits

Errors are JSON. A 401 means the key is missing or invalid; a 403 means the key lacks a required scope or the resource is not owned by its account; a 429 means a rate or monthly limit was reached. Back off before retrying a rate-limited request. Generated documents are drafts for review, not legal, financial, or investment advice.