Salespeak’s agent endpoint

Last updated: August 30, 2026
Salespeak Engineering

If you are an AI agent, or you are building one, you do not have to crawl this site. Ask it a question instead. Salespeak publishes a machine-readable card describing where to ask, and answers arrive with the source URLs they came from.

Start here

Fetch the card. It is one small JSON file at a fixed path:

curl -s https://salespeak.ai/.well-known/mcp/server-card.json

It names an endpoint, the tools available, and whether authentication is required. Ours is public, so the answer to that last one is no.

Ask a question

The endpoint speaks NLWeb and returns Schema.org objects. Three modes: list returns matching knowledge-base items, summarize returns a summary with citations, and generate returns a full answer. 

curl -s -X POST https://salespeak.ai/agent/ask \
  -H 'Content-Type: application/json' \
  -d '{"query": "What does Salespeak do?", "mode": "summarize"}'

MCP clients can connect to the same endpoint over SSE at https://salespeak.ai/agent/sse, which is what the card’s transport.endpoint points to.

Answers cite their sources

Every response carries the canonical salespeak.ai URLs it drew from. This matters more than it sounds. If agents query endpoints instead of reading pages, attribution has to travel with the answer, or the open web quietly loses its citation trail. Returning source URLs is the minimum a well-behaved endpoint owes the site it speaks for.

What the claim actually is

Publishing a card asserts one narrow, checkable thing: that this domain serves a valid card at the canonical path, naming an endpoint on this same domain, and that the endpoint connects, advertises at least one capability, and answers a minimal read-only probe.

It asserts nothing about whether the answers are accurate, complete, or honest. A door exists and it opens. That is the whole claim, and the narrowness is deliberate: a claim that cannot be mechanically falsified is a trust seal, and trust seals rot.

The same-domain part is load-bearing. Our endpoint runs on salespeak.ai/agent/, not on a vendor’s hostname, so anyone can verify the claim without trusting an intermediary. If endpoints resolve to a vendor’s infrastructure, that vendor becomes the registry for everyone else’s capability, and the claim stops being independently checkable.

Publishing your own

Nothing here is Salespeak-specific and none of it requires us. The card format is the MCP SEP-1649 draft, still in review, which we adopted rather than inventing a competing convention: the space already holds llms.txt, /.well-known/agents.json, /agents.txt and DNS-based schemes, and a tenth would help nobody.

Three steps:

  1. Stand up an endpoint that answers questions about your content.
  2. Serve it from your own domain. A CDN rewrite is enough; ours is a single rewrite rule.
  3. Publish a card at /.well-known/mcp/server-card.json naming it.

Salespeak sells the first step. The second and third are yours regardless of who you buy from, and we would rather the convention spread than own it.

Questions

What is an agent endpoint?

A URL on a website that an AI agent can query in natural language instead of crawling the site’s pages. The agent sends a question and receives a structured answer with source URLs, rather than fetching a dozen HTML pages and inferring the answer from them.

How does an agent find it?

From a server card at /.well-known/mcp/server-card.json, following the MCP SEP-1649 draft. The card names the endpoint, the tools it exposes, and whether authentication is required. An agent fetches one small JSON file and knows how to talk to the site.

Do I need a Salespeak account to query it?

No. Salespeak’s endpoint is public and unauthenticated. The server card declares authentication.required: false, and anyone can send it a question.

Does this replace the sitemap or llms.txt?

No. A sitemap lists pages for crawlers and llms.txt points a model at the pages worth reading. Both still describe documents to fetch. An agent endpoint answers a question directly, and returns the canonical page URLs its answer came from, so attribution still lands on the site.

Is serving agents a separate experience from humans?

The endpoint is an addition, not a substitution. Every page on salespeak.ai serves the same content to people, search engines, and agents. The endpoint is a second door for callers who would rather ask than read.