Skip to content
AI News HubLIVE
More
Summary only

Show HN: Endpoint Context Protocol – Browsers get HTML, AI agents get Markdown

The Endpoint Context Protocol (ECP) leverages HTTP content negotiation to serve different representations from the same URL: browsers get HTML, AI agents get semantic Markdown. No new infrastructure required; just two simple files. It enables live context updates, API discovery, and can be extended with hosted ECP context servers.

SourceHacker News AIAuthor: devconcierge
Show HN: Endpoint Context Protocol – Browsers get HTML, AI agents get Markdown
Report an error

The correction channel is not available yet. You can copy the article reference below for later.

Correction instructions

Summary only

Under the source content permission, this page provides an editorial summary, key points, and a link to the original article.

Key points and analysis

Article intelligence

EngineersAdvanced

Key points

  • ECP uses existing HTTP content negotiation headers (Sec-Fetch-Dest, Accept) to distinguish browsers from automated agents.
  • Implementation is simple: create ecp.json in the site root and configure request handling to serve Markdown to agents.
  • Supports URL-first discovery, live operational context, and agent indexing via the ECP directory.

Highlights and analysis are generated automatically and may contain errors. Check the original source.

More recent stories on this topic · Agents