Public integration reference
Use REST when your product controls the workflow. Use MCP when an AI client should discover and operate Minds as a tool. Both lead to the same durable research infrastructure.
Protocol decision router
Pick the job. The lab returns the shortest supported route and a maintained source to continue from.
Call typed public endpoints from your backend, keep API keys server-side, and store durable run identifiers with your application state.
Runtime source of truth
This page does not maintain a second endpoint catalog. Counts and resource groups are calculated from the production OpenAPI document when you load it.
A durable research loop
Describe the market, customer, or stakeholder population the study must represent.
Create explicit cohorts and reusable research context before asking the first question.
Run panels and research jobs as durable work rather than holding a chat session open.
Poll or resume by run identifier, then bring structured findings into the system making the decision.
Copy a starting point
npx openapi-typescript \
https://api.getminds.ai/api/v1/openapi.json \
--output minds-api.d.tsMinds developer infrastructure