Prove AI

The Preuve AI startup validation API lets any AI agent validate startup ideas programmatically. The Agent API and its MCP server are live. 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, Hermes Agent, 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, Trends, and Community Signals. 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.

Turn your ClaudeCursorCodexHermesClaude into a cofounder who says no.

Only 17.5% of ideas earn a go. Find out where yours stands, with market research and cited evidence inside your agent.

Connect Preuve

Works with the agent you already use

ClaudeCursorCodexHermesAny MCP client

Paste into any agentSet up Preuve AI MCP for me.Copy

Find out now, not after the build.

Any agent · no Preuve

Says yes. Starts building.

$ any-agent> Build me a companion-app platform for game studios.Great idea. Scaffolding the architecture…✓ 12-step plan written✓ 40 files created✓ deploying to production

sources checked 0competitors named 0buyers found 0

Preuve AI · same agent

Checks first. Then decides.

claude · preuve connectedLIVE

> Build me a companion-app platform for game studios.● preuve · validate_idea("SecondScreen OS", "starter") ⠹ scanning 60+ live sources… SCORE 48 / 100 VERDICT CAUTION RIVALS Discord +4 mapped TOP RISK go-to-market✓ starter scan complete · share/p0Y8vGqy> Hold on. Score 48. Discord already owns the room and studios take months to sign. Wedge first, code after.

60+ sources · 5 competitors · 1 tool callReal report ↗

Same agent. Same prompt. One of them asked the market first.

What changes once it's connected

Rank your ideas side by side

Regu84 · Go

Mallorca Dental GPO82 · Go

OpsCopilot69 · Caution

SecondScreen OS48 · Caution

Know who pays

255threads

r/EntrepreneurCOMPLAINT

“He answers everything. Remembers everything. Knows every client. Jumps into every problem.”

Ship with a plan

01

Ship the revenue verification pipeline

02

Deploy 3 to 5 test agents, $25 each

03

Publish a live agent leaderboard

Business ideas that fit you

5free a day

> Ten years in healthcare ops, $5k to start, never again compliance paperwork.

ICP: healthcare opsBudget: $5kAvoid: compliance

Does it fit you?

10 yrs domain40 h/week6 mo runway

52FITMODERATE

Connect Preuve→

Ask it anything

ClaudeCursorCodexHermes

mcp.preuve.ai/mcpone URL for every agent

RedditSEC EDGARCrunchbaseG2tcTechCrunch+55

ClaudeCursorCodexHermes

mcp.preuve.ai/mcpone URL for every agent

RedditSEC EDGARCrunchbaseG2tcTechCrunch+55

Connect your agent

Fastest · free

In claude.ai

Web, desktop or mobile. Claude signs you in and mints the key during consent, so there is nothing to paste.

_1_Open the Preuve AI listing

_2_Sign in with Preuve AI, press Allow

_3_Ask it anything

Connect from Claude

Works on the free plan. About 20 seconds.

In a coding agent

Claude Code, Cursor, Codex, Hermes or any MCP client. You don't configure anything. Paste one prompt.

_1_Get a key from your account

_2_Paste one message to your agent

_3_It installs Preuve and runs your first scan

Paste the prompt→

Same message for every agent. It reads docs.preuve.ai and does the rest.

Paste this prompt to your agent

Replace prv_your_key with yours. The agent reads the two doc pages, picks the setup for its own client, installs the skill if it supports skills, then runs a free starter scan.

Generate key ↗

copycopied ✓

Set up Preuve AI MCP for me.

Server: https://mcp.preuve.ai/mcp (HTTP transport) Auth header: Authorization: Bearer prv_your_key

Read https://docs.preuve.ai/mcp-server.md for the setup that matches this client, and https://docs.preuve.ai/agent-skill.md for how to use the tools without spending paid quota. Install the skill if you can.

Then run start_analysis with scanType "starter" on this idea:

Prefer to do it by hand? Per-client snippets for Claude Code, Cursor, Codex and Hermes are on docs.preuve.ai/mcp-server.

Ask it

Validate one idea01

Validate this startup idea with Preuve: [your idea]. Start with a free starter scan, then walk me through the verdict, competitors, and biggest risk.

✓Runs free, no quotaCopy

Compare 5 ideas02

Here are 5 ideas I'm considering. Run Preuve starter scans on all of them and rank them by viability score, with one sentence on why.

✓Up to 10, rankedCopy

Build a dashboard03

Export my latest Preuve report and build a dashboard artifact: score gauge, top competitors, market size, and the 3 pivots.

✓Becomes an artifactCopy

