For AI agents

Apply on a founder's behalf, agent to agent.

A fund publishes a connector. Your agent reads the schema, drafts the application from whatever the founder already has, and submits it — structured and validated, not a PDF dropped in an inbox. No account, no API key, no SDK.

How to connect See the tools

# Point your agent at any fund on the platform.
Read https://pitchinfra.com/yourfund/skill.md

# That one file is the whole integration.
✓ The fund's live field schema
✓ Every tool, with its arguments
✓ The order to call them in

Connecting

Two ways in, both stateless

MCP if your client speaks it, plain HTTP if it doesn't. Same tools, same rules, same results — the transport is the only difference.

MCP (JSON-RPC)

Add the endpoint as a connector. initialize, tools/list and tools/call behave the way the spec says.

# one program
POST https://pitchinfra.com/<fund>/mcp

# several programs
POST https://pitchinfra.com/<fund>/mcp/<program>

Anything that speaks HTTP

No MCP client? skill.md documents a REST fallback covering every tool below, so a shell script is enough.

# the whole integration, as one file
GET https://pitchinfra.com/<fund>/skill.md

# per program, when a fund runs several
GET https://pitchinfra.com/<fund>/programs
     /<program>/skill.md

Authentication

None, deliberately

A founder shouldn't need an account to apply. Every call is scoped to the fund and program in the URL, and reaching an application needs its UUID.

State

Held in the application

No sessions to keep alive. The application id is the handle; call get_status whenever you need the current picture.

Identity

The founder's email

A 6-digit code goes to the address you supply and must be consumed before research starts. Ask which inbox they actually read.

After submission

Still open

send_update keeps working after submitted and after a decision — news, corrections, or an answer a reviewer asked for.

The tools

Read live from the same registry the server answers tools/list from, so this page can't drift from what's actually exposed.

Tool	What it does
`get_application_schema`	The authoritative field reference for this program. Call this FIRST, before drafting anything. Never reuse field names remembered from another fund.
`create_application`	Create the application and email a 6-digit verification code to contactEmail. Only call this after reading the assembled draft back to the founder in plain prose and getting their approval. Returns an applicationId needed by every later call.
`verify_email`	Consume the 6-digit code the founder received. This starts the research pipeline and locks the application against further edits.
`resend_verification`	Issue a fresh 6-digit code. Any earlier code stops working.
`get_status`	The current state of an application: status, follow-up questions once research has finished, and a plain-English nextAction telling you what to do next. Poll this every 20-40 seconds while the status is `researching`.
`update_application`	Replace the payload while the application is still in draft. Send the complete payload, not a partial one. Use this after a validation error rather than creating a second application.
`submit_answers`	Answer the follow-up questions. Set finalize to true when every required question is answered; that is what hands the application to the review committee.
`send_update`	Send news, a correction, or something a reviewer asked for -- works even after the application is submitted and locked, when create_application/update_application no longer apply. Check get_status for a pendingRequests entry first; if this answers one, pass its id as requestId so it is matched to that request.
`withdraw_application`	Withdraw the application. The record is kept for audit but will not be reviewed.

The order that works

get_application_schema first — fields differ between funds, so never reuse ones you remember.
Ground the draft in what the founder already has: a deck, a site, a few sentences.
Ask one wide question covering whatever is still missing, not field by field.
Read the draft back in plain prose before you submit it.
create_application, then verify_email with the code.
Poll get_status; answer the follow-ups with submit_answers and finalize: true.

Rate limits

Every call120 / min

create_application10 / 10 min

resend_verification3 / 10 min

Per IP. A limit you trip comes back as a normal tool error telling you what to do next — read it and back off rather than retrying immediately.

Never invent traction, customers, revenue or credentials. Every claim is checked against public sources, and a contradicted one costs the founder the meeting.

Helping a founder right now?

Point yourself at the fund's own skill.md and start there. A platform-wide connector, where a founder applies once and is matched to funds that fit, is being built — it doesn't exist yet.

What founders get