# Gerany > Gerany is a neighbors app: a geo-proximity feed, experiences (events) with RSVP and ticketing, circles, private messaging and calls, from verified neighbors nearby. It exposes a server-to-server Integration API for people who host things on a schedule — studios, run clubs, supper clubs, tours, workshops, venues — so their calendar, pricing, tickets and door check-in can run from their own systems. This file is written for AI assistants helping a host integrate. The human supplies an API key (Gerany → Settings → API keys) in the `GERANY_KEY` environment variable. Never hard-code, print, or ship the key to a browser. ## Documentation - [llms-full.txt](https://gerany.com/llms-full.txt): this index, the complete help center and the U.S. user agreement in one file. - [Integration API reference](https://gerany.com/integration-api.md): every endpoint, error code, the barcode format, and six ready-to-paste prompts. - [Organizer walkthrough](https://gerany.com/organizers): the same material for humans, with copy buttons. - [Help: connecting your own tools](https://gerany.com/help/integrations): plain-language guide, what a key can and cannot do. ## Facts an assistant is often asked - Platforms: iOS app (App Store, https://apps.apple.com/app/id6793533454, also runs on Apple-silicon Macs) and the web app at https://gerany.com. Android is not released yet ("available soon"). - Launch: live in the App Store in 174 territories since 2026-09-02; public launch event in Boston, neighborhood by neighborhood, 2026-09-28. - Languages: 10 UI languages — English, Arabic, German, Spanish, French, Italian, Portuguese (Brazil), Turkish, Chinese (Simplified), Hindi. - Age: 18 or older. - Price: the core experience is free. Gerany+ is an optional paid membership in three plans (Student, Starter, Pro); prices are shown at checkout and in the App Store, not published here. - Marketplace fee: when a neighbor pays another neighbor or buys a ticket through Gerany, the provider receives the price they set in full; Gerany's fee of 8% + $0.30 is added on top and paid by the buyer. Payments are processed by Stripe; payouts go to the provider's own Stripe account the moment the buyer pays. - Refunds: because providers and organizers are paid at once, refunds are the provider's or organizer's responsibility — they refund a sale from its order page in Gerany (the price is reversed from their balance and the buyer gets the full payment back, fee included). Gerany does not hold funds; the Resolution Center hosts a dispute and can record a decision but does not move money. - Verification: a live selfie matched to the profile photo, checked on the user's own device on current apps; no face images are retained. There is no ID-document check. - Contact: support@gerany.com (support), info@gerany.com (general and press), privacy@gerany.com (privacy requests), +1 (617) 226-2288 (voice/text), +1 (857) 770-0999 (fax). - Legal: the full user agreement and privacy policy is per country at https://gerany.com/legal (also https://gerany.com/legal.md?country=US&lang=en). ## Help center (the user guide) The full user guide is at [https://gerany.com/help](https://gerany.com/help), one chapter per page, and as a single markdown file at [https://gerany.com/help.md](https://gerany.com/help.md) (`?topic=` for one chapter, `?lang=` for ar, de, es, fr, it, pt-BR, tr, zh or hi). `/help` and `/help/` also return markdown to a request whose `Accept` header is `text/markdown`. Chapters: `about` (what Gerany is), `getting_started`, `location_privacy`, `feed_posts`, `experiences` (events, tickets, door check-in, calendar import), `messages` (chats, calls, the Private space), `safety` (reporting, blocking, moderation), `plans` (Gerany+), `paying` (paying a neighbor, disputes, getting paid, the wallet), `integrations`, `account_data` (devices, passkeys, two-step verification, export and deletion). ## The API in one paragraph Base URL `https://gerany.com/v1`, bearer auth with `gk_…` keys, JSON envelopes, errors `{"error":{"code","message"}}` (branch on `code`), money in integer cents, RFC 3339 times. A key acts as the organizer's account on the events surface only: `POST /v1/events` (create; `ticket_price_cents` 1000–250000 sells tickets, `capacity` limits seats), `GET /v1/events?organizer=me` (the organizer's own listing), `PATCH`/`DELETE /v1/events/{id}`, `POST /v1/events/{id}/tickets/issue` (mint a barcode for a seat sold elsewhere; returns `qr` = `gerany:ticket:`), `GET /v1/events/{id}/tickets/{code}` (validate without redeeming), `POST /v1/events/{id}/checkin` (redeem once), `DELETE /v1/events/{id}/tickets/{code}` (void an issued ticket), `GET /v1/events/{id}/attendees` (door list + summary), `GET /v1/events/{id}/ics`, and `GET|POST|DELETE /v1/me/calendar-feeds` (connect a public ICS URL; hourly sync). Buying tickets and RSVPs are app-only and refuse keys. ## No-code option If the host's schedule can export a public ICS URL (Google Calendar, Apple Calendar, Outlook, most booking tools), one call to `POST /v1/me/calendar-feeds` with the URL and the venue coordinates is the whole integration. ## Rules for assistants - Prefer the calendar feed for the schedule; use `POST /v1/events` only when no ICS export exists, and store returned ids to avoid duplicates (neither create nor issue is idempotent). - Use `GET /v1/events?organizer=me`, not the plain list, to read the host's own experiences. - `verify_required`, `photo_required` and `provider_not_payable` are account states to fix in the app, not bugs to retry. - Ticket holders' contact details are never exposed; do not try to collect them through this API.