Live. The Founder API is available in production (
api.venture.caplia.ai, mcp.venture.caplia.ai), with a sandbox (api-sandbox.venture.caplia.ai, mcp-sandbox.venture.caplia.ai) for safe testing. Mint a company-scoped key in the founder portal - see Authentication.Founder, not investor? This is the right place. If you’re a VC, accelerator, angel, or corp-dev team reading other people’s deal flow, you want the Venture API instead. The two are separate surfaces with separate keys.
What you can do
See your CRI and what to fix
Pull your live CRI score (0-1000), its six domain breakdowns, and the rubric’s ranked, concrete recommendations - the same signals investors see, plus exactly how far you are from Caplia Verified.
Iterate your deck to 700
Submit a deck draft, get a private CRI score back, regenerate, resubmit - loop until you clear 700, then publish one clean public update. Investors never see the drafts.
Keep your profile current
Update your company name, website, industry, stage, and problem statement, and upload documents to your data room - so the record investors read stays accurate.
Drive it from Claude
Connect Claude (or any MCP client) to the Caplia MCP server and run the whole loop in natural language - pair it with Canva or your deck tool and let the agent rebuild the deck between scores.
Start here
Quickstart
Read your CRI and recommendations in under three minutes.
The deck loop
The headline workflow: iterate your pitch deck to Caplia Verified.
Authentication
How company-scoped
cap_fnd_* keys work and how to get one.MCP server
Connect Claude Desktop, Cursor, or ChatGPT to run the loop for you.
How the Founder API is different
The Founder API and the Venture API run on the same hosts (api.venture.caplia.ai, mcp.venture.caplia.ai) but behave differently depending on which kind of key you present:
| Founder API | Venture API | |
|---|---|---|
| Who it’s for | A founder, on their own company | Investors reading their deal flow |
| Key prefix | cap_fnd_live_* / cap_fnd_test_* | cap_inv_live_* / cap_inv_test_* |
| Scope | One company - the company the key was minted for | The caller’s whole pipeline |
| How a company is identified | Resolved from the key - no company id in any request | By id, in the path |
| Namespace | /v1/me/* | /v1/companies/*, /v1/search, etc. |
| Headline feature | Private deck-scoring loop → Caplia Verified | Submit and score inbound decks at scale |
/v1/me/* endpoint resolves the company from the key itself, so there’s no company id to pass and no way to read or change anyone else’s data.
Base URL
Environments
| Production | Sandbox | |
|---|---|---|
| REST | https://api.venture.caplia.ai/v1/... | https://api-sandbox.venture.caplia.ai/v1/... |
| MCP | https://mcp.venture.caplia.ai/ | https://mcp-sandbox.venture.caplia.ai/ |
| Key prefix | cap_fnd_live_* | cap_fnd_test_* |
| Data | Your real company | Sandbox / test company |
live key hitting a -sandbox URL returns 401, and a test key hitting a production URL returns 401.
Need help?
- Founder API access and issues: email paul@caplia.ai
- Status: check status.caplia.ai