Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cerca.dev/llms.txt

Use this file to discover all available pages before exploring further.

Start with an API key from the Cerca app. API-key routes use the production base URL: 
Authorization: Bearer $CERCA_API_KEY
If you want to call the API from application code, install the official SDK for your language first. See Client libraries for TypeScript, Python, Go, Ruby, and CLI install commands. First, verify the key and recover the organization it belongs to: 
curl https://api.cerca.dev/auth/context \
  -H "Authorization: Bearer $CERCA_API_KEY"
Then list the fleets available to that key and choose the fleet that should own the agent configuration. Fleets are where shared defaults live: custom tools, OAuth apps, approval policies, default model settings, and other configuration you do not want to repeat for every agent. Create one agent per durable workspace. A common pattern is one agent per end user: 
curl https://api.cerca.dev/agents \
  -H "Authorization: Bearer $CERCA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "userId": "user_finance_ops",
    "fleetId": "fleet_internal_ops",
    "configuration": {
      "instructions": "Help the finance team keep vendor work moving.",
      "tools": ["web.*", "sandbox.*"]
    }
  }'
After that, start threads against the agent, stream progress, and resolve approvals when the runtime pauses for a decision. Once the agent is running, the next step is to wire your product into agent activity that happens outside a foreground request — thread completions, approval requests, schedule triggers. Subscribe a URL with Webhooks and follow the Receiving webhooks guide to verify deliveries end-to-end.