M0
M0 is modular stablecoin infrastructure that lets organizations launch and manage their own custom stablecoins instead of adopting a one-size-fits-all token. Its stack has three independent layers: an application layer for token behavior, rewards, and access controls; a distribution layer for cross-chain liquidity routing; and an issuance layer where teams pick an issuer or become their own. M0 is backed by U.S. Treasury Bill collateral held in special purpose vehicles, and exposes an Orchestration REST API (quotes, cross-chain orders, EIP-2612 permits) plus a Protocol GraphQL API for on-chain data, along with an MCP server and agent skills for AI builders. Used by MetaMask, PayPal, Anchorage, MoonPay, and others.
M0 publishes 5 API contracts indexed on the APIs.io network, including Order API, Permit API, Quote API, and 2 more. Tagged areas include Company, Cryptocurrency, Stablecoins, Payments, and Blockchain.
The M0 catalog on APIs.io includes 1 Spectral governance ruleset.
M0’s developer surface includes engineering blog, sandbox, documentation, API reference, getting-started guide, signup flow, support, and 20 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Stablecoins and Tokenization (stablecoin issuers, tokenized assets) | covered | 17.2 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 3
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
M0 Protocol API
GraphQL API to query on-chain M0 protocol data — token supplies, holder balances, yields, and configuration.
M0 Order API
The Order API from M0 — 3 operation(s) for order.
M0 Permit API
The Permit API from M0 — 2 operation(s) for permit.
M0 Quote API
The Quote API from M0 — 2 operation(s) for quote.
M0 Topology API
The Topology API from M0 — 2 operation(s) for topology.
Open Collections 4
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
liquidity-api Order API
OPEN COLLECTIONliquidity-api Order Permit API
OPEN COLLECTIONliquidity-api Order Quote API
OPEN COLLECTIONliquidity-api Order Topology API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
M0 MCP Server
M0's official hosted, remote MCP server. Exposes the M0 protocol and platform documentation, glossary, and deployed contract addresses to AI assistants over the Model Context Pr...
MCP SERVERAgent Skills 1
Packaged agent skills for driving this provider's APIs from an AI assistant.
Spectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
M0 API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
M0 Orchestration Overlay
DERIVEDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
M0 API — frequently asked questions
Does M0 have an API?
Yes. APIs.io lists 5 APIs from M0, including M0 Protocol API, M0 Order API and M0 Permit API, and 2 more.
Is there an OpenAPI specification for the M0 API?
Yes. APIs.io indexes 4 OpenAPI specifications for M0, each linked for download from this page.
How do I authenticate with the M0 API?
M0 uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as M0 Authentication.
Does M0 have an MCP server?
Yes. APIs.io lists 1 MCP server for M0: M0's official hosted, remote MCP server. Exposes the M0 protocol and platform documentation, glossary, and deployed contract addresses to AI assistants over the Model Context Protocol (streamable HTTP
Is the M0 API ready for AI agents?
M0 has a Kin Score of 42.9 out of 100 (developing) and an Agent Readiness score of 32.1 (agent-ready), scored by API Evangelist on 2026-11-06.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.