Agent access

Bring your own agent

APEX speaks Model Context Protocol. Point any MCP-capable AI at the endpoint below and it can search the site, pull business facts, check live availability, and carry a booking to checkout — the same rails our Concierge runs on.

Site MCP endpoint

https://www.apex-drive.co/_api/mcp

Streamable HTTP · JSON-RPC · no key required

Wire it up

Claude Code

claude mcp add --transport http apex https://www.apex-drive.co/_api/mcp

Claude.ai & Claude Desktop

Settings → Connectors → Add custom connector — paste the endpoint, no authentication step.

Any MCP client

{
  "mcpServers": {
    "apex": { "type": "http", "url": "https://www.apex-drive.co/_api/mcp" }
  }
}

Then say something like

“Find me something fast at apex-drive.co this Saturday morning, under €600 — search the site over its MCP endpoint, check real availability, and hand me the booking link.”

What your agent gets

SearchInSite
Full-text search across the sessions, the About story, and the FAQ.
GetBusinessDetails
The business card — name, locale, and how to reach the outfit.
GenerateVisitorToken
A scoped visitor identity, no account required.
CallWixSiteAPI
The big one: the live service catalog, real availability, and the booking flow.
SearchSiteApiDocs
With the docs readers alongside it, the agent discovers API shapes on its own.

Nine tools on the endpoint; these five do the booking.

Already machine-readable

  • llms.txt — the curated map, with live session names and prices
  • llms-full.txt — the map plus the full About story and FAQ, generated per request
  • JSON-LD — Service, Offer, ReserveAction, and FAQPage structured data on the relevant pages

And the proof it all works: the Concierge riding the corner of every page books through this same endpoint. We run on our own rails.