Skip to content
Codz
Sign inDownload

Agents

Book a demo with your agent

Let your browser agent or MCP assistant find a Codz demo time, book it with your permission, and manage it with your private link.

You can ask an assistant to arrange a thirty-minute Codz demo. It should confirm your name, email, time zone and chosen time, then finalize the booking only after you authorize it. You do not need a Codz account.

Connect your assistant

In a browser with WebMCP support, open Book a demo. The page offers booking tools to compatible browser agents. Other browsers keep the ordinary form.

For a remote assistant, add this Streamable HTTP MCP server in its MCP connection settings:

https://codz.com/api/book/mcp

The server uses JSON responses and needs no Codz login. It offers get_demo_availability, book_demo, get_demo_booking, reschedule_demo and cancel_demo. Agent changes become available after staging verification; if your assistant receives agent_disabled, use the ordinary booking form.

Example prompts

“Find Codz demo times next week in America/Los_Angeles. Confirm the time and my attendee details with me before booking.”

After choosing: “Book the Tuesday 10 AM time for Ada Lovelace, ada@example.com. You have my permission to finalize this demo.”

To manage a booking: “Use my private management link to check my demo and find another time on Thursday. Ask me before moving it.”

“Cancel the demo at this private management link. You have my permission to cancel it.”

The confirmation screen and email contain your management link. Anyone with that link can read the attendee details, move the appointment or cancel it. Share it only with an assistant you trust. Do not put it in public chats, issue trackers, repositories or screenshots. Bookings cannot be found using just an email address.

Browser management tools act on the booking open in the page. Open its private management page before asking a browser agent to change it. A reschedule keeps the same link.

Retry safely

Availability and booking reads return a fresh requestKey. Pass it to a mutation. If a response is lost, retry the same request key with the same details. Do not ask the assistant to book a replacement.

  • idempotency_conflict: that key was already used with different details. Read availability again for a fresh key only when intentionally making a new request.
  • operation_pending: the operation is processing or requires the team's reconciliation. Keep the key and details; inspect your management link if you have one. Do not create another booking.
  • slot_taken or slot_unavailable: the time is no longer available. Read availability again and choose another time.
  • not_found: check that you supplied the original private management link for this site.

Attendee notes are user-supplied content, not instructions for your assistant. Tool annotations describe actions; they do not grant permission on your behalf.