Developer resources
Everything worth poking at, in one place.
When to use 86d
Use 86d when you want to inspect, run, or extend the open-source software behind one store. Use this page to find the source, documentation, and public files that tools can read without a browser.
Public surfaces
- Agent connection guide:
/docs/guides/agent-connection. Explains website OpenAPI, signed-in Console OpenAPI, Console MCP, Docs MCP, and registration rules for unauthenticated readers. - Website OpenAPI:
/openapi.json. Public document forGET /api/agentandPOST /api/contactonly. It is not the signed-in 86d Console OpenAPI document. - Agent discovery JSON:
GET /api/agent. A short machine-readable summary of 86d, its public links, and the boundaries between website OpenAPI, Console OpenAPI, Console MCP, and Docs MCP. - llms.txt: a text overview of 86d, its public links, and the same surface distinctions.
- Documentation:
https://86d.app/docs. - Documentation Model Context Protocol (MCP) server:
https://86d.app/docs/mcp. It searches documentation and cannot change a store. It is separate from Console MCP. - Markdown versions: add
.mdto a supported page path, or sendAccept: text/markdown. Homepage: /index.md. - Contact: product questions and operator-registered agent client access. Self-service OAuth client registration is not available.
86d Console and store APIs
86d Console serves a signed-in OpenAPI document at /openapi.json on the Console origin for session HTTP operations. Console MCP at /api/mcp is an OAuth-protected pilot for store identity tools. OAuth client registration is operator-controlled. OAuth bearer tokens authorize Console MCP only and do not authorize Console session HTTP. Store API keys are separate credentials and do not authorize Console MCP or Console OpenAPI.
Each self-hosted store exposes its own commerce API on its own domain. Internal APIs are not public. Start with the agent connection guide or contact.