Help

No — an email address is enough. What guest checkout does, what an ezerve account adds, and how to claim past guest bookings.

From naming your business to a published booking site — the web address rules, what templates seed, and what you can change later.

The three ideas under every ezerve business — assets, offerings, and reservations — and how they fit together.

Weekly hours, seasons, blackout dates, buffers, lead times, and slot granularity — everything that decides which times customers see.

People, places, and things — exclusive or with capacity — and how to decide which shape fits what you rent, staff, or schedule.

Assets are what you have; offerings are what customers book. How requirements and pools turn one into the other.

Where to cancel, what happens to the time slot, and how each business's cancellation deadline works.

The conflict rule lives in the database itself, not in app code — what that means when two customers race for the same slot.

Your own Stripe account, direct charges, and why ezerve never holds or takes a cut of your customers' money.

A flat fee per completed booking on your ezerve invoice — never a cut of a customer payment — with a published definition you can audit to the row.

Read-only REST v1, ezk_ tokens, rate limits, and the MCP server that makes your availability searchable by AI agents.