Compass developer docs

Vegan dishes and supporting evidence for US restaurants, for travel planners and AI assistants.

Quickstart

Go from a key to Search, Enrich, and a Decide verdict.

Integration patterns

Match records you already have, or discover first, then store compass_id and decide.

MCP server

Install Compass in Claude Desktop, Cursor, or Codex.

API reference

Read endpoint contracts, examples, fields, and error behavior.

Transparency

Review source tiers, evidence policy, and conservative output rules.

Which surface should I use?

Field	Type	Notes
MCP server	Agent tools	Start here when your host can install MCP, such as Claude Desktop, Cursor, or Codex.
REST / OpenAPI	Production apps	Use this when your backend needs exact HTTP contracts, auth behavior, errors, and response schemas.
Examples	Copy-paste requests	Use the Quickstart and Integration patterns examples. OpenAPI remains the source of truth. Compass does not publish a client SDK.

Field	Type	Notes
Search	Entry point — discovery	Search with a user profile, then Decide on the result your user selects.
Enrich	Entry point — your records	Enrich a record you already have, store the compass_id, then Decide.
Decision	The verdict	Every chain ends here: fit, not_fit, or unknown for one profile.
Changes	Supporting sync	Changes lists create, update, and delete signals and is not a complete deletion record.

Start here

Search, Enrich, and Decide are the three core APIs. Changes supports synchronization. It is not an extra verdict API. Responses include reason codes, evidence pointers, confidence, and verification guidance.

Read the quickstart