11xplay API developers

Markdown for Agents

Request any public page with Accept: text/markdown to receive a clean markdown representation. HTML remains the default for browsers.

curl -H "Accept: text/markdown" https://11xplay.cc

OpenAPI: /.well-known/openapi/markdown

Session API

Cookie-backed /api/session supports GET (probe), POST (login / demo), and DELETE (logout) for the web app.

OpenAPI: /.well-known/openapi/session

Web Bot Auth

Outbound agent requests from 11xplay.cc are signed with HTTP Message Signatures (Web Bot Auth). Public keys live at /.well-known/http-message-signatures-directory.

curl -sS https://11xplay.cc/.well-known/http-message-signatures-directory
curl -sS -X POST https://11xplay.cc/api/web-bot-auth/sign \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://example.com/"}'

WebMCP (browser tools)

Supporting browsers expose in-page tools via navigator.modelContext.registerTool. When modelContext is available, the site loads /webmcp.js and registers guide search, markdown fetch, navigation, and API catalog tools (unregistered with an AbortController on page hide).

DNS for AI Discovery (DNS-AID)

Agents can discover endpoints via DNS HTTPS/SVCB records under _agents.11xplay.cc (signed with DNSSEC):

_index._agents.11xplay.cc. 3600 IN HTTPS 1 11xplay.cc. alpn="h3,h2" port=443
_mcp._agents.11xplay.cc.   3600 IN HTTPS 1 11xplay.cc. alpn="h3,h2" port=443 mandatory="alpn,port"
_a2a._agents.11xplay.cc.   3600 IN HTTPS 1 11xplay.cc. alpn="h3,h2" port=443 mandatory="alpn,port"

Experimental capability URIs use RFC 9460 key65400 until DNS-AID parameter names are registered. Publish with scripts/publish-dns-aid.sh.