The Founder API is live in production. The examples below use the sandbox host (
api-sandbox.venture.caplia.ai) with a cap_fnd_test_* key so you can build safely; swap to api.venture.caplia.ai and your cap_fnd_live_* key for your real company.Get a founder key
Mint a company-scoped key in the Caplia founder portal: account menu → API Keys → Create key, pick a
read (or read + write) scope, and copy the plaintext - it’s shown once. You must be a company admin. See Authentication for the key model.Store it in an environment variable - never paste it into a browser or commit it:Confirm what Caplia has on record
Your key is your company - no id needed. Check the profile Caplia currently shows investors:
Response
Read your CRI score and recommendations
This is the founder’s primary signal - your score, how far you are from Caplia Verified, and the rubric’s concrete fixes:The CRI is on a 0-1000 scale. A company is Caplia Verified at
Response
score >= 700; points_to_verified tells you the exact gap. Each recommendation carries an expected_points_increase so you can attack the highest-leverage fixes first.Iterate your deck to 700
The recommendations tell you what to fix. To actually move the score, submit a revised deck for private scoring, read the new CRI, and repeat - without investors seeing the drafts. That loop is the whole point of the Founder API:
The deck loop →
Submit a draft, poll for a private CRI, regenerate, resubmit - then publish one clean update once you clear 700.
Do it from Claude instead
Every step above is also an MCP tool, so you can run the whole thing in natural language from Claude Desktop, Cursor, or ChatGPT - “what’s my CRI and what should I fix?” See MCP server.Next steps
The deck loop
The full iterate-to-Verified workflow.
API reference
Every
/v1/me/* endpoint, with schemas.