# Intro call — LLM reliability audit with Arjun Ponnaganti

> 20 minutes to find out whether a reliability audit fits your situation. You describe the AI feature you've shipped and where it's causing trouble — outputs nobody can verify, manual checking before every release, prompt changes that fix one case and quietly break three others. I'll tell you whether the audit helps. If it doesn't, I'll say so and point you somewhere useful. No deck, no pitch.

- Host: Arjun Ponnaganti
- Duration: 20 min
- Location: Cal Video, Google Meet
- Host time zone: Europe/Berlin
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/arjunworks-intro-call/llm-reliability-audit
- Event type id: 5257045

## Check availability

```http
GET https://api.cal.com/v2/slots?eventTypeId=5257045&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

```http
POST https://api.cal.com/v2/bookings
cal-api-version: 2026-02-25
Content-Type: application/json

{
  "eventTypeId": 5257045,
  "start": "<UTC ISO 8601 start from the slots response>",
  "attendee": {
    "name": "…",
    "email": "…",
    "timeZone": "<IANA time zone>"
  },
  "guests": [
    "guest@example.com"
  ],
  "bookingFieldsResponses": {
    "notes": "…"
  }
}
```

- Required fields: `name` (Your name), `email` (Email address)
- Optional fields: `notes` (Additional notes), `guests` (Add guests)
- `name` and `email` go in `attendee` and `guests` is a list of emails; every other field goes in `bookingFieldsResponses` under its name.
- `location` is optional; without it the booking uses the event’s first location.