APIs

Diafunc exposes a set of versioned public REST APIs, each covering a distinct domain of the platform. All endpoints are served under a shared /api/v1/ path. Most APIs authenticate via API tokens scoped to a project, while the Admin API is session-authenticated and the Status endpoints are public — each stated on its own page.

Every API is documented via an OpenAPI specification and comes with an interactive Swagger UI that can be used to browse the endpoints and try them out directly from the browser.

Shared model for authentication, scopes, and error responses:

Manages users, projects, subscriptions, and API tokens. Use this API to provision accounts, organize access, and issue credentials for programmatic access to the platform.

Drives Diafunc's automatic-analysis workflow programmatically. Create an analysis recipe, upload a dataset, set targets and budget, queue runs, stream progress, and schedule recurring triggers — without provisioning any project, table, or notebook by hand.

Executes functions, manages triggers, and exposes evaluation outputs and logs. Use this API to run code on the platform and to inspect the results of previous evaluations.

Triggers rebuilds of the search index for a single project or for the entire platform. Use this API to keep search results in sync after large-scale content changes.

A Model Context Protocol server that exposes project, entity, function, table, notebook, and evaluation operations as MCP tools, resources, and prompts. Use it to connect Claude Desktop, IDE assistants, or custom agents directly to a Diafunc project. It is the supported surface for language-driven tooling; the platform's internal Language service, which also powers the conversational assistant, is not a public API.

Persists and retrieves project data: entities, links, events, tables, notebooks, branches, forks, and import/export operations. This is the primary API for reading and writing project content.

Publishes the current operational status of the Diafunc platform: a high-level summary, per-component health, ongoing and historical incidents, and uptime statistics. The status endpoints are unauthenticated and safe to poll from external monitoring.