Controlled developer access
Developer Gateway

Build controlled AI applications with m-pathy.

Developer access starts with a guided schooling path. You receive SDK orientation, API command context, local workspace structure and the staging migration path before anything reaches the platform economy.

schoolSDKcommandAPIruntimeSTG
SDK
Extension contracts and local structure
API
Command based model access
STG
Staging execution before release
Proof
Traceable platform actions
Developer Schooling

Start your Developer Schooling now.

Begin the guided developer path on Staging. It prepares SDK usage, API commands, local workspace structure and the controlled extension route.

Note: the Developer Schooling flow currently runs entirely in English.

Start Developer Schooling
What you can build

Controlled applications

Create structured AI applications with bounded inputs, deterministic outputs and clear execution artifacts.

What you can build

Proof-ready extensions

Connect model calls, local runtime steps and user-facing reports to a proof path instead of a loose chat result.

What you can build

Platform paths

Prepare extensions for staging review and later economic participation when they are released into m-pathy.

Developer Schooling

The gateway is guided, not open-ended.

Developer Schooling is the controlled entry into SDK usage, API commands, public key binding, API key provisioning and staging migration. It prevents unclear API usage before the developer context is ready.

01

Provision access

A default developer workspace, public key and API key can be provisioned after login on staging.

02

Complete schooling

The schooling state marks when the developer path has been completed with a proof run.

03

Move through staging

Extensions are tested in the staging execution space before they become part of the public platform path.

Runtime boundary

Developer Schooling runs on Staging.

Main presents the platform and connects future economic ownership. Staging is the developer execution space for schooling, SDK tests, dev tokens and extension migration. Main tokens and dev tokens remain separated.

Identity bridge

Use the same email on Main and Staging.

The same email links the future developer identity across separated account spaces. It supports attribution and future earnings visibility without merging account balances or runtime contexts.

Developer Schooling

Start your Developer Schooling now.

Begin the guided developer path on Staging. It prepares SDK usage, API commands, local workspace structure and the controlled extension route.

Note: the Developer Schooling flow currently runs entirely in English.

Start Developer Schooling
Early access

Request the developer path.

If you do not have dev tokens yet, leave your email. This lightweight gateway will become the early access request path for SDK, API commands and staging migration.

Choose your entry

Developer Schooling currently runs in English.

Use the same email on Main and Staging so your developer identity can be linked later.