Dynamite Circle Places API

openapi: 3.2.0
info:
  contact:
    name: DC Team
    url: https://dc.dynamitecircle.com
  description: 'Programmatic access to your DC membership data — trips, events, profile, announcements, and more. Designed for AI assistants, automation, and personal integrations. > **For ALL active DC members.** Every active DC member is eligible from day one — DC, DC BLACK, and trial accounts alike. ## What this is for


    The DC Member API is for **personal use** — wiring DC into your own AI assistant, scripting personal automations, pulling your own data into your own dashboards. Think "give my Claude/Codex/Cursor access to my DC trips and announcements" or "auto-update my DC trip when I book a flight."


    **It is not for:**


    - Building apps that other DC members log into (use the official DC app)

    - Crawling, scraping, or bulk-exporting member data

    - Building an alternative DC client

    - Public-facing services running on top of the API


    We **augment, we don''t replace** — the API gives you awareness and convenience, then sends you to the app for the real interactions. Human stuff stays in the app: no message content, no DM access, no bulk profile browsing, no discussion threads. **Rate limits are strict on purpose.** They''re sized for personal automation, not application traffic. We''ll loosen them once we see real usage patterns — if you hit a wall, email the DC developer team at **bugs+api@dynamitecircle.com** and we''ll sort you out. ## Connect to Claude & other AI apps (hosted MCP)


    This API is also a hosted MCP server — add it as a connector in Claude, Cursor, ChatGPT, or any MCP-compatible app and your assistant can read and act on your DC data directly. **No install.** When prompted, **sign in with your DC account** (one-click OAuth) — or paste a `dk_` API key. Every endpoint below is exposed as a tool. **Connector URL** (Streamable HTTP): `https://api.dynamitecircle.com/mcp`


    - **Claude (web, Desktop & mobile):** Settings → Connectors → **Add custom connector** → paste the URL → **Connect**, then sign in with your DC account. (Paid Claude plan; on Team/Enterprise an admin may need to approve it first.)

    - **Claude Code:** `claude mcp add --transport http dc https://api.dynamitecircle.com/mcp`

    - **Cursor, ChatGPT & other MCP apps:** add a custom / remote MCP connector pointing at the URL above (Streamable HTTP). Discovery is published at `/.well-known/mcp.json`. **What you can do once connected** — ask in plain language, e.g. "Which DCBKK sessions have I bookmarked?", "Add a trip to Lisbon and show me which DCers will be around", "RSVP me to the next Bangkok meetup", "Summarize the latest announcements." Reads run freely; writes do exactly what the matching endpoint documents. Access is scoped to **you** — the connector only ever sees your own membership data. ## Official client — Agent Skill, CLI, Python library, MCP server


    The fastest way to use this API — and to plug it into Claude Code, Codex CLI, Gemini CLI, Cursor, GitHub Copilot, or Claude Desktop — is the **official DC client**. One self-contained Python file, stdlib only, that ships as **four integrations from the same source**: Agent Skill (auto-discovered via SKILL.md), CLI (`dc …`), Python library (`from dc import DC`), and MCP server (`dc --mcp`, optional `mcp` dep). **Install via PyPI** (easiest):


    ```bash

    pip install dynamitecircle

    dc setup --api-key dk_your_api_key

    dc self-test

    dc profile

    ```


    The package is published on PyPI as `dynamitecircle` — same code as the repo, version-locked to the deployed API.'
  title: DC Member Places API
  version: 2.6.11
servers:
- description: Production
  url: https://api.dynamitecircle.com
