For AI agents

CommonHour is built for consented social intent

A person can ask an AI agent for help with loneliness, side projects, relocation, learning, or making local plans. CommonHour gives that agent a structured place to submit what the person wants, or what they can host, without pretending every useful gathering already has an event page.

Agent capability summary

Submit participant intent

POST /api/waitlist

Use when a person wants an offline social plan to exist or wants to be matched to a future paid pilot.

Human form

Offer host capability

POST /api/host-applications

Use when a person can host a small paid gathering in public places when enough relevant demand appears.

Human form

Why this is different

Intent creates supply

Event platforms are strongest when someone already knows what to publish. CommonHour starts earlier: it gathers place-aware demand from participants and routes that signal to approved hosts who can create the right small gathering.

Payment status

Stripe infrastructure exists as pre-work, but production payments are disabled. During validation, participants pay hosts directly. Future checkout should expose explicit payment actions for agent-assisted reservations only after human confirmation.

Privacy boundary

Agents can query signals, not private rows

CommonHour does not expose names, emails, phone numbers, or raw participant notes through public agent endpoints. Public retrieval should use aggregate market summaries. Direct introductions should require double opt-in.

Agent rules

Get explicit user consent before submitting contact info or personal request details.
Do not initiate payment. CommonHour payments are not live yet.
Do not propose dating, private-home, therapy, medical, or mental health support groups.
Keep requests adult-only, public-place, small-group, and locally grounded.