Interfaces agents can trust

MantrixFlow publishes an OpenAPI 3.1 description for the read-only discovery endpoints on this origin, an llms.txt guide, a complete agent context file, Markdown representations of public pages, robots.txt, sitemap.xml, structured JSON API errors, and Schema.org JSON-LD. These interfaces help software understand what MantrixFlow is, locate authoritative resources, and avoid assuming capabilities that are not available.

Request a public page with Accept: text/markdown to receive clean Markdown from the same URL, or use the explicit .md sibling. Responses include Vary: Accept so caches keep HTML and Markdown separate. The discovery API requires no authentication and has no mutating operations. Its OpenAPI operations use stable identifiers, descriptions, schemas, and explicit response types suitable for function-calling tools.

The MantrixFlow web application communicates with a protected product API using authenticated workspace sessions and server-enforced organization roles. That application contract is not currently offered as a general public developer API or API-key program. Connector OAuth flows authorize specific third-party systems; they do not make MantrixFlow an OAuth authorization server for external agents.

No public MCP server, downloadable CLI, public agent sandbox, dynamic OAuth client registration endpoint, or public pipeline-control scope catalog is currently published. The capability manifest reports each of those boundaries directly. Contact support if your integration requires a capability outside the documented discovery surface, and use the product documentation for supported implementation workflows.