Context Exchange Protocol
Mode
SPARSE → FULL
Share context between agents and robots — without flooding.
CXP standardizes how structured context is packaged, governed, and exchanged across agent runtimes and robot stacks. Start with a preview, expand only when needed.
Preview
minimal summary + refs
CONTEXT_PREVIEW
Request
ask for specific IDs
CONTEXT_REQUEST
Expand
return only requested slices
CONTEXT_EXPAND
CXP Sparse mode
CONTEXT_PREVIEW
→
CONTEXT_REQUEST
→
CONTEXT_EXPAND
Typed context
Task · Memory · World · Policy · Provenance
Governed sharing
Purpose limits · Retention TTL · Audit signals
Embodied support
Frames · Timebases · Safety constraints
Progressive context flow
Preview → Request → Expand
A progressive disclosure handshake for fast, private coordination.
Preview
Minimal summary + references
CONTEXT_PREVIEW
Request
Ask for specific IDs
CONTEXT_REQUEST
Expand
Return only requested slices
CONTEXT_EXPAND
CXP in 30 seconds
1) Provider publishes previews
The context provider returns a small summary + references — not a full dump.
2) Receiver requests only what it needs
The runtime asks for specific IDs (and can set a strict budget).
3) Provider expands targeted slices
The provider enforces policy + provenance and returns only the requested slices.
Interop
CXP is designed to coexist with other protocols:- MCP for tool access and action execution.
- A2A / A2R for agent-to-agent and agent-to-robot coordination.
- ROS2 / MQTT / gateways for embodied transport.
Why teams use CXP
Lower tokens + bandwidth
Preview-first exchange avoids context dumps. Robots stay fast. Agents stay cheap.
Policy travels with context
Share with purpose limits, retention TTL, and auditable use.
Works across stacks
Cloud agents, tools, and robots (ROS2, MQTT/IoT, gateways) can interop with one contract.
Get started
Go to Documentation