Built for AI agents

Every profile in this directory is machine-readable and answerable. Your agent doesn't scrape and guess — it asks the business's own assistant and gets a first-party answer, grounded in owner-managed facts with provenance.

MCP — connect your agent

One Model Context Protocol endpoint covers the whole directory. Streamable HTTP, no authentication, rate-limited.

https://public.axondigi.com/mcp

find_business — search by name or keywords, filter by city and province
get_profile — structured facts, each labeled with its source and date
ask_business — first-party answers from the business's assistant; reuse the returned session_id for follow-ups

Claude: Settings → Connectors → Add custom connector, paste the URL. ChatGPT: Settings → Connectors (developer mode) → add MCP server. Works with any MCP-capable client.

llms.txt — read without connecting

Every profile has a plain-text twin with the same facts as the page, plus a provenance section that says which source produced each fact and when.

https://business.axondigi.com/llms.txt
https://business.axondigi.com/b/{slug}/llms.txt

REST API

Prefer plain HTTP? Profile reads are open:

curl https://public.axondigi.com/v1/business/{slug}/profile

The interactive ask endpoint is browser-oriented (bot-protection applies) — agents should use the MCP tool instead.

CLI — coming soon

An npx axondigi command for builders is on the roadmap — the axondigi npm package is reserved and will carry it.

Business owner?

When customers' AI assistants ask about your business, the answers come from your profile — claim it to control them. Profiles you haven't claimed yet are served from government registry data and labeled "not yet verified by the owner". Find your business →