# AxiomOS · design partner chat with utkarsh maurya

> let’s talk about what you’re building, how you test and deploy changes to your robots, and what happens when an update goes wrong. i’m building AxiomOS, a runtime-programmable kernel for robots, and looking for early design partners to shape it around real engineering problems. we’ll spend 20 minutes understanding your setup and exploring one concrete problem we could tackle together. this is an exploratory conversation, not a commitment to a pilot. you don’t need slides or a demo.

- Host: utkarsh maurya
- Duration: 20 min
- Location: Cal Video
- Host time zone: Asia/Kolkata
- Confirmation: Bookings are confirmed instantly.
- Booking page: https://cal.com/utkarsh-maurya/axiomos
- Event type id: 6988710

## Check availability

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