Developers
Minoa API, MCP server, and developer resources
Everything an engineer or an agent needs to work with Minoa: a public read-only content API with an OpenAPI description, the authenticated product API, the Minoa MCP server, and Markdown versions of every page.
Content API
Read Minoa's public content as JSON
The content API needs no key and no account. It serves the same articles, glossary, pricing, and company details this site renders, so an agent answering a question about Minoa can cite a structured source instead of scraping a page. Every response is JSON, every failure is a JSON envelope with a code, a message, and a resolution, and the whole surface is described at /openapi.json (also served at /.well-known/openapi.json).
GET /api/v1
Index of every endpoint, with links to the OpenAPI description.
GET /api/v1/company
Company profile, registered address, and contact channels.
GET /api/v1/pricing
Published plans, the flat annual platform fee, and the pricing FAQ.
GET /api/v1/posts
Published articles, newest first. Filter with category, limit, and offset.
GET /api/v1/posts/{slug}
One article, including its full Markdown body.
GET /api/v1/glossary
Every value selling glossary term, alphabetically.
GET /api/v1/glossary/{slug}
One glossary term, including its Markdown definition.
Responses are cached and CORS-open. Please keep automated reads to a fair volume; if you need bulk access, write to hello@minoa.io.
Build
Minoa product API
The product API covers business cases, value frameworks, global inputs, and analytics inside your workspace. Authentication, endpoints, and worked recipes are documented in the product docs.
docs.minoa.ioMinoa MCP server
A remote Model Context Protocol server over Streamable HTTP at mcp.minoa.io, published as io.minoa/minoa. It authenticates with OAuth, so agents read and write only the value data the signed-in user can already see. The manifest is at /server.json, and Claude, Glean, Dust, Langdock, and n8n all have a documented setup path.
How the MCP server worksMarkdown for agents
Every public page on this site returns Markdown when you send the header Accept: text/markdown, or when you prefix the path with /api/md. No HTML parsing, no hydration payload, same URL structure.
Try /api/md/resourcesllms.txt
A single plain-text map of the site for language models: what Minoa is, every key page, the comparison hub, the glossary, and the research reports, each with a one-line description.
Read llms.txtAccess
Public content API
No authentication. Call it now, from anywhere, and read the OpenAPI description for the exact response shapes.
Product API and MCP
Generate a key from your Minoa workspace settings, or connect the MCP server and approve the OAuth prompt. Both scope access to your own workspace.
No workspace yet
Book a demo and we will set one up. Enterprise plans include bring-your-own MCP and warehouse connectors.
Questions about the API
Endpoints, access, rate limits, and how agents read minoa.io as structured content.
Does Minoa have a public API?
Yes. The public content API lives under minoa.io/api/v1 with an OpenAPI description at minoa.io/openapi.json. Product API documentation for your Minoa workspace, covering authentication and integrations, is at docs.minoa.io.
Can agents read minoa.io as structured content?
Yes. Every content route has a Markdown representation, the content API returns blog posts, guides and glossary terms as JSON, and llms.txt gives an agent a single indexed summary of the site.
How do we get API access?
The public content API needs no key. Product API access to your own workspace data is issued per workspace; contact us and we will provision credentials against your plan.
What is the Value Realization Tracker API for?
Pushing actual outcome data back into Minoa so delivered value can be measured against the value promised in the original business case. Teams feed it from a warehouse connector, Snowflake or BigQuery, or directly from product telemetry.
Is there rate limiting?
The public content API is rate limited per IP at a level intended for agents and integrations rather than bulk scraping. Product API limits are set per workspace and documented at docs.minoa.io.
Still have questions? Talk to our team
Put value data where your agents already work
Connect the Minoa MCP server, or read the public content API. Both take minutes.