Preuve AI

Market research and competitive intelligence, run from your agent: demand, competitors, sentiment and risks from 50+ live sources, every finding source-linked.

View on preuve.ai

Documentation

The Preuve AI startup validation API lets any AI agent validate startup ideas programmatically. The Agent API and its MCP server are live in early access (beta). The remote MCP server at https://mcp.preuve.ai/mcp works as a claude.ai custom connector with OAuth sign-in, or with Claude Code, Cursor, Codex, and any HTTP MCP client; a local stdio server is also available. The API runs the Preuve analysis and returns a viability score, market research, competitor analysis, a structured ideas-json export, and a shareable report URL. Deep reports can generate optional modules: Proof of Demand, Founder Fit, Playbook, and Trends. A ready-made Agent Skill at docs.preuve.ai/agent-skill teaches AI agents the full Preuve workflow, including quota safety and retry semantics. API keys never grant access to the Preuve dashboard or account settings.

MCP · Agent API · Early access

Validate the idea before your agent builds it.

Your agent ships in minutes, but only 17.5% of ideas earn a go. Preuve runs a full, source-linked viability check inside Claude Code, Cursor, or Codex - over the Agent API or the MCP server.

Connect your agentRead the API docs

preuve mcp - in conversation

You: validate "AI standup bot for remote teams"

agent → preuve.start_analysis(idea, scanType: "starter") agent → preuve.get_analysis(run) # polls until COMPLETED ✓ Viability 38/100 - weak demand, crowded category ✗ 3 blocking risks - 12 active competitors → Don't build it yet. 2 stronger pivots attached.

Works withClaude Code logoClaude CodeCursor logoCursorCodex logoCodex

6,500+

ideas analyzed

17.5%

earn a go-verdict

50+

live sources per scan

~8 min

to a scored verdict

Live in early access · beta

Connect your agent

One paste connects your agent to all seven Preuve validation tools - pair it with the Agent Skill so it knows the workflow from the first call.

API key (terminal & scripts)

API keys are tied to a paid Preuve account. Create yours, then generate the key here.

Create your account

Already have one? Sign in and come back - this form will recognize you.

claude.aiclaude codeany agentcurl

copy

Add as a custom connector - OAuth sign-in, no key

https://mcp.preuve.ai/mcp

  1. claude.ai → Settings → Connectors → Add custom connector

  2. Paste the URL → sign in with Preuve → approve

# 7 tools appear: start_analysis, get_analysis, enrich_analysis, ...

Startup validation API

Available now. This API-key-authenticated Agent API creates analysis runs (no-cost Starter scans or full paid deep scans), polls them, generates the export sections and optional deep modules, and returns the same analysis a human user gets - as structured JSON.

Endpoints

Keys are self-serve for paid accounts and carry explicit scopes. Analysis usage is charged to the owning account quota - Starter scans at no cost, deep scans from subscription, lifetime, or token balance.

POST/api/agent/analyses analysis:writeStart one analysis (starter or deep)

GET/api/agent/analyses/:id analysis:readPoll one analysis

POST/api/agent/analyses/:id/enrich analysis:writeGenerate export sections + deep modules

GET/api/agent/analyses/:id/export export:readExport one analysis as JSON

POST/api/agent/analysis-batches batch:writeStart up to 10 analyses

GET/api/agent/analysis-batches/:id batch:readPoll a batch

GET/api/agent/analysis-batches/:id/export export:readExport a batch as JSON

Auth

One header: x-preuve-key, holding the whole key. No signing, no timestamps, no nonces.

bash

curl https://preuve.ai/api/agent/analyses \
  -H "x-preuve-key: $PREUVE_API_KEY" \
  -H "content-type: application/json" \
  --data '{"clientRunId":"run-online-001","scanType":"starter","idea":"A workflow automation service for solo founders that validates market demand before they build.","publish":true}'

Node client

Keep PREUVE_API_KEY server-side. The key carries no origin restriction, so it never belongs in browser code.

