—Proof
Sample certificate, public verification page, and the API surface — three things a buyer, partner, adjuster, or clerk can click into right now. That's what proof should look like.
01Inspectable today
Public surfaces anyone can examine. They show how the certificate is structured, how verification works, and how the API exposes the reservation and signing flow.
A clearly marked sample showing the packet text, per-item acknowledgments, drawn signature, audit trail, content hash, and QR verification path.
Generated from the same certificate renderer used by signed reservations.
A no-login verify page recomputes the certificate HMAC and returns a public verdict without exposing guest PII.
Backed by functions/api/verify/[hash].js and the PDF QR token.
The public REST API describes reservation, certificate, and webhook surfaces that partners can integrate against.
developers.prearrive.com hosts the reference, test mode, idempotency, and versioning guides.
02Limit
A signed acknowledgment makes a file clearer: what the guest saw, what they tapped, when they signed, and whether the certificate still verifies. It does not decide whether Airbnb, an insurer, or a court agrees with the host — and the marketing here will never pretend otherwise.
Open the sample certificate, verify the chain, and start free. Free covers one property.