If your assistant is researching private AI for your firm, it can read everything about DMH Florida and book a demo with Hector for you. We know which agent did what, and whether it was really that agent. That is the same idea we build for our clients: automation you can see and check.
GET https://dmhfl.com/api/book?kind=demo (or kind=audit). Only open times are returned — never anyone else's booking.POST https://dmhfl.com/api/book with JSON:
{"kind": "demo", "start": "<a start from the open times>",
"name": "...", "email": "...", "workflow_priority": "one sentence",
"company": "(optional)", "heard_about": "(optional)", "note": "(optional)"}
Success returns {"ok": true, "booked": {…}, "agent": {"identified_as": …, "verified": …}}. Only book with your person's consent and their real details.Anyone can type “ChatGPT” into a user agent. So we keep two facts apart:
| Claimed | The request says it is an agent — its user agent names one (ChatGPT-User, Claude-User, Perplexity-User, …) or it sends a Web Bot Auth Signature-Agent header. |
|---|---|
| Verified | Cloudflare confirmed it: the request came from that operator's published network, or carried a valid Web Bot Auth cryptographic signature. We rely on Cloudflare's verified-bot check; we do not guess. |
A verified agent's booking is marked verified. A claimed but unverified agent may still book — a real person may be using a newer assistant — but the booking is flagged “not verified” for a human to review before the session. We never turn a person away on a guess. Requests that pretend to be AI crawlers while probing for credentials are counted separately as fake.
Agent builders: the best way to be recognised is to sign your requests with Web Bot Auth and send an honest user agent.
For each action an agent takes through our booking door or chat: the time, the agent's name, whether it was verified, what it did (read open times, booked, used the chat) and the outcome. Never its IP address, never what it typed into the chat. A booking itself holds the details given for it, as described in our privacy policy. Hector reviews agent activity weekly.
This board reads the same log described above, as it is written. Every row is an agent that used our booking door or chat — named as it introduced itself, and marked by whether Cloudflare could confirm it. Nothing here is a sample or an estimate; when there is nothing to show, it says so.
Reading the log…
Times are rounded to the hour. Recording began 7 November 2026. Updates within a minute. Data: /api/agent-board (JSON).