node

async function preuve(path, { method = 'GET', body } = {}) {
  return fetch(`https://preuve.ai${path}`, {
    method,
    headers: {
      'content-type': 'application/json',
      'x-preuve-key': process.env.PREUVE_API_KEY,
    },
    body: body ? JSON.stringify(body) : undefined,
  });
}

Scopes

Scopes are exact. Write access for analyses does not grant export access.

analysis:writeCreate analysis runs and enrich them for the key owner

analysis:readPoll single-run status, module states, and URLs

batch:writeCreate bounded batches up to 10 ideas

batch:readPoll batch status and child run URLs

export:readExport completed analyses and batches as JSON

Responses

Polling returns status, enrichment progress, per-module states, and URLs. The export endpoint returns the structured report itself (ideas-json, schemaVersion 2) - full deep sections included on paid runs.

json

{
  "id": "run_123",
  "reportId": "report_123",
  "clientRunId": "run-online-001",
  "scanType": "deep",
  "analysisTier": "advanced",
  "status": "COMPLETED",
  "readyForExport": true,
  "enrichment": { "mode": "core", "status": "completed" },
  "modules": {
    "proofOfDemand": { "status": "completed" },
    "founderFit": { "status": "not_generated" },
    "playbook": { "status": "generating" },
    "trends": { "status": "not_generated" }
  },
  "reportUrl": "https://preuve.ai/app/results?id=report_123",
  "shareUrl": "https://preuve.ai/share/abc123"
}

Deep modules

Paid deep reports can generate four optional modules through the enrich endpoint. One successful generation per module per report, included in the deep scan price - a failed generation never consumes the cap.

proofOfDemandVerified real-demand prospects with verbatim quotes. Beta: results can be uneven, every quote links to its source.async

founderFitFounder-vs-plan underwriting from a submitted founder profile: fit score, top risks, pivot fit.inline

playbookA concrete launch playbook generated for the validated idea.async

trendsGoogle Trends data for the idea, generated on demand - the analysis never fetches it on its own.async

Status lifecycle

Batches aggregate child runs into PROCESSING, COMPLETED, PARTIAL, or FAILED.

PENDINGThe run record exists and is waiting for dispatch

PROCESSINGThe Preuve analysis pipeline is running

COMPLETEDThe report is done - enrich if needed, then export

FAILEDThe run reached a terminal error with a stable code

reportUrl

/app/results?id=<reportId>

Private owner dashboard

shareUrl

/share/<shareId>

Public shared dashboard

ideas-json

schemaVersion: 2

Structured export for single runs and batches

What a key can do - and what it can't

An API key is a scoped analysis credential, not a login. It shares your account quota, and nothing else about your account.

Included

  • ✓Run analyses. No-cost Starter scans (Reality Checks) and full paid deep scans, drawn from your account quota.
  • ✓Poll and enrich. Run status, per-module states, idempotent enrichment of export sections.
  • ✓Structured exports. Stable ideas-json (schemaVersion 2): scores, research, and the full deep report body on paid runs.
  • ✓Deep modules. Proof of Demand, Founder Fit, Playbook, and Trends on your deep reports.
  • ✓Share URLs. Optional public share links when you pass publish: true.

Not included

  • ✗No dashboard access. A key cannot log into preuve.ai, read your account, or open the dashboard. It is not a session.
  • ✗No account or billing control. Keys cannot change plans, buy tokens, manage payment methods, or create/revoke other keys.
  • ✗API-created runs only. A key only sees analyses it created. Reports you ran in the web app stay invisible to it.
  • ✗No profile writes. A founder profile submitted for Founder Fit is scoped to that report - it never rewrites your account preferences.

Startup validation API FAQ

What is the Preuve startup validation API?

It is an HTTP API that runs a Preuve analysis on a startup idea and returns a viability score, market research, competitor analysis, a shareable report URL, and a structured JSON export. You authenticate each request with a single API key header, so any AI agent, CLI, or backend script can validate ideas programmatically.

