Endpoint Context Protocol – Browsers get HTML, AI agents get Markdown

Name: Endpoint Context Protocol – Browsers get HTML, AI agents get Markdown
Availability: InStock
Author: devconcierge

by devconcierge·May 13, 2026·3 points·0 comments

Visit Project View on HN

AI Analysis

●●SolidBig BrainSolve My Problem

Leverages 1999 HTTP headers to solve the AI scraping problem elegantly.

Strengths

•Uses standard Sec-Fetch-Dest headers instead of inventing new protocols.
•No infrastructure changes required; works with existing hosting providers.
•Solves the 'scraping vs serving' dilemma with a single canonical URL.

Weaknesses

•Requires server-side logic to inspect headers, not just static hosting.
•Adoption depends on AI agents respecting standard HTTP headers.

Similar Projects

Developer Tools●●●Banger

Mkdnsite – Markdown-native web server for humans (HTML) and agents (md)

Content negotiation serves raw Markdown to agents, skipping the reconversion tax entirely.

Big BrainSolve My ProblemShip It

nexdrew

602mo ago

Developer Tools●●Solid

AgentProbe – Validate AI agent endpoints across 8 protocols in one URL

Checks eight layers in one go — from plain HTTP reachability to on‑chain ERC‑8004 lookups and x402 payment detection — and even exposes a /mcp POST API so other tools can trigger programmatic validation. The built-in MCP server and agent-lookup features are clever for this niche ecosystem; what I'd want next is clearer detection heuristics, error modes and false-positive handling so teams can trust automated scans in CI.

Niche GemWizardry

Andreas_3d

104mo ago

Developer Tools●●Solid