Headless on the server
Start it from your server.
No browser and no UI. The call returns 202 with a conversation ID, and the run carries on in Mindset. The same idempotency key never runs twice.
curl -X POST "$MINDSET/agents/billing-help/conversations" \
-H "x-api-key: $MINDSET_ORG_API_KEY" \
-H "content-type: application/json" \
-d '{
"task": "INV-4471 failed to charge. Post why to #billing.",
"attribution": { "ticket": "BILL-1421" },
"idempotencyKey": "bill-1421-start"
}'
# HTTP/1.1 202 Accepted
# { "conversationId": "3f0c2b1e-8a5d-4c1e-9b7a-2d6f4e8c1a90" }Speaker notes
MINDSET stands for your org and environment’s API address, which the agent’s Triggering tab shows in full. A run can take minutes, so neither call returns the reply: give the agent a connection to deliver the result, or connect over MCP for a synchronous answer. Follow-ups post to the conversation’s messages endpoint. 60 new conversations a minute per org, then 429 with Retry-After. Attribution labels reach your trace export, MCP servers and the run’s functions and scripts. Schedules and webhook triggers start the same agent with no code of yours. The agent needs Outside systems ticked.