security:
- ApiKeyAuth: []
tags:
- name: Places
paths:
  /places/search:
    get:
      description: 'Search for places by name. Use this to look up a Google Place ID before creating a trip or referencing a venue.


        Results include a `type` field that classifies each match as `city` (a chapter-level locality usable for trips) or `venue` (a specific establishment, address, or country/region match — usable for events/meetups but rejected by `POST /trips`). Filter on `type === "city"` if you''re building a trip-creation flow; pass either type to event/meetup APIs.


        Every result also includes the full enriched location (`description`, `lat`, `lon`, `region`, `regionCode`, `utcOffsetMins`) so the same payload can be passed straight to `POST /trips` without a follow-up `GET /places/:placeID` lookup.'
      operationId: get_places_search
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  places:
                    items:
                      type: object
                    type: array
                    description: Array of place matches
                    properties:
                      placeID:
                        type: string
                        description: Google Place ID — pass to POST /trips (only when type=city) or to event APIs
                      name:
                        type: string
                        description: Display name
                      type:
                        type: string
                        description: Place type — `city` is usable in `POST /trips`; `venue` is usable in event/meetup APIs but rejected by trips.
                        enum:
                        - city
                        - venue
                      city:
                        type: string
                        description: City (populated when the place resolves to a city; venues outside cities may be null)
                      country:
                        type: string
                        description: Country
                      countryCode:
                        type: string
                        description: ISO country code
                      region:
                        type: string
                        description: Region / state / prefecture (administrative_area_level_1)
                      regionCode:
                        type: string
                        description: Region short code
                      description:
                        type: string
                        description: Google formatted address — usable as a friendly display string
                      lat:
                        type: number
                        description: Latitude
                      lon:
                        type: number
                        description: Longitude
                      latLon:
                        type: string
                        description: '"lat,lon" string'
                      locHash:
                        type: string
                        description: Geohash for the location
                      utcOffsetMins:
                        type: number
                        description: UTC offset in minutes (e.g. 540 for Tokyo)
                type: object
          description: Success
        '401':
          description: Unauthorized — missing or invalid API key
        '403':
          description: Forbidden — inactive membership or not eligible
        '429':
          description: Rate limit exceeded
      summary: Search Google Places
      tags:
      - Places
      parameters:
      - description: Search query (city name, country, address, etc.)
        example: Tokyo Japan
        in: query
        name: q
        required: true
        schema:
          type: string
      - description: Max results (1-20)
        in: query
        name: limit
        required: false
        schema:
          default: '10'
          type: number
  /places/{placeID}:
    get:
      description: 'Fetch full details for one Google Place ID. Useful for verifying a placeID before sending it to `POST /trips` (which only accepts `type: "city"` placeIDs and rejects venues with a 400). Same shape as a single entry from `GET /places/search`.'
      operationId: get_places__placeID
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  place:
                    type: object
                    description: Place details. Same shape as one entry from `GET /places/search`.
                    properties:
                      placeID:
                        type: string
                        description: Google Place ID — pass to POST /trips (only when type=city) or to event APIs.
                      name:
                        type: string
                        description: Display name.
                      type:
                        type: string
                        description: Place type — `city` is usable in `POST /trips`; `venue` is usable in event/meetup APIs but rejected by trips.
                        enum:
                        - city
                        - venue
                      city:
                        type: string
                        description: City (populated when the place resolves to a city; venues outside cities may be null).
                      country:
                        type: string
                        description: Country.
                      countryCode:
                        type: string
                        description: ISO country code.
                      region:
                        type: string
                        description: Region / state / prefecture.
                      regionCode:
                        type: string
                        description: Region short code.
                      description:
                        type: string
                        description: Google formatted address — usable as a friendly display string.
                      lat:
                        type: number
                        description: Latitude.
                      lon:
                        type: number
                        description: Longitude.
                      latLon:
                        type: string
                        description: '"lat,lon" string.'
                      locHash:
                        type: string
                        description: Geohash for the location.
                      utcOffsetMins:
                        type: number
                        description: UTC offset in minutes.
                type: object
          description: Success
        '401':
          description: Unauthorized — missing or invalid API key
        '403':
          description: Forbidden — inactive membership or not eligible
        '429':
          description: Rate limit exceeded
      summary: Get place details
      tags:
      - Places
      parameters:
      - description: Google Place ID. Get one from `GET /places/search` or from a previous response (e.g. `event.city.placeID`).
        example: ChIJ51cu8IcbXWARiRtXIothAS4
        in: path
        name: placeID
        required: true
        schema:
          type: string
components:
  securitySchemes:
    ApiKeyAuth:
      bearerFormat: dk_<userID>_<random>
      description: 'Your DC Member API key. Generate one from the user menu inside the DC member area (admin/tester access required). Send it as `Authorization: Bearer dk_your_api_key`.'
      scheme: bearer
      type: http