Use the public conversation API. Leyline does not claim a native MCP server for this harness.
POST https://leyline.ahensya.com/api/v1/conversations
POST https://leyline.ahensya.com/api/v1/conversations/{id}/messages
Authorization: Bearer {token}
Content-Type: application/json
{"message":"compare browser automation options","requestId":"{uuid}","mode":"research"}
[ Endpoints ]
GET https://leyline.ahensya.com/api/v1/resolve?q=web+crawl
GET https://leyline.ahensya.com/api/v1/components
GET https://leyline.ahensya.com/api/v1/components?sort=rising
GET https://leyline.ahensya.com/api/v1/components?sort=in-demand
GET https://leyline.ahensya.com/api/v1/components?score=70
GET https://leyline.ahensya.com/api/v1/components/{slug}
GET https://leyline.ahensya.com/api/v1/frequency
GET https://leyline.ahensya.com/api/v1/frequency?slug={slug}
GET https://leyline.ahensya.com/api/v1/ranks
GET https://leyline.ahensya.com/api/v1/shares/{id}
POST https://leyline.ahensya.com/api/v1/parse
GET https://leyline.ahensya.com/api/v1/pulse
GET https://leyline.ahensya.com/api/v1/pulse/digest.md
POST https://leyline.ahensya.com/api/v1/sorcery
POST https://leyline.ahensya.com/api/v1/conversations
GET https://leyline.ahensya.com/api/v1/conversations/{id}
POST https://leyline.ahensya.com/api/v1/conversations/{id}/messages
POST https://leyline.ahensya.com/api/v1/compositions
GET https://leyline.ahensya.com/api/v1/compositions/{id}
POST https://leyline.ahensya.com/api/v1/compositions/{id}/recheck
POST https://leyline.ahensya.com/mcp
GET https://leyline.ahensya.com/llms.txt
Save and re-check compositions over HTTP. Those writes have no MCP tool. A read-only MCP server is POST https://leyline.ahensya.com/mcp. There is no WebMCP server. The legacy scour, decide, and sorcery endpoints remain published contracts. New agent work should use one conversation.