Prior Art
OSBP is not trying to own every part of agent commerce. It is a small booking-domain layer designed to compose with neighboring standards.
Adjacent layers
Section titled “Adjacent layers”| Layer | Examples | OSBP relationship |
|---|---|---|
| Agent tool transport | Model Context Protocol | OSBP can ride MCP instead of defining its own transport. |
| Commerce and ordering | Agentic Commerce Protocol (ACP) and Universal Commerce Protocol (UCP) | These are adjacent to cart, checkout, and order flows; OSBP covers staff-bound timeslots. |
| Payment authorization | AP2 | A booking mandate can sit beside a payment mandate. |
| Sector booking standards | OpenActive, FHIR | OSBP borrows the open-booking instinct, scoped to agent-driven service appointments. |
Boundary
Section titled “Boundary”The novelty claim is intentionally scoped. OSBP does not claim to be the first booking or scheduling standard. It claims that staff-bound service appointments need a clear mandate and mutation surface for AI agents.
Protocols and platforms named here are illustrative, not endorsements.
See the v0.1.0 specification for how OSBP draws these boundaries in practice.