# Find a Time — meet.pawpawanalytics.com

> Free, no-sign-in group scheduling: propose times, share a link, collect
> availability. This file tells an AI agent how to drive the whole flow over a
> small no-auth JSON API — no MCP install and no page scraping. Every path below
> is relative to https://meet.pawpawanalytics.com and needs no authentication.

## Create an event (you have a request and need links to share)

POST /events
Content-Type: application/json

    {
      "title": "string",
      "timezone": "IANA name, e.g. America/Chicago",
      "slot_minutes": 15 | 30 | 60,
      "availability": {            // high-level grid; expanded server-side
        "start_date": "YYYY-MM-DD",
        "end_date":   "YYYY-MM-DD",
        "weekdays":   [1,2,3,4,5], // ISO 1=Mon..7=Sun, or a preset name:
                                   // "weekdays" | "everyDay" | "weekends"
        "window_start": "HH:MM",   // 24h wall-time in the event timezone
        "window_end":   "HH:MM"    // exclusive end
      }
    }

Instead of "availability" you may send exact slots:
"slot_starts": ["<UTC ISO-8601>", ...].

The response carries "_links" — the invite and results pages to hand to the
people you're scheduling — and "_actions", the same respond/density URLs below.

## Read an event (you were handed a share link)

A share link looks like /e/<event_id>; the event id is that UUID.

GET /events/<event_id>
  → { title, timezone, slots: [{slot_id, starts_at}], _actions: {...} }

starts_at is UTC ISO-8601 — render it in the returned "timezone" to label each
slot for your user.

## Respond on someone's behalf

POST /events/<event_id>/responses
Content-Type: application/json

    { "name": "string", "slot_ids": ["<slot_id>", ...] }

Submit this exactly ONCE — responses are not de-duplicated.

## See who overlaps where

GET /events/<event_id>/density
  → [{slot_id, starts_at, count, names}]

## Notes

No authentication or sign-in is required for any endpoint above.