Verified local business data, with the proof

Local data rots fast. Opening hours change, menus rotate daily, services appear and disappear — and most APIs answer from an aggregator that copied another aggregator months ago. If you run a directory, a comparison site or a local app, you have felt the cost: a user standing in front of a closed door because your data said "open".

ClaimTrace takes the other road: it reads the business's own publications — its website rendered in a real browser, its linked PDFs, even its scanned menu images — and returns each fact with its source URL, date and verbatim excerpt. Seventeen aggregators are explicitly rejected as sources, because a fact you cannot trace to its owner is unverifiable by construction.

What you get per business

• The fact, structured — under the stable ClaimV1 contract: field, value, provenance, confidence.
• The proof — source_url, date read (ISO 8601), verbatim excerpt, whether the domain belongs to the business.
• Anti-homonym identity — the address outweighs the name, so "Café Central" in your town is never confused with its namesake elsewhere.
• Freshness you can check — live revalidation before anything is served from cache (at most 24 h for dated data): confirmed, contradicted or unverifiable, stated as such.
• The honest null — if the business publishes nothing, you get not_found with the reason and the source checked. Your directory can show "not published" instead of stale guesses.

One call

curl -X POST https://claimtrace.dev/v1/fetch \
  -H "X-API-Key: $CLAIMTRACE_KEY" \
  -H "Content-Type: application/json" \
  -d '{"thematique": "restaurants menus du jour", "lieu": "Neuchâtel",
       "prompt": "the actual daily menu, with prices if published"}'

1 credit = 1 business freshly resolved and verified; recently verified facts are served free from the shared cache. Refusals are never charged. See pricing details in the FAQ.

Where it runs today

ClaimTrace is the engine behind arc-menu.ch, which serves verified daily menus in Switzerland in production. The engine has been through 11 external adversarial audits — across the last four, no fabricated menu (91 entities checked one by one on the last two, 31.07.2026). The restaurant vertical is the most mature; other entity types run in generic beta, and when the engine does not know, it says so.