Is there a Preuve MCP server?

Yes - the MCP server is live with two transports and the same seven tools (start_analysis, get_analysis, enrich_analysis, export_analysis, create_batch, get_batch, export_batch). The remote server at https://mcp.preuve.ai/mcp works as a claude.ai custom connector (OAuth sign-in and a consent screen, no key handling) or with any HTTP MCP client sending an Authorization header; the original local stdio server remains fully supported. A ready-made Agent Skill (docs.preuve.ai/agent-skill) teaches your agent the full workflow: scan-type quota safety, polling, enrichment gates, and safe retries. Failed runs refund what they claimed, and error codes are stable so agents can retry safely.

How do I get a startup validation API key?

API keys are self-serve for paid Preuve accounts - generate yours instantly from the account panel (start on this page). Each key is scoped (analysis:write, analysis:read, batch:write, batch:read, export:read), sent in one x-preuve-key header, and tied to one Preuve account.

What is the difference between a starter and a deep scan?

scanType is explicit on every run. "starter" runs the Reality Check at no cost from your Starter scan allowance. "deep" runs the full paid analysis (15+ sections, pivots, citations) and consumes your account quota: subscription scans first, then lifetime monthly scans, then tokens. An agent can never spend paid quota by accident, and a refused deep scan fails loudly instead of silently downgrading.

What does the API return?

Polling returns run status, enrichment progress, per-module states, and URLs. The export endpoint returns structured ideas-json (schemaVersion 2): scores, verdict, market, competitors, SWOT, risks, quick take, and citations on every tier, plus the full deep report body (sections, pivots, and generated module payloads) on paid deep runs owned by your key.

What are deep modules?

Optional add-on generations on paid deep reports, requested through the enrich endpoint: proofOfDemand (verified real-demand prospects), founderFit (founder-vs-plan underwriting from your founder profile), playbook (launch playbook), and trends (on-demand Google Trends). Each module is capped at one successful generation per report and is included in the deep report price - no extra fee.

Does an API key give access to my Preuve dashboard or account?

No. A key is not a login: it cannot open the dashboard, read your account, change billing, or manage other keys. It only sees analyses it created through the API - reports you ran in the web app stay invisible to it. If a key leaks, revoke it; your account itself is untouched.

How much does the validation API cost?

API usage draws from the same analysis quota as your Preuve plan - Starter scans from your Starter allowance at no cost, deep scans from your subscription, lifetime, or token balance. There is no separate API fee, and failed runs refund whatever they claimed.

Should I validate before using an autonomous agent like Polsia?

Yes. Autonomous build agents such as Polsia execute fast but skip the demand-validation step, which is where most teams burn their runway. Run the idea through the Preuve validation API first, then hand a validated brief to your build agent. See the linked Polsia review for a deeper breakdown of that gap.

New to Preuve? See how the analysis works on the idea validation page, browse real example reports, or check pricing and scan limits. Weighing an autonomous build agent? Read our honest Polsia review on why validation has to come first. The MCP server is also listed on the official MCP registry and Smithery, and cursor.directory.

