Skip to main content
POST
Mint a Try-Me Config (scenario + model) with a server-generated token.

Authorizations

Authorization
string
header
required

Supabase JWT token in Authorization: Bearer header

Body

application/json
scenarioId
string
required

dojo_scenarios.id (e.g. 'db-shepherd').

label
string | null

MNE-828: optional operator label (free text) for the operator's own list (e.g. 'WonderCo DB-Shepherd demo'). NOT a credential — the resolve token is server-generated.

Maximum string length: 200
model
object

Frontier model; defaults to {provider:'anthropic', name:'claude'}.

expiresAt
string<date-time> | null
usageLimit
integer
default:1
Required range: x >= 1
briefingManifestRef
string | null
logoUrl
string<uri> | null

MNE-1322: optional brand logo (https URL); the agent minted from this invite carries it as its avatar.

Maximum string length: 2048

Response

Try-Me Config created (with a server-generated token) and a compute key bound server-side. The compute key is NOT returned (MNE-828).

config
object
required
share_line
string
required

MNE-804 — the agent-directive entry one-liner the operator copies and SENDS to the person they're inviting: an invite to spar in the Dojo that tells the agent to CONNECT to the Mnemom MCP and call get_started with the (server-generated) token, or (no MCP) HTTP GET the resolve endpoint and read the RAW JSON, then follow the returned manifest verbatim. Never 'visit', never a password prompt.