Discover Events in Any City

Find and book real-world things to do — restaurants, bars, concerts, comedy, museums, events, and activities — via natural-language search. The general entry point to Outgoing; use it for any "what should we do / where should we eat / what's on near me" request, or route to a narrower companion skill when the occasion is specific (date-night, kids-weekend, trip-planning, work-meetup, enjoy-nature, friends-hangout, meet-new-people, pet-friendly, stay-active, accessible-outings) or the user wants to buy tickets (book-tickets). Works in cities worldwide.

Outgoing — things to do

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 book tickets when you're ready.

Use this general skill for everyday "what's on / where should we eat" requests. For a specific plan, prefer the matching companion — each is tuned to get you better results:

Skill	Helps you…
date-night	plan a romantic night out for two
kids-weekend	find family- and kid-friendly fun
trip-planning	make the most of a visit to a new city
work-meetup	pick the right spot for a client dinner or meeting
enjoy-nature	get outside — parks, gardens, scenic walks, hikes
friends-hangout	round up a fun night with a group
meet-new-people	find welcoming social events to meet people
pet-friendly	bring your dog or pet along
stay-active	do something sporty and active
accessible-outings	find step-free, wheelchair-accessible places
book-tickets	buy tickets for a bookable activity

How it works

Calls the Outgoing Partner API (GET /partner/v1/search) — one natural-language search returns up to 20 ranked, real venues/events. Full reference (auth, every parameter, booking, schemas) as plain Markdown: https://www.outgoing.world/llms.txt and https://www.outgoing.world/llms-full.txt.

Setup

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

Provision each end user once (POST /partner/v1/users with their external_user_id), then pass that id as X-External-User-Id on every call. A 404 means provision them first (details in llms.txt).

Search

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

• city — the city to search, lowercase with underscores (e.g. paris, new_york, tokyo, mexico_city). Defaults to new_york. Outgoing is global — pass whatever city the user names.
• Returns { message, activities[] }; each activity has name, short_description, semantic_location, is_bookable, ticket_price, ….
• Optional lat/lng center the search on a landmark or neighborhood.

Shape the 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 dinner near the Eiffel Tower for four people"

Present & book

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. To buy tickets, use the book-tickets skill (POST /partner/v1/bookings).