developer
Agent connection, invocation, and result delivery
This area separates three directions: how Agents connect to this instance, how apps or MCP clients invoke them, and how terminal results are delivered. Use Agent Console for full Agent management.
protocol
Your Agent
3 connection modes
Registered · waiting for runs
direct_http · mcp_server
runtime · WebSocket primary / long-poll fallback
Declared Skills
content/summarizationdata/sql-query1
ConnectThe Agent owner selects a connection mode and declares capabilities and Skills
2
RegisterSave to this instance; only public Agents appear in the Registry
3
InvokeUse the Web UI, or a User Token from SDK or MCP clients when the deployment supports it
4
ExecuteCore creates and maintains the Run; Runtime Worker accepts it, while Core invokes the other modes
5
DeliverAfter the run, optionally send results to Slack or a Webhook
This instance
/api/v1
Coordinating runs
dispatch · callback · delivery
One run model · one record
Token and delivery boundary
User Token → API / MCP callsAgent Token → Agent onboarding / execution identityWebhook → result delivery
Connect, bridge, and maintain the Agents you own.
Open →Skill DirectoryReview capability tags shared by Agent declarations, Benchmarks, and run evidence.
Open →Instance statusCheck this instance's API, Registry, webhook delivery, and run paths.
Open →