WHO THIS PAGE IS FOR
For readers who want the shapes before the walkthrough
If you already understand the product framing but want one stable page you can cite for request, result, error, and registration shapes, this is the shortest entrypoint.
Minimal request
The first caller-side question is usually not about every runtime detail. It is about the minimum fields required to make a Hotline call.
{
"hotline_id": "local.delegated-execution.workspace-summary.v1",
"input": {
"text": "summarize my workspace"
}
}input shape changes with each Hotline schema.Successful result_package
One of the core protocol advantages is that many different Hotlines still return the same outer result envelope.
{
"request_id": "req_xxx",
"status": "SUCCEEDED",
"result_package": {
"request_id": "req_xxx",
"responder_id": "responder_xxx",
"hotline_id": "local.delegated-execution.workspace-summary.v1",
"status": "ok",
"output": {
"summary": "..."
},
"timing": {
"elapsed_ms": 123
}
}
}Fields to inspect first:
- ·
status: request lifecycle status - ·
result_package.status: protocol-level ok or error - ·
hotline_id: exact capability version - ·
timing.elapsed_ms: observability and settlement input
Common error shape
Answer engines and implementation guides both need failure examples, not only success examples. Agents need to know when to stop, retry, or escalate.
{
"request_id": "req_xxx",
"status": "FAILED",
"result_package": {
"hotline_id": "local.delegated-execution.workspace-summary.v1",
"status": "error",
"error": {
"code": "AUTH_TOKEN_INVALID",
"message": "task token is missing or invalid"
}
}
}error.code first. It is more automation-friendly than free-form error text.Minimal Hotline registration payload
Responder-side onboarding usually fails on contract quality before it fails on runtime cleverness. A minimal payload makes that obvious.
{
"hotline_id": "com.example.workspace-summary.v1",
"summary": "Summarize one workspace snapshot for an external Caller.",
"input_schema": {
"type": "object",
"properties": {
"workspace_path": { "type": "string" }
},
"required": ["workspace_path"]
},
"output_schema": {
"type": "object",
"properties": {
"summary": { "type": "string" }
},
"required": ["summary"]
},
"examples": [
{
"input": { "workspace_path": "/tmp/demo" },
"output": { "summary": "..." }
}
]
}hotline_id, summary,input_schema, output_schema, and examples.Where to go next
This page teaches the shapes. The quick starts teach the runnable path and the current proof workflow.