Three products. Sixty days. A straight answer at the end.

What you get

• Free Search, Enrich, and Decide, plus MCP, for 60 days.
• A Pro-level allowance of 100,000 credits per month, starting at kickoff.
• Structured verdicts for US restaurants: fit, not_fit, or unknown, with reason codes, evidence, and confidence. Evidence depth varies by record.
• Changes and Refresh stay available to every API customer. They are not reserved for partners.
• A kickoff and schema-mapping session, plus a starter integration example.
• A private founder-led channel, with an acknowledgement the same business day.
• Integration-blocking defects get priority. Feature requests get a real evaluation and an honest answer, not a guaranteed build.
• A say in what we build next.
• No cost, and no lock-in.

What we ask of you

• A real integration on the milestone plan.
• Ongoing feedback through the 60 days.
• A straight pay or no-pay answer at day 60. A no, with reasons, is worth more than a polite maybe.
• Permission to name you once you are live: one factual line, in wording you approve. We do not use logos or quotes unless we ask separately. If your company cannot be named, tell us up front. That will not cost you the slot.

Four things we say before you say yes

If any of these breaks your use case, we'd rather find out in the first conversation than in week three.

1. US-only coverage today

   Compass is the dietary layer for US restaurants. International coverage is on the roadmap, not a promise.

2. Vegan and plant-based first

   That is the verdict we return today. Compass is not a general dietary-preferences engine yet.

3. Not an allergy-certification service

   Compass answers vegan and plant-based questions. It doesn't assess allergens or cross-contamination, and it doesn't replace confirming with the restaurant when a decision is safety-sensitive.

4. Data honesty

   Restaurant data changes constantly. Verdicts carry evidence, confidence, and source freshness rather than a freshness guarantee. Where evidence is thin, you get unknown. Read the source policy.

The sixty days

Checkpoints, not deadlines.

• Day 7. First successful API calls.
• Day 30. A working staging integration.
• Day 45. A user-facing pilot. That is a target, and it bends to your release cadence.
• Day 60. The pay or no-pay decision.

At day 60, three ways this ends

The tier and price are agreed before kickoff, so day 60 is a real decision.

Is this you?

• A live product with real users, not a prototype or a waitlist.
• Restaurant recommendations in a core flow, not a side feature.
• A meaningfully US-based audience.

If that's not you yet, the program isn't either — but the API is. Same data, same verdicts, same evidence: we don't keep a better version behind the program.