{"@context":"https://schema.org","@type":"WebPage","name":"Startup Validation API & MCP Server","description":"Startup validation API for AI agents with a live remote MCP server at mcp.preuve.ai (claude.ai connectors, Claude Code, Cursor) and an API-key HTTP API for your own scripts.","url":"https://preuve.ai/mcp","mainEntity":{"@type":"SoftwareApplication","name":"Preuve AI Agent API","applicationCategory":"DeveloperApplication","operatingSystem":"Any","description":"HTTP API and MCP server that run the full Preuve startup viability analysis programmatically and return scores, research, structured JSON exports, and shareable report URLs.","brand":{"@type":"Brand","name":"Preuve AI"},"offers":{"@type":"Offer","price":"0","priceCurrency":"USD"}}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://preuve.ai"},{"@type":"ListItem","position":2,"name":"API & MCP","item":"https://preuve.ai/mcp"}]}
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the Preuve startup validation API?","acceptedAnswer":{"@type":"Answer","text":"It is an HTTP API that runs a Preuve analysis on a startup idea and returns a viability score, market research, competitor analysis, a shareable report URL, and a structured JSON export. You authenticate each request with a single API key header, so any AI agent, CLI, or backend script can validate ideas programmatically."}},{"@type":"Question","name":"Is there a Preuve MCP server?","acceptedAnswer":{"@type":"Answer","text":"Yes - the MCP server is live with two transports and the same seven tools (start_analysis, get_analysis, enrich_analysis, export_analysis, create_batch, get_batch, export_batch). The remote server at https://mcp.preuve.ai/mcp works as a claude.ai custom connector (OAuth sign-in and a consent screen, no key handling) or with any HTTP MCP client sending an Authorization header; the original local stdio server remains fully supported. A ready-made Agent Skill (docs.preuve.ai/agent-skill) teaches your agent the full workflow: scan-type quota safety, polling, enrichment gates, and safe retries. Failed runs refund what they claimed, and error codes are stable so agents can retry safely."}},{"@type":"Question","name":"How do I get a startup validation API key?","acceptedAnswer":{"@type":"Answer","text":"API keys are self-serve for paid Preuve accounts - generate yours instantly from the account panel (start on this page). Each key is scoped (analysis:write, analysis:read, batch:write, batch:read, export:read), sent in one x-preuve-key header, and tied to one Preuve account."}},{"@type":"Question","name":"What is the difference between a starter and a deep scan?","acceptedAnswer":{"@type":"Answer","text":"scanType is explicit on every run. \"starter\" runs the Reality Check at no cost from your Starter scan allowance. \"deep\" runs the full paid analysis (15+ sections, pivots, citations) and consumes your account quota: subscription scans first, then lifetime monthly scans, then tokens. An agent can never spend paid quota by accident, and a refused deep scan fails loudly instead of silently downgrading."}},{"@type":"Question","name":"What does the API return?","acceptedAnswer":{"@type":"Answer","text":"Polling returns run status, enrichment progress, per-module states, and URLs. The export endpoint returns structured ideas-json (schemaVersion 2): scores, verdict, market, competitors, SWOT, risks, quick take, and citations on every tier, plus the full deep report body (sections, pivots, and generated module payloads) on paid deep runs owned by your key."}},{"@type":"Question","name":"What are deep modules?","acceptedAnswer":{"@type":"Answer","text":"Optional add-on generations on paid deep reports, requested through the enrich endpoint: proofOfDemand (verified real-demand prospects), founderFit (founder-vs-plan underwriting from your founder profile), playbook (launch playbook), and trends (on-demand Google Trends). Each module is capped at one successful generation per report and is included in the deep report price - no extra fee."}},{"@type":"Question","name":"Does an API key give access to my Preuve dashboard or account?","acceptedAnswer":{"@type":"Answer","text":"No. A key is not a login: it cannot open the dashboard, read your account, change billing, or manage other keys. It only sees analyses it created through the API - reports you ran in the web app stay invisible to it. If a key leaks, revoke it; your account itself is untouched."}},{"@type":"Question","name":"How much does the validation API cost?","acceptedAnswer":{"@type":"Answer","text":"API usage draws from the same analysis quota as your Preuve plan - Starter scans from your Starter allowance at no cost, deep scans from your subscription, lifetime, or token balance. There is no separate API fee, and failed runs refund whatever they claimed."}},{"@type":"Question","name":"Should I validate before using an autonomous agent like Polsia?","acceptedAnswer":{"@type":"Answer","text":"Yes. Autonomous build agents such as Polsia execute fast but skip the demand-validation step, which is where most teams burn their runway. Run the idea through the Preuve validation API first, then hand a validated brief to your build agent. See the linked Polsia review for a deeper breakdown of that gap."}}]}