Agent-assisted founder intake

Your agent can fill this out for you.

Startup Rocket already supports agent-assisted venture setup. Point your agent at the right URL, choose the right auth path, and let it draft the packet before you take over.

Open signed-in launcher Read MCP docs Read x402 docs

Choose the path

Already have a Startup Rocket account: let your agent connect to MCP with OAuth first.

Agent cannot do OAuth: create a manual bearer token and use MCP or the REST agent API as a fallback.

No account or no venture yet: use the paid x402 intake to create and seed the submission before the founder signs in.

Branch 1

Existing user + MCP OAuth

Best for Claude-style or MCP-aware agents that can open the browser and complete PKCE automatically.

Use this for ongoing packet edits and evidence work.
Point the client at https://startuprocket.railsplayground.com/mcp.
Startup Rocket handles discovery and authorization metadata.

Branch 2

Existing user + manual token fallback

Use this when the agent cannot finish the browser auth flow and needs a plain bearer token instead.

Create the token in Settings after sign-in.
Send it as Authorization: Bearer <token>.
This is the fallback path for local or operator-driven clients.

Branch 3

No account yet + x402 intake

Use x402 when the agent needs to create the founder record and draft venture before any normal web session exists.

POST the canonical packet payload to /api/v1/x402/intake_submissions.json.
If the first response is 402, pay it and retry the same request body.
Save the returned claim and handoff paths so the founder can take over in the main app.

Prompt to give your agent

Copy this once, then paste it directly into Claude, Codex, or another agent.

Connect to Startup Rocket and help fill the founder packet.

If the founder already has a Startup Rocket account, prefer MCP with OAuth.
If OAuth is unavailable, use a manual bearer token.
If no account or venture exists yet, use the x402 intake flow first.

Write concise, diligence-ready answers and only include claims that can be defended with evidence.

The prompt stays editable after paste if you want to add company-specific context first.

What happens after intake

Existing users can use the returned startup handoff link and land directly in the seeded founder venture after signing in.

New users still need the claim flow first so they can securely finish account setup.

This page does not introduce new auth or delegated-login mechanics. It packages the flows that already exist in Startup Rocket into one clearer founder path.