Prefer raw HTTP? Same tools, one header. API reference on docs.preuve.ai

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 six tools: five for your own ideas (start_analysis, get_analysis, enrich_analysis, export_analysis, generate_ideas) and get_agency for client work on a Consultant or Agency workspace, which is also what workspace: "agency" on start_analysis, get_analysis and export_analysis acts on. Those Agency calls each need one specific scope - agency:write to start a client analysis, agency:read for get_agency and the two agency reads - and neither is ever granted implicitly, so an older key gets a 403 scope refusal on them until it is replaced or the connector is reconnected. Neither recovery is unconditional: reconnecting only widens the key if the client rebuilds its scope request from our discovery document rather than replaying a cached one, so check the consent screen actually lists the Agency permissions before approving (reconnecting revokes the current key either way), and creating a key by hand needs either a paid personal plan or membership of a Consultant or Agency workspace with an active subscription. It is listed in the Claude Connectors Directory (claude.ai/directory/preuve-ai). The remote server at https://mcp.preuve.ai/mcp works as a claude.ai 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?

Two ways. Connecting the Preuve connector from Claude signs you in and mints the key for you during consent, on any plan including free. Creating a key by hand in the account panel is self-serve on a paid personal plan or in an active Consultant or Agency workspace. Start free: connect and run your first starter scans. Each key is scoped, sent in one x-preuve-key header, and tied to one Preuve account. A key carries the five personal scopes by default (analysis:write, analysis:read, batch:write, batch:read, export:read). The two Agency scopes, agency:write and agency:read, are never implicit: ask for them when you create the key, or approve them on the OAuth consent screen. They are what unlocks the Agency workspace, and workspace membership is checked separately on every call, so holding them does nothing on an account that belongs to no workspace.

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), trends (on-demand Google Trends), and community (community signals from forums, Reddit, review sites, and X). 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 sees only the analyses it created through the API, and reports you ran in the web app stay invisible to it. The one exception is a key you gave Agency access: agency:read can list and export every client report in your Consultant or Agency workspace, dashboard-created ones included, and agency:write can spend that workspace shared credits. Those two scopes are never implicit, so a key that was not asked for them has no such reach. If a key leaks, revoke it; your account itself is untouched, but revoking an Agency key is urgent in a way a personal one is not.

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.

Read the Polsia review

{"@context":"https://schema.org","@type":"WebPage","name":"Startup Validation API & MCP Server","description":"Preuve's startup validation MCP server and HTTP API score a startup idea from 60+ live sources, returning a viability verdict, market and competitor research, and a shareable report inside Claude, Cursor, Codex or Hermes.","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 six tools: five for your own ideas (start_analysis, get_analysis, enrich_analysis, export_analysis, generate_ideas) and get_agency for client work on a Consultant or Agency workspace, which is also what workspace: \"agency\" on start_analysis, get_analysis and export_analysis acts on. Those Agency calls each need one specific scope - agency:write to start a client analysis, agency:read for get_agency and the two agency reads - and neither is ever granted implicitly, so an older key gets a 403 scope refusal on them until it is replaced or the connector is reconnected. Neither recovery is unconditional: reconnecting only widens the key if the client rebuilds its scope request from our discovery document rather than replaying a cached one, so check the consent screen actually lists the Agency permissions before approving (reconnecting revokes the current key either way), and creating a key by hand needs either a paid personal plan or membership of a Consultant or Agency workspace with an active subscription. It is listed in the Claude Connectors Directory (claude.ai/directory/preuve-ai). The remote server at https://mcp.preuve.ai/mcp works as a claude.ai 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":"Two ways. Connecting the Preuve connector from Claude signs you in and mints the key for you during consent, on any plan including free. Creating a key by hand in the account panel is self-serve on a paid personal plan or in an active Consultant or Agency workspace. Start free: connect and run your first starter scans. Each key is scoped, sent in one x-preuve-key header, and tied to one Preuve account. A key carries the five personal scopes by default (analysis:write, analysis:read, batch:write, batch:read, export:read). The two Agency scopes, agency:write and agency:read, are never implicit: ask for them when you create the key, or approve them on the OAuth consent screen. They are what unlocks the Agency workspace, and workspace membership is checked separately on every call, so holding them does nothing on an account that belongs to no workspace."}},{"@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), trends (on-demand Google Trends), and community (community signals from forums, Reddit, review sites, and X). 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 sees only the analyses it created through the API, and reports you ran in the web app stay invisible to it. The one exception is a key you gave Agency access: agency:read can list and export every client report in your Consultant or Agency workspace, dashboard-created ones included, and agency:write can spend that workspace shared credits. Those two scopes are never implicit, so a key that was not asked for them has no such reach. If a key leaks, revoke it; your account itself is untouched, but revoking an Agency key is urgent in a way a personal one is not."}},{"@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."}}]}