Start Here
Use the same `s2s_...` key for REST discovery, MCP execution, and account verification. The recommended path is: search papers, create or reuse a workspace from a seed, run a sidekick brief, then export a launch pack.
Create a key at /developers/keys. Every example below assumes Authorization: Bearer s2s_YOUR_KEY.
Call /api/developers/whoami or the MCP whoami tool before doing workspace actions. This tells the agent which user and workspaces the key is bound to.
Use REST for discovery and MCP for workspace-native actions. That keeps the flow short and avoids low-level route assembly in your client.
curl -H "Authorization: Bearer s2s_YOUR_KEY" \ "https://sciencetostartup.com/api/developers/whoami"
curl -H "Authorization: Bearer s2s_YOUR_KEY" \ "https://sciencetostartup.com/api/v1/free/papers?limit=5&q=voice+agents"
Server URL: https://sciencetostartup.com/api/mcp
Clients: OpenAI, Codex, Cursor, Claude, and any MCP-compatible agent can use the same endpoint and key.
Verify MCP identity first
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "whoami",
"arguments": {}
}
}Golden path
1. search_papers { "query": "voice agents", "limit": 5 }
2. workspace_create_from_seed {
"title": "Opportunity: Voice agents",
"seed_type": "paper",
"seed_id": "2401.00001"
}
3. workspace_run_action {
"workspace_id": "YOUR_WORKSPACE_ID",
"run_kind": "sidekick_brief"
}
4. workspace_run_action {
"workspace_id": "YOUR_WORKSPACE_ID",
"run_kind": "launch_pack"
}
5. get_launch_pack { "arxiv_id": "2401.00001" }