Skip to main content

​
Base URL

MESO runs on two backends. Both expose the same function paths.
The first-party application currently deploys against Supabase Cloud. The self-hosted stack on GKE serves the same contract.

​
Shape of every call

Almost all endpoints are POST, take JSON, return JSON, and share the response envelope. Two exceptions: /whisper-transcribe takes multipart/form-data, and several capability handlers answer a GET /health sub-path.

​
Endpoint names changed on 2026-08-18

The -bedrock, generate- and -unified suffixes were dropped when the capability handlers moved to the Vertex agents. The endpoints now carry the plain capability names used throughout this reference.There are no compatibility aliases. The old deployed instances were removed, so a client built against a pre-August 2026 endpoint list will get a 404, not a redirect. Client and functions must ship together.
These names were deliberately left alone, because none of them carried a provider or migration word: account-lookup, admin-invite-user, ai-actions, chat, ingest-teacher-document, recommend-as, recommend-lo, redeem-signup-code, retrieval-proxy, unit-hero-image, validate-signup-token, whisper-transcribe.
There is no /v1 path prefix and no version header. The endpoint name is the contract, which is why a rename is a breaking change rather than a deprecation.

​
Endpoint index

Unit planning

Lesson planning

Rubric

Assessment

Resource

Slides

Hero image

Chat

AI actions

Transcription

Recommend outcomes

Recommend assessments

Document ingestion

MESO does not currently offer a public, self-serve API programme. These endpoints back the first-party application and are documented here for integration partners and publishers working with us directly. Contact contact@mesolab.ai to discuss access.