# Dave Ingle – Cal.com booking page

> Helping teams prove what their AI systems did — before and after things go wrong.

Focus: agent actions, provider drift, and evidence you can actually defend.

Booking page: https://cal.com/vertrule

## Event types

- [AI Workflow Failure Review](https://cal.com/vertrule/review): 15 min, confirmed instantly, event type id 5601214. We’ll look at one AI workflow and where failures are hardest to explain or prove (agent, provider, or system). Goal: • Identify where things break down • Pinpoint what you can’t currently prove If there’s a gap, I’ll show how teams are making this defensible. No prep needed. Details: https://cal.com/vertrule/review.md
- [AI Evidence Deep Dive](https://cal.com/vertrule/deep-dive): 30, 45 min, confirmed instantly, event type id 5601215. We’ll go deeper on a real workflow. Goal: • Walk through how failures actually occur • Map what evidence exists today • Identify gaps across agent, provider, and system layers • Outline what a defensible setup would look like Best if you already have something in production or actively being built. No prep needed. Details: https://cal.com/vertrule/deep-dive.md

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=<event type id>&start=YYYY-MM-DD&end=YYYY-MM-DD&timeZone=<IANA time zone>
cal-api-version: 2024-09-04
```

The response is `{"data":{"YYYY-MM-DD":[{"start":"<ISO 8601 with offset>"}]}}`; no API key is needed.

## Book

Each event type's `.md` document lists its required booking fields and the `POST https://api.cal.com/v2/bookings` request (`cal-api-version: 2026-02-25`).

## More

- API docs: https://cal.com/docs/api-reference/v2/introduction
