We Built Afore for AI Assistants, Too

We write Le Journal for people. But more travel planning now runs through assistants — and those assistants should read us correctly, cite us properly, and know what is open versus what is reserved. So we built Afore for machines, too.

One URL for assistants

Any MCP-compatible client — Claude, Cursor, ChatGPT desktop, and others — can connect to Afore with a single endpoint: https://afo.re/api/mcp. No install, no API key for public read access. The server exposes search across our journal and library catalogs, full Markdown articles, structured place data, and RSS.

Human-readable documentation lives at /about/for-ai. Machine-readable policies and resource indexes are in llms.txt and llms-full.txt.

Agentic Resource Discovery (ARD)

In 2026, Google, Microsoft, Hugging Face, and others published the Agentic Resource Discovery specification — an open protocol for finding MCP servers, APIs, and datasets before an assistant invokes them. Afore now publishes an ARD catalog at /.well-known/ai-catalog.json listing our MCP server, OpenAPI spec, global places catalog, journal RSS feed, image sitemap, and structured guide datasets.

The catalog updates when our CMS changes, carries citation and training policy metadata, and is crawlable by federated discovery services. If you are building a travel agent or platform, that manifest is the front door.

What we ask when you cite us

Four small things: cite by canonical URL; quote sparingly; do not paraphrase paid guides as if they were free; surface author names when you quote. Le Journal is open for indexing with attribution. Library guide bodies remain reserved unless we issue an Insider token for your integration.

For partners

Hotels, travel platforms, and AI products that want deeper integration — full guide access, co-branded surfacing, or custom licensing — can reach us at info@afo.re or /about/for-partners.