Examples

OSBP v0.1.0 ships examples at two levels: credential-free reference examples anyone can run from a clean clone, and a real-platform design-partner example with Openings. Both exist to test the same claim: an agent can look up a service, explain policy, ask for bounded permission, create only inside a BookingMandate, and fail closed when the selected appointment no longer fits.

Reference backend

The repository’s reference backend is the public runnable baseline. It is a synthetic booking platform plus one vertical-neutral adapter. It needs no account, no booking-platform credentials, no network access, and no live customer phone number.

The point is generality. The adapter code is the same across the example businesses; the differences live in realistic service, schedule, policy, money, timezone, and verification data.

Example	What it demonstrates
Carolyn’s Dental	Fixed-price booking, insurance-dependent price, deposit, consultation handoff, and no-show fee
Gus’ Notary	In-person and remote appointments for the same service, quote-required price, verification flow, and deposit
Andy’s Auto	EUR pricing, Berlin local time, cancellation fee, quote and consultation branches, and deposit
Phil’s Spa	UK timezone, full prepay policy branches, consultation branch, late/no-show policy, and a JPY zero-decimal money fixture

Start here when you want to see OSBP work without any private setup:

Trace gallery

The v0.1.0 trace gallery is the easiest way to inspect the contract after you have read the spec. The traces are credential-free and can be replayed. They show the ordered loop: user request, generated BookingMandate, read tools, user approval, booking.create, verification when needed, status, receipt, and audit event ids.

Trace	What to look for
`reference-dental-booking-create.json`	A complete mandate-gated booking create path
`reference-dental-fail-closed-guardrails.json`	The boundary refusing requests outside the mandate
`reference-dental-idempotent-retry.json`	A retry returning the same logical booking result
`reference-auto-timezone-currency.json`	Merchant-local time and EUR money handling
`reference-notary-remote-service.json`	Remote-service booking shape without a physical address

Openings design-partner example

Openings is the real-platform design-partner example. Openings builds booking software for appointment-based service businesses. They worked with OSBP during the launch work so the protocol could be tested against the shape of a real scheduling platform, not only synthetic fixtures.

That collaboration matters. A synthetic backend can prove the contract is coherent, but a real platform exposes the practical adapter questions: how a service is identified, how policy is read back, how customer verification is handled, how native booking ids are returned, and where a safe handoff is better than pretending the agent can continue. The Openings adapter ships in v0.1.0 as an example of how a booking platform can expose AI-agent booking through OSBP while keeping the platform as the system of record.

The Openings page explains the partner context and the adapter path. It is not a logo wall or a claimed endorsement program; it is a worked example from a launch design partner that helped make the proof more real.

Bring your platform

If you run a booking platform and want to expose it through OSBP, the same path is open to you: implement the seven-method adapter contract from the adapter starter, check it against the conformance kit, and open an issue to compare notes. Openings was the first booking platform to work with OSBP, and we welcome more integrations.