Outgoing — The AI-First Index for Ephemeral Events and Activities

Outgoing is an AI concierge for the real world: turn any "what should we do?" into a short, ranked list of real places and events, and automatically book tickets or make reservations when you're ready.

Use this general skill for everyday "what's on / where should we eat" requests at home, as well as detailed planning when you and your family are traveling.

We offer many skills specifically tuned to get you better results for common scenarios:

How it works

Calls the Outgoing API (GET /partner/v1/search) — one natural-language search returns ranked, personalized, high-quality events and activities. Full reference (auth, every parameter, booking, schemas) as plain Markdown: \x3Chttps://www.outgoing.world/llms.txt> and \x3Chttps://www.outgoing.world/llms-full.txt>.

Setup

You can authenticate with either an Outgoing API key or an AAuth key — AAuth keys are auto-provisioned by OpenClaw (see \x3Chttps://www.npmjs.com/package/@aauth/mcp-openclaw>). If you're not using AAuth, request an API key with the partner scope and store it in an env var:

export OUTGOING_API_KEY="og_api_…"   # partner scope — get one at https://outgoing.world

For Claw, usually your agent will act on behalf of a single user account, but you can provision additional users (e.g. for a partner or family member) and pass that id as X-External-User-Id.

Formulating your prompt

Pass the user's intent verbatim and fold in timeframe, vibe, group, and any landmark. One rich prompt beats several thin ones.

• "what's on tonight in SoMa — drinks and live music"
• "low-key things to do this rainy Sunday afternoon"
• "best outdoor music near the Eiffel Tower next weekend"

Running the search

curl -sS -G https://api.outgoing.world/partner/v1/search \
  -H "Authorization: Bearer $OUTGOING_API_KEY" \
  --data-urlencode "prompt=live jazz and a late dinner tonight" \
  --data-urlencode "city=paris"

• city — an optional hint to ground the search, if the query doesn't specify enough. Overridden by the contents of the query (e.g. live jazz in Soho)
• Returns { message, activities[] }; each activity has activity_id, name, short_description, semantic_location, is_bookable, ticket_price, ….

Lead with the message, then list picks: name, one-line short_description, neighborhood (semantic_location), and the price label when is_bookable. Render picture_url where supported. Only report what the API returns — never invent venues, prices, or availability.

Booking (optional)

To buy tickets, use the book-tickets skill (POST /partner/v1/bookings).