Documentation
Behavioral State Protocol — a standard interaction surface so any caller can send commands to any service, and any observer can consume the events it produces.
Caller
Any Caller
app · agent · IoT · human
Command
→
BSP Endpoint
Your Implementation
/.well-known/bsp
Event
→
Consumer
Any Agent
LLM · app · UI · agent
1
Expose
/.well-known/bsp Serve a discovery manifest describing your agents, capabilities, and transport bindings. Consumers read it once and know everything.
2
Accept commands, produce events
Callers POST commands to your service. Your service processes them (any way it likes) and the events it produces are observable via the HTTP or MCP API.
3
Observe every execution
Every command→event cycle is stored as an execution trace — input, output, duration, and success — giving you a full audit trail.
Getting Started
- Protocol OverviewWhat BSP is and how it works
- DiscoveryThe
/.well-known/bspmanifest
Agents
- Global RegistryFuture concept — public BSP directory
- LifecyclePause and resume agents
- EventsEvents published by services
- CommandsAccept and catalogue commands
- QueriesSynchronous reads of current state
Transports
Reference
- VersioningHow versions work
- ConformanceWhat it means to be BSP-compliant
- Design DecisionsWhy BSP is shaped the way it is
Comparisons
- BSP vs UCPHow BSP relates to Google's Universal Commerce Protocol