# Receptionist Index

> Compare AI receptionists for small businesses: what each one does, whether
> it books into your calendar, and what 100 calls a month really cost.

Receptionist Index lists AI receptionists with their features, prices and
limits. Facts link to their sources, and every listing shows the date we
last checked it.

## The directory right now

- 0 AI receptionists published.

## Machine-readable surfaces (read + cite these)

- https://receptionistindex.com/listings.json — the full Published set as JSON (structured facts per AI receptionist: name, url, tier, categories, tags, pricing, API, last-verified). The machine-readable source of truth.
- https://receptionistindex.com/rss.xml — RSS feed of listings, newest-verified first.
- https://receptionistindex.com/index.md — the home twin: what this index is, the live counts, every category with its published count, the picks and the most-recently re-verified rows. Start here for the entity, then follow a slug.
- https://receptionistindex.com/llms-full.txt — the WHOLE corpus as one markdown document (every listing, answer-first) for one-shot ingestion.
- Per-listing markdown twins at https://receptionistindex.com/{slug}.md — the same researched facts as the HTML page, token-lean.
- https://receptionistindex.com/mcp — the MCP door (JSON-RPC POST): search_listings / get_listing / list_categories / compare_listings / get_best_of (free, keyless reads) + submit_listing (the write door). Full tool schemas: https://receptionistindex.com/.well-known/mcp.json — the same tool list this door serves.
- POST https://receptionistindex.com/api/submit (JSON: url, name, note?) — requires a signed-in account with verified email; send its session Cookie header, including on MCP submit_listing requests. Sign in or explicitly create an account at https://receptionistindex.com/login?next=%2Fsubmit, then verify its email. No session → HTTP 401 {error:'sign_in_required', message, loginUrl}; unverified session → HTTP 403 {error:'email_unverified', message, email, remediation}. Company gate: the account's address, or an address it proved with a code, must be on the submitted website's domain; otherwise HTTP 403 {error:'domain_unverified', message, domain, remediation} — POST /api/domain-proof/start {url, email} mails a 6-digit code to an address at that domain, POST /api/domain-proof/verify {proofId, code} redeems it, then submit again. Personal mailboxes (gmail, outlook…) never prove a domain. Refusals create no account, mail or listing. Identity/email come only from the session. Success returns 201 {id, slug, status:'Draft'}; research + the quality gate decide publication. Your own (url, session email) replay within 24h returns 200; validation returns 400 and duplicate/claim responses 409. Track progress at GET https://receptionistindex.com/api/submissions/{id}. The https://receptionistindex.com/submit form uses the same account-first flow.
- Claim a listing you own at https://receptionistindex.com/claim/{slug} — email-domain verification unlocks the owner dashboard (edits, tier upgrades).
- Category answer sheets at https://receptionistindex.com/category/{slug}.md (+ structured export at https://receptionistindex.com/category/{slug}.json).
- https://receptionistindex.com/.well-known/mcp.json + https://receptionistindex.com/.well-known/agents.json — machine discovery: the MCP door and the narrowed REST operations with I/O descriptors.
- https://receptionistindex.com/index.json — the machine manifest: every surface here, live counts, license, attribution.
- https://receptionistindex.com/license.xml — the RSL 1.0 licence document (application/rsl+xml): what machines may and may not do with this corpus, in machine-readable form.
- https://receptionistindex.com/openapi.json — OpenAPI 3.1 for the read + submit endpoints.
- POST https://receptionistindex.com/api/lead (JSON: name, email, message>=20, consent:true, listingSlug|categorySlug) — send a buyer-intent enquiry to a AI receptionist or category. Keyless, CSRF-free as application/json. Returns { ok, delivered }.
- POST https://receptionistindex.com/api/newsletter/subscribe (form-encoded: email; needs a same-origin Origin header) — single opt-in to the digest. Returns an HTML confirmation.
- https://receptionistindex.com/sitemap-index.xml — every indexable page.
- https://receptionistindex.com/api/search?q=… — full-text + faceted search over the Published corpus (JSON).
- Every listing page carries schema.org JSON-LD (SoftwareApplication, Organization, WebSite, BreadcrumbList) — parse it for citable structured facts, and /{slug}.md for the full sheet.
- Comparison twins at https://receptionistindex.com/compare/{a}-vs-{b}.md — the head-to-head facts table + verdict as markdown.
- Ranked best-of twins at https://receptionistindex.com/best/{category}/{tag}.md — one ranking per category-and-tag intersection as markdown.

## Terms

Reading is free and keyless. Use is licensed, not unconditional:
Receptionist Index Machine Access Terms 1.0
(https://receptionistindex.com/terms): permitted machine use — search,
ai-input; prohibited — ai-train. Attribution required: Data from
Receptionist Index (https://receptionistindex.com). Attribution required:
name Receptionist Index and link https://receptionistindex.com when citing.

Machine-readable terms: https://receptionistindex.com/license.xml — RSL 1.0
(application/rsl+xml), also announced as a License: directive in
https://receptionistindex.com/robots.txt. Human-readable text:
https://receptionistindex.com/terms.

Agents may write as well as read: POST /api/submit and MCP submit_listing
require a verified account session Cookie header. Sign in or create an
account explicitly at https://receptionistindex.com/login?next=%2Fsubmit.
Missing session returns 401 sign_in_required with loginUrl; unverified email
returns 403 email_unverified with remediation; an account not on the
website's domain gets 403 domain_unverified and proves an address there via
/api/domain-proof/start and /verify. Refusals create no account, mail or
listing. Successful Drafts are inert until research + the quality gate clear
them. Checking a submission is open (GET /api/submissions/{id}), and a claim
starts at /claim/{slug}.