Opt in to the provider index agents read at index.inceptionagents.com: what gets published, how listings are ordered, and how agents consume it over MCP, llms.txt, JSON-LD feeds and HTML pages.

Provider index

The provider index at index.inceptionagents.com is an opt-in directory of businesses whose own sites answer agents directly. An agent that finds you there reads the same briefing, Inception Points and tools your site already publishes, and is pointed back to your own /mcp and express pages to act: request a consultation, ask for a quote, request an appointment, request a callback. Your own domain stays the main place agents find you (/.well-known/mcp.json points them to /mcp); the index is one more.

Status: the index is deployed and has no listings yet, so it is not linked from this site as a directory.

Your listing is off by default. Nothing about your business appears in the index until you switch it on, and switching it off removes the listing with the next write, not the next cron.

What is published

Everything in a listing comes from content your site already serves to agents. The index adds no facts of its own.

Field	Source
Name, domain, vertical and child verticals	Your tenant name, your verified user-facing domain, your services vertical (`legal`, `home-improvement`, `elective-health`, `senior-living`, `multifamily`)
Services offered and referred out	`services.primary`, `services.offered`, `services.not_offered` point facts
Service area	`service_area.*` point facts, or the override you set on the listing
Hours	`hours.*` point facts, or the override you set on the listing
Credentials	`credentials.` point facts that carry both* a proof URL and a verified date. A credential without a proof is not listed.
Reviews	Link-only: the `reviews.*` facts that carry a proof URL become “read the reviews here” links. Scores and review text are never reproduced.
Briefing and points	`https://{your-domain}/agent/briefing` and one `/agent/{slug}` link per published Inception Point
Tools	Every enabled interaction intent: tool name, description, its express URL for action tools, and `read_only` for lookups
MCP endpoint	`https://{your-domain}/mcp` (or the hosted MCP URL on your listing)
Published at	The timestamp of the snapshot that produced the listing

Never published: unverified facts, credentials without a proof, review scores or text, contact details, anything a ServiceTitan connector supplied (its API terms forbid retention and aggregation, so connector-sourced facts are dropped for any business with that connector).

Opt in

The listing needs two things before it can be built: a verified user-facing domain and a services vertical. Once both are in place:

Dashboard. Settings → Provider index listing. The switch lists or removes the business, the listing address sets your public slug (index.inceptionagents.com/{vertical}/{slug}, derived from your company name until you change it), and Republish now rebuilds the listing on demand.
API. GET /api/v1/provider-index/profile returns the row plus a live preview of the listing; PUT /api/v1/provider-index/profile accepts { published, listing_slug, service_area, hours }; POST /api/v1/provider-index/publish rebuilds and rewrites a published listing. All three take your tenant API key.
MCP. From Claude or Cowork on your Inception Agents connector: get_provider_listing, set_provider_listing, publish_provider_listing.

Publishing writes the listing to the index immediately. A snapshot also runs every six hours, so a new credential or tool on your site reaches the index within that window without any action on your side.

Ordering

Listings are flat. Within a vertical they are alphabetical by business name, and that is the only order the index has. There is no paid placement, no “recommended” or “featured” label, no score, no ranking by any signal. find_providers filters by vertical, location and service and returns the matches in the same alphabetical order; the JSON-LD feeds declare themselves ItemListUnordered; every page and every feed says so in its own text. What distinguishes one listing from another is what it can prove: the count of credentials with proofs, the tools it exposes, the service area it states.

How agents consume it

Surface	URL	What it returns
MCP server	`POST https://index.inceptionagents.com/mcp`	JSON-RPC 2.0: `initialize`, `tools/list`, `tools/call`
llms.txt	`GET /llms.txt`	One section per vertical: every provider with its briefing URL, MCP endpoint, tool names, service area and proof count, plus the vertical’s curated query catalog
JSON-LD feed	`GET /v1/{vertical}/feed.jsonld`	An unordered `ItemList` of typed entries (`LegalService`, `HomeAndConstructionBusiness`, `MedicalBusiness` or `Dentist`, `LocalBusiness`) with `potentialAction` targets: a `ReadAction` on the briefing, an `InteractAction` on `/mcp`, a `ReadAction` per Inception Point, and a `CommunicateAction` per express URL
Sitemap	`GET /sitemap.xml`	Every vertical page, listing page and feed
HTML	`GET /`, `GET /{vertical}`, `GET /{vertical}/{slug}`	The vertical list, the alphabetical provider list with the “what to ask, what you get” catalog, and one page per listing

The MCP server exposes three tools, all read-only:

Tool	Arguments	Returns
`find_providers`	`vertical` (required; a top-level or child slug such as `legal-personal-injury`, `roofing`, `med-spa`), `location`, `service`, `limit` (1-50, default 20)	Matching listings, alphabetical, each with briefing URL, point URLs, MCP endpoint, express URLs and tool names. A stated location outside a provider’s service area drops that provider; a match is marked.
`get_provider`	`slug`	One listing in full: services, service area, hours, credentials with proofs, review links, points, tools
`list_verticals`	none	The verticals the index covers with listing counts, feed URLs and each vertical’s curated query catalog

Results carry text for every client and a provider_card widget through _meta.ui for hosts that render MCP Apps. Every vertical also carries a curated query catalog: the questions an agent should ask (“Are you licensed and insured?”, “When is the earliest you can see me?”), the Inception Point on the provider’s site that answers each one, and the action tool that naturally follows. The index and your own site teach agents the same read order.

# Find personal-injury firms serving Boston
curl -s https://index.inceptionagents.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_providers","arguments":{"vertical":"legal-personal-injury","location":"Boston"}}}'

# The same directory as text, and as a feed
curl -s https://index.inceptionagents.com/llms.txt
curl -s https://index.inceptionagents.com/v1/legal/feed.jsonld

Requests are limited to 120 per minute per IP across every surface; over the limit the index answers 429 with retry_after. Fetches are logged by user-agent family (ChatGPT, Claude, Perplexity, Google, MCP clients, SDKs, CLIs, browsers), never by identity: the index is public and unauthenticated, and the only thing worth knowing is which agent families read it.

Google Actions Center

Google’s Actions Center is the one documented multi-merchant consumer of appointment listings today: “Book online” redirect links on Business Profiles in Search and Maps, fed by a partner feed that Google admits by application. The provider index feeds are not a source for it. Whether Google’s AI Mode reads third-party provider feeds is unverified, so treat the index as an MCP-, llms.txt- and JSON-LD-first surface.

Verify your listing

Switch the listing on and open the public URL from the settings card (index.inceptionagents.com/{vertical}/{slug}).
curl https://index.inceptionagents.com/v1/{vertical}/feed.jsonld and confirm your entry’s potentialAction targets resolve on your own domain.
Call find_providers with your vertical and a location inside your service area; your listing should appear with its tool names.
Switch the listing off; the same call no longer returns you.