The standards your page speaks

MCP — Model Context Protocol

The open standard AI assistants use to connect to external sources and ask structured questions. Assistants that speak MCP can query a business directly — services, hours, locations, reviews — instead of guessing from an old web crawl.

What CoreLoop serves A public MCP server per published business, Streamable HTTP transport, with auto-generated tools: get_info, get_services, check_availability, get_reviews, compare_services (when a category has two or more services), and send_inquiry — the one deliberately limited write path. Responses are bounded, locale-negotiated (?locale, then Accept-Language), and carry last_updated, verified, and data_source metadata. Rate limits scale by plan. Alongside it, a network router serves the whole directory from ONE endpoint: search_businesses finds a business, and get_business_info, get_business_services, compare_business_services, check_business_availability, get_business_agent and send_business_inquiry then query or contact it without changing endpoints. (coreloop.so/api/mcp/directory is the older path for the same router and is still served.)

• coreloop.so/api/mcp/{business}
• coreloop.so/api/mcp/coreloop-directory

Who uses it AI assistants answering “find me a…” and “how much is…” questions; developers building agents that need reliable business data.

Full reference

A2A — Agent2Agent

The protocol agents use to discover and converse with each other. When a booking helper or a partner’s assistant needs to talk to your business, this is the standard it expects.

What CoreLoop serves A full A2A v1.0 endpoint per business (ProtoJSON wire format): SendMessage and SendStreamingMessage over SSE, standard task states, stateless tasks, and version negotiation, plus a statically cacheable agent card advertising supported interfaces and the languages the business speaks. Conversations happen in the caller’s chosen supported language. And like MCP, the whole network speaks A2A from ONE endpoint: the CoreLoop agent card at the root well-known address advertises three skills — find a business, compare businesses, and route a question or inquiry to a business found — so an A2A agent connects once and reaches the whole network. Each business’s own protocol switches are honoured: the router reaches exactly the businesses that are published with A2A enabled.

• coreloop.so/api/a2a/{business}
• coreloop.so/{business}/.well-known/agent-card.json
• coreloop.so/api/a2a/coreloop-directory
• coreloop.so/.well-known/agent-card.json

Who uses it Agent-to-agent ecosystems, multi-agent products, and partner integrations.

Full reference

WebMCP — tools in the page

A browser capability: tools registered inside a web page that an AI assistant in the visitor’s browser can call directly, with page context.

What CoreLoop serves In-page tool registration on the CoreLoop Page from the Starter plan and, from the Pro plan, on an active custom domain and — once the business’s website code is verified — on the business’s own site; not included on Free. Each channel is authorised per verified origin and carries its own owner switch. An assistant working in the visitor’s browser calls the read-only profile tools on the page it is already on. CoreLoop-generated page shortcuts (open a page, read a section) and form pre-fill currently exist only on the verified own website: the owner approves each one, CoreLoop re-checks it and pauses it when the page changes, and on an approved form the assistant pre-fills fields the visitor supplied after the visitor confirms on the page — CoreLoop never submits.

• Registered in-page on coreloop.so/{business}, and on snippet-verified customer sites

Who uses it Assistants working inside the visitor’s browser.

Full reference

llms.txt — the discovery file

A plain-text convention AI crawlers check for a machine-readable summary of a site, and pointers to more.

What CoreLoop serves A per-business llms.txt generated live from the current profile on every request (name, description, services, hours, locations, contact, plus pointers to the MCP endpoint and the page), and a platform-wide file at the root. Served in the business’s content language by design; locale negotiation happens at the live endpoints it points to.

• coreloop.so/{business}/llms.txt
• coreloop.so/llms.txt

Who uses it AI crawlers and any agent doing first-contact discovery.

Full reference