ECP Context Servers
Protocol Docs

Hosted ECP Context Servers

Instead of hosting your own AgentWelcome.md and redeploying on every change, a Hosted ECP Context Server gives you a single URL to drop into your site configuration, with support for on-demand updates, live data, API integrations, and more.

What This Is

When an agent hits your canonical URL, ECP routes it to a context server that returns structured, current information about your site. Your products, services, status, API surface. Browsers continue to get your existing HTML. Same URL, two audiences, served correctly.

A context server can be as simple as an AgentWelcome.md file you write once and update in a browser, or as dynamic as a live-updating cache that reflects your actual operational state. The provider you choose determines what is possible.


Servers

AgentFriendly.dev Coming June 2026

Advanced ECP capabilities for your domain, including live APIs, payments, house agents, and custom notifications.

More providers coming Ecosystem

Specialized ECP Context Servers with richer analytics, CMS integrations, team workflows, or vertical-specific context formats are expected to emerge as the ecosystem matures. Providers are encouraged to get in touch.


For Providers

If you're building an ECP-compatible context server, we'd like to know. The criteria are straightforward: your server must deliver a valid non-HTML response to agent callers at the canonical URL, return the correct Vary headers, and be publicly reachable.

Reach out at [email protected] to discuss listing.


ECP.Directory

As agents increasingly discover sites without human-initiated search, the ECP index gives your site a verified presence in that layer. Submit once at ecp.directory. The index is opt-in, free, and queried directly by model providers and agent frameworks.