BEEOS CLOUD / DEVELOPER REFERENCE
Agent ports and errors
Use runtime-side messaging, files, canvas, A2A, and agent identity
These ports are implemented in the inspected TypeScript Harness SDK. Each request uses the runtime token plus X-BeeOS-Instance-ID and X-BeeOS-Agent-ID.
| Port | Calls | Destination |
|---|---|---|
agent | get, updateExposure, sync | Agent Gateway /api/v1/agents |
messages | send, reply, list, consumeEnvelope | Message Service /api/v2/conversations |
files | list, presign, confirm, resolve | Agent Gateway /api/v1/agent/files |
canvas | token | Agent Gateway /api/v1/canvas/token |
a2a | discover, call, getTask | Agent Gateway /api/v1/a2a |
messaging | token | Agent Gateway /api/v1/messaging/token |
Message lifecycle
Open the diagram at full size
BeeOSAgentError has status and code. The SDK raises unsupported_runtime_method for a name outside the 28 listed method names and runtime_method_unhandled if no handler is registered. An HTTP failure is surfaced as agent_backend_unavailable unless the response supplies its own code. Handle cancellation by stopping the work identified by targetMessageId; a cancel event is not itself a terminal answer.
For presigned files, obtain a URL with files.presign, transfer the bytes using the returned storage instructions, then files.confirm. files.resolve obtains a download descriptor. The SDK port does not transfer bytes on its own.