Standard endpoints, real businesses
If you’re building an assistant, an agent, or an agentic product: every published CoreLoop business serves llms.txt, speaks MCP and A2A on whichever of those channels its owner has switched on, and appears in our agent-queryable directory by default unless its owner opts out. No partnership required. The endpoints are open.
From website to agent-ready
No integration project and no partnership. Each published business serves its own llms.txt file; MCP and A2A follow the owner’s per-channel switches, and the directory listing is on by default unless the owner opts out.
A business publishes
CoreLoop crawls their website and builds a structured, typed business profile.
Endpoints go live
Each profile serves llms.txt from the moment it is published, plus MCP and A2A endpoints with an agent card on whichever of those channels the owner leaves switched on.
Your agents build on it
Query any published business with its AI connections switched on, through open standards, with no per-site integration.
Standard endpoints, no lock-in
MCP, A2A, the agent card, and llms.txt are open specifications. Point your agents at the URLs. There’s nothing proprietary to adopt.
Get started freeBuild on open standards
MCP endpoints
Every published business that leaves its MCP connection switched on serves Model Context Protocol tools at a stable URL: services, hours, prices, policies, inquiries.
A2A agent cards
Published businesses with their A2A connection switched on can be discovered and worked with through the open agent-to-agent standard, agent card included.
The directory
Search published businesses listed in the directory, by what they do and where. Built for agents, not scrapers.
Structured profiles
Crawled websites become clean, typed business data your agents can rely on.
llms.txt
A machine-readable summary of every business, ready for LLM ingestion.
WebMCP embed
From the Pro plan, once their website code is verified, businesses register the same read-only tools on their own site with one script tag, alongside the page shortcuts and form pre-fill they approve. The same open standard.
Every published business with the relevant AI connection switched on is queryable today over MCP and A2A, and the cross-business directory endpoint finds one across the whole network — no account or API key required.
Go deeper
Agent protocols overview
The technical reference for CoreLoop’s agent surfaces, MCP, A2A, llms.txt, and WebMCP, and the gates every request passes through.
Read the referenceMCP endpoint
Per-business MCP servers over Streamable HTTP, seven auto-generated tools, locale negotiation, tier-based rate limits, and full interaction logging.
Read the referenceWhere each tool is offered
The Access tab — choosing which channels carry each of your tools, how it sits alongside the channel and tool switches, and how fast a change takes effect.
Read the referenceWhat happens when an AI agent asks about your business
A technical walkthrough of one MCP request, the gates it passes, the tool that answers it, and the log line it leaves behind.
Read the referenceExplore the rest of CoreLoop
Build on agent-ready business data
Every published CoreLoop business speaks the open protocols on the channels its owner has switched on. Point your agents at the endpoints and start building.