SyncSo Partner API — live demo

Real-time local life intelligence for experiences, venues, availability, and local context. The offline world is fragmented, constantly changing, and built for humans rather than machines: information about experiences, venues, events and availability is scattered across hundreds of thousands of sources, buried in unstructured pages, and changing by the hour. SyncSo continuously discovers, structures, labels, verifies, deduplicates and reranks that information — turning fragmented sources into a comprehensive, real-time map of what is happening. An agent reaches it through a single API or MCP connection, with no data pipeline to build and no fragmented sources to maintain. The interactive playground on this page needs JavaScript; everything below describes what it calls.

Three endpoints

POST /partner/api/v1/search — find: Free-text search over live experiences and venues, narrowed by city or coordinates, time windows and filters. Answers in 2–4 seconds. Costs 1 credit per 20 results delivered.
POST /partner/api/v1/featured — discover: A curated, individually scored pool per city, returned without a query, for surfaces where nobody has typed anything. Answers in under a second. Growth plan and above.
POST /partner/api/v1/local-intelligence — decide: Ranks results for a specific person from context you supply — group size, budget, interests, things to avoid, accessibility needs — and returns a written reason per result. Streamed as Server-Sent Events: the first ranked result typically arrives in a few seconds, the full list in 10–33 seconds.

A request

curl https://rtdb.syncso.com/partner/api/v1/search \
  -H "Authorization: Bearer rtdb_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "query": "live jazz",
    "location": {"city": "New York"},
    "time_windows": [{"start": "2026-09-05T19:00", "end": "2026-09-05T23:59"}],
    "limit": 5
  }'

Time windows are local to the target city and carry no UTC offset. Response times are wall-clock at the venue, as {local, timezone}. Request bodies are validated strictly: an unrecognised field returns 422 rather than being ignored.

What a result carries

Title, summary, category and experience type; the schedule with its precision and matched occurrences; venue with address and neighborhood; price; tags and vibe tags; how socially demanding it is; who it suits; images; the booking link and whether signing up in advance is required. Local Intelligence adds a match score and a one-sentence reason built from that result's own facts.

Ticket inventory is not published. The booking link is the authority on whether anything remains.

For AI agents

There is an MCP server, so a client can call this catalogue mid-conversation without writing an integration: https://rtdb.syncso.com/partner/mcp. It exposes search_experiences, recommend_experiences, get_details and list_supported_cities, using the same key, limits and billing as the REST API.

Access

Keys are issued by SyncSo and are server-side credentials. Full manual at syncso.com/partner-api; interactive explorer at rtdb.syncso.com/partner/docs. Request access at hello@syncso.com.