Developer Docs

Agent booking API.

Server-to-server booking endpoints for outside AI agents. Use this surface to discover the allowed routes for your key, fetch open consultation slots, create bookings, and monitor your current rate-limit budget.

Outside booking integrations should use the dedicated /api/agent/* surface documented here, not internal /api/admin/* management routes.

View rendered API reference Admin key manager

Rendered reference

Human-readable API reference rendered from the live OpenAPI contract.

OpenAPI schema

Raw JSON contract for OpenClaw, HTTP wrappers, and generated clients.

Admin key manager

Provision and revoke booking keys in Admin -> Settings -> Agent Keys.

Booking page

Public booking UX that also links back to this API surface.

Resources hub

Return to the broader WERZ guides and resources index.

Provisioning

Admin setup for booking keys.

The public contract is self-serve for agents. Key provisioning is admin-managed. Create or revoke keys in the WERZ admin, then hand the key to your booking tool together with this docs page or the raw OpenAPI contract.

Provision keys in admin

Admins can create agent keys, choose scopes, set a rate limit, and copy the docs URL from the dedicated settings screen.

Open agent key manager Raw schema

bookings

Outside booking agents

Recommended for OpenClaw, ChatGPT tools, Claude tools, and other third-party booking agents. This scope can use the documented `/api/agent/*` surface only.

bookings-admin

Internal booking management

Internal-only scope for automations that need `/api/admin/bookings*` access, including booking records and mutations. Do not give this scope to outside agents unless you explicitly need internal booking-management access.

Quick Start

Integration flow.

Admins create keys in Admin -> Settings -> Agent Keys. For outside agents, start with the `bookings` scope and the `MANAGER` role.

Call `GET /api/agent/capabilities` first to confirm which routes and scopes the current key can use.

Call `GET /api/agent/booking/availability?start=YYYY-MM-DD&end=YYYY-MM-DD` to inspect open slots.

Submit `POST /api/agent/booking` with `name`, `email`, `phone`, `date`, and `startTime`.

Use `GET /api/agent/rate-limit` when needed to monitor remaining quota and reset timing.

Endpoint Reference

What agents can call.

GET/api/agent/capabilities

Manifest discovery

Returns the endpoints and scopes available to the current caller. Scoped keys only see the routes they can actually use.

GET/api/agent/booking/availability

Availability lookup

Returns open 30-minute consultation slots within the public booking window.

POST/api/agent/booking

Booking creation

Creates a confirmed consultation booking. Retries for the same confirmed email/date/time return the existing booking.

GET/api/agent/rate-limit

Quota status

Returns the current remaining quota and reset time for the calling agent key.

Examples

Example requests.

Capabilities

curl -H "Authorization: Bearer wrzk_your_key" \
  https://werz.ai/api/agent/capabilities

Availability

curl -H "Authorization: Bearer wrzk_your_key" \
  "https://werz.ai/api/agent/booking/availability?start=2026-03-20&end=2026-03-21"

Booking

curl -X POST \
  -H "Authorization: Bearer wrzk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Taylor Example",
    "email": "taylor@example.com",
    "phone": "+15555555555",
    "date": "2026-03-20",
    "startTime": "10:00",
    "source": "chatgpt"
  }' \
  https://werz.ai/api/agent/booking

The booking route requires a real callback number, and duplicate retries for the same confirmed email, date, and start time return the existing reservation rather than creating a second booking. All agent endpoints can also return 429when a key exceeds its rate limit; respect the Retry-After response header before retrying.

API Reference

Rendered OpenAPI reference.

Use the rendered reference below for human review, or the raw schema for tool wrappers and generated clients such as OpenClaw integrations.

Loading rendered API reference...