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:
| Skill | Helps you… |
|---|---|
| ------- | ----------- |
dining | find a restaurant or place to eat |
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 to 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 low-mobility, accessible places |
book-tickets | buy tickets for a bookable activity |
make-reservation | reserve a table at a restaurant |
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:
You can authenticate with either an Outgoing API key or an AAuth key —
AAuth keys are auto-provisioned by OpenClaw (see
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.
Pass the user's intent verbatim and fold in timeframe, vibe, group, and any
landmark. One rich prompt beats several thin ones.
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. Overriddenby the contents of the query (e.g. live jazz in Soho)
{ 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.
To buy tickets, use the book-tickets skill (POST /partner/v1/bookings).
共 2 个版本