How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
M0

M0 Permit API

The Permit API from M0 — 2 operation(s) for permit.

Documentation Provider Profile APIs.io OpenAPI GitHub

M0 Permit API is one of 5 APIs that M0 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Permit. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 27 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 4 base URLs: https://gateway.m0.xyz/v1/orchestration, https://gateway.stage.m0.xyz/v1/orchestration, https://gateway.dev.m0.xyz/v1/orchestration, http://localhost:5600.

2 operations 2 paths 27 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://gateway.m0.xyz/v1/orchestration
Authentication
API Key
Resource Areas
1

Authentication & Security 1

M0 Permit API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth).

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Permit 2
POST
/permit/quote
Get quotes for the gasless-approval (EIP-2612 permit) flow. Like /quote, but every returned quote's approvals are satisfied by signing an off-chain EIP-2612 permit instead of broadcasting a separate…
permit_permitQuote body → 200400404500
POST
/permit/build
Exchange signed permit recipes for executable transaction payloads. Echo back the PermitRecipes from /permit/quote, each paired with the user's EIP-2612 signature over its typedData. Returns one Payl…
permit_permitBuild body → 200400410422500

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are PermitRecipe (10 properties), LimitOrderPermitOp (10 properties), PermitQuote (8 properties), AmmSwapPermitOp (7 properties). Each schema is shown below with its type and property counts.

Chain
string
SwapPermitOp
object
M Swap Facility swapWithPermit.
6 properties 4 required
PermitIssues
object
Soft warnings; their presence does not fail the request.
1 property
SvmPayload
object
2 properties 2 required
ProvidersParams
object
2 properties
BalanceIssue
object
3 properties 3 required
Payload
object
4 properties 2 required
EvmPayload
object
5 properties 5 required
Eip2612Message
object
5 properties 5 required
Route
object
2 properties 2 required
Eip712Domain
object
4 properties 4 required
ErrorBody
object
Standard error response body. Every error response from this API returns this shape.
3 properties 2 required
TransactionPayload
PayloadSolver
object
The solver behind a limit-order leg. exclusive means the leg is bound to this solver on-chain (it becomes the order's designatedSolver); when false, the quote…
4 properties 2 required
SignedPermitRecipe
object
2 properties 2 required
LimitOrderPermitOp
object
OrderBook openOrderWithPermit.
10 properties 10 required
PermitQuoteResponse
object
3 properties 2 required
AmmSwapPermitOp
object
Uniswap V3 multicall([selfPermit, exactInputSingle]). Signature split to v,r,s.
7 properties 7 required
PermitRecipe
object
Everything needed to sign one leg's permit and produce its executable transaction — either by POSTing to /permit/build or by encoding the WithPermit call local…
10 properties 9 required
Providers
string
PermitOperation
Provider-specific static args for the WithPermit call, discriminated so the build step (or a self-encoding client) knows exactly what to build.
PermitBuildResponse
object
3 properties 2 required
SwapMethod
string
Eip2612TypedData
object
Directly signable EIP-712 payload. types/primaryType are the standard EIP-2612 Permit definition and are omitted; clients use the canonical set.
2 properties 2 required
PermitQuote
object
A quote whose approvals are satisfied by signing permits, not approve.
8 properties 8 required
AssetAddress
object
2 properties 2 required
ErrorCode
string
Stable machine-readable identifier for an API error. Each value corresponds 1:1 to an error type (and to one responses entry in the OpenAPI spec). Branch on th…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

m0-permit-api-openapi.yml Raw ↑

Other APIs M0 publishes across the network.

M0 Protocol API
AE Profile APIs.io
M0 Order API
AE Profile APIs.io
M0 Quote API
AE Profile APIs.io
M0 Topology API
AE Profile APIs.io
#Permit
← Back to M APIs
API Details
ID
m0:m0-permit-api
Base URL
https://gateway.m0.xyz/v1/orchestration
Docs
https://docs.m0.org/api-reference/introduction
Provider
M0
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=m0-permit-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/m0-permit-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of M0 Permit API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.