The system behind every model.
The m-pathy API does not return raw output, it returns controlled operations through M13.
The m-pathy API does not return raw output, it returns controlled operations through M13.
A normal model call gives you text, but M13 gives you the system layer around it.
You see:
So you can use AI output inside real workflows, not just read it.
An M13 response is a structured system object with generated content and runtime facts.
The model output shaped by the active M13 operation.
Token usage, cached tokens and billable tokens.
Debit status, debit amount, balance source and balance after the call.
A structured result object that can be stored, rendered or processed.
Server side runtime evidence produced outside the model response.
Run ID, stage ID, operation ID, command and execution metadata.
A traceable reference for later audit and proof.
You do not just receive an answer.
You receive a controlled operation result.
M13 places each API model into a specific Space, so the operation defines what the model is allowed to do in that call.
Use M13 reasoning when complex input needs to be processed into a stable analytical foundation.
M13 places Claude Sonnet 4-6 into a reasoning space for structured analysis, stepwise derivation and robust information processing.
Use M13 challenge when an answer, plan, report or decision should not move forward without a stress test.
M13 places Claude Opus 4-6 into a validation space.
The operation tests assumptions, missing evidence, contradictions, weak boundaries, unsupported inference, risk and drift.
You do not receive a second opinion.
You receive a controlled challenge operation.
Use M13 summary when long content needs to become clear, compact and usable.
M13 places GPT-4.1 mini into a summary space for controlled reduction, ordered output and cost-aware summarization.
Use M13 fast when you need quick classification, first orientation or lightweight processing with low latency.
M13 places Claude Haiku into a fast operation space for simple checks, routing decisions and rapid pre-processing.
Many APIs give you model access, but m-pathy gives you controlled M13 operations with command, rich response and runtime evidence.
This helps you build AI features that are not loose text surfaces.
You can build workflows where model output is structured, billable, traceable and ready for downstream processing.
You start with the developer path, not with a loose API key.
The Build page guides API access, Developer Schooling, SDK workflow and staging. Developer Schooling then opens the M13 Extension SDK workspace for local VS Code development.
Build against M13 when AI should not only generate text, but operate inside a controlled system layer that m-pathy turns into an executable ecosystem.