Mesh is the first global crypto payments network, connecting hundreds of exchanges, wallets, and financial platforms into a single, unified infrastructure layer so businesses can let users pay, get paid, deposit, and transfer digital assets from any wallet on any chain. The Mesh Connect Integration API lets developers programmatically generate Link tokens for Mesh's hosted connection UX, initiate managed crypto transfers (deposit, payment, onramp, withdrawal), read holdings, balances, and transaction history across connected exchange and self-custody accounts, verify wallet ownership, and receive HMAC-signed transfer-status webhooks. Mesh handles credential validation, MFA, OAuth, and per-integration error handling on the developer's behalf. Formerly Front Finance. SOC 2 Type II certified. Backed by Anthemis and General Catalyst.
Mesh publishes 19 API contracts indexed on the APIs.io network, including Assets API, Balance API, BrokerAccountDetail API, and 16 more. Tagged areas include Company, Cryptocurrency, Payments, Digital Assets, and Financial Services.
The Mesh catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.
Mesh’s developer surface includes documentation, API reference, getting-started guide, engineering blog, authentication, changelog, sandbox, and 25 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Payments regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/mesh/"><img src="https://apis.io/badge/mesh/card.svg" alt="Mesh on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card+8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
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.
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 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.
The recommended approach for account authentication. Front manages multiple authentication flows and handles all authentication steps such as MFA codes and OAuth redirect throug...
Not recommended approach. Using this approach, the API client is responsible for handling multiple authentication flows and supporting future updates and changes.
Mesh's cross-chain bridging engine as a pure API, with no Mesh-hosted UI or SDK. Discover bridged routes, quote a pay-in amount and generate a single-use deposit address that br...
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.
aid: mesh
name: Mesh
description: Mesh is the first global crypto payments network, connecting hundreds of exchanges, wallets, and financial platforms
into a single, unified infrastructure layer so businesses can let users pay, get paid, deposit, and transfer digital assets
from any wallet on any chain. The Mesh Connect Integration API lets developers programmatically generate Link tokens for
Mesh's hosted connection UX, initiate managed crypto transfers (deposit, payment, onramp, withdrawal), read holdings, balances,
and transaction history across connected exchange and self-custody accounts, verify wallet ownership, and receive HMAC-signed
transfer-status webhooks. Mesh handles credential validation, MFA, OAuth, and per-integration error handling on the developer's
behalf. Formerly Front Finance. SOC 2 Type II certified. Backed by Anthemis and General Catalyst.
url: https://raw.githubusercontent.com/api-evangelist/mesh/refs/heads/main/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- security
- sandbox
generated: '2026-11-06'
method: derived
image: https://cdn.prod.website-files.com/656cc624086b77872a31a084/68d8116f8f0a10f661523cea_Favicon_new.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- anthemis
- general-catalyst
x-tier: profiled
x-tier-reason: enriched-from-stub
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- Company
- Cryptocurrency
- Payments
- Digital Assets
- Financial Services
- Wallets
- Exchange
- Transfers
- Stablecoins
- Embedded Finance
- Fintech
- On-Ramp
- Blockchain
tags_raw:
- Company
- Crypto
- Cryptocurrency
- Payments
- Digital Assets
- Financial Services
- Wallets
- Exchanges
- Transfers
- Stablecoins
- Embedded Finance
- Fintech
- On-Ramp
- Blockchain
- Financial-Services
apis:
- aid: mesh:mesh-assets-api
name: Mesh Assets API
description: The Assets API from Mesh — 2 operation(s) for assets.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Assets
properties:
- type: OpenAPI
url: openapi/mesh-assets-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-balance-api
name: Mesh Balance API
description: '### Supported integrations:
```Robinhood```
```ETrade```
```Alpaca```
```WeBull```
```Stash```
```InteractiveBrokers```
```Public```
```Coinbase```
```Kraken```
```CoinbasePro```
```CryptoCom```
```Binance```
```Gemini```
```OkCoin```
```KuCoin```
```Etoro```
```CexIo```
```BinanceInternational```
```Bitstamp```
```GateIo```
```Acorns```
```Okx```
```BitFlyer```
```Coinlist```
```Huobi```
```Bitfinex```
```KrakenDirect```
```Vanguard```
```BinanceInternationalDirect```
```BitfinexDirect```
```Bybit```
```Paxos```
```CoinbasePrime```'
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Balances
tags_raw:
- Balance
properties:
- type: OpenAPI
url: openapi/mesh-balance-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-brokeraccountdetail-api
name: Mesh BrokerAccountDetail API
description: The BrokerAccountDetail API from Mesh — 1 operation(s) for brokeraccountdetail.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- BrokerAccountDetail
properties:
- type: OpenAPI
url: openapi/mesh-brokeraccountdetail-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-managed-account-authentication-api
name: Mesh Managed Account Authentication API
description: The recommended approach for account authentication. Front manages multiple authentication flows and handles
all authentication steps such as MFA codes and OAuth redirect through our web and mobile SDKs.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Managed Account Authentication
properties:
- type: OpenAPI
url: openapi/mesh-managed-account-authentication-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-managed-transfers-api
name: Mesh Managed Transfers API
description: The Managed Transfers API from Mesh — 10 operation(s) for managed transfers.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Managed Transfers
properties:
- type: OpenAPI
url: openapi/mesh-managed-transfers-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-portfolio-api
name: Mesh Portfolio API
description: '### Supported integrations:
```Robinhood```
```ETrade```
```Alpaca```
```WeBull```
```Stash```
```InteractiveBrokers```
```Public```
```Coinbase```
```Kraken```
```CoinbasePro```
```CryptoCom```
```OpenSea```
```Binance```
```Gemini```
```OkCoin```
```KuCoin```
```Etoro```
```CexIo```
```BinanceInternational```
```Bitstamp```
```GateIo```
```Acorns```
```Okx```
```BitFlyer```
```Coinlist```
```Huobi```
```Bitfinex```
```KrakenDirect```
```Vanguard```
```BinanceInternationalDirect```
```BitfinexDirect```
```Bybit```
```Paxos```
```CoinbasePrime```
```DeFiWallet```'
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Portfolio
properties:
- type: OpenAPI
url: openapi/mesh-portfolio-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-self-managed-account-authentication-api
name: Mesh Self Managed Account Authentication API
description: Not recommended approach. Using this approach, the API client is responsible for handling multiple authentication
flows and supporting future updates and changes.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Self Managed Account Authentication
properties:
- type: OpenAPI
url: openapi/mesh-self-managed-account-authentication-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-transactions-api
name: Mesh Transactions API
description: '### Supported integrations:
```Robinhood```
```ETrade```
```Alpaca```
```WeBull```
```Stash```
```InteractiveBrokers```
```Public```
```Coinbase```
```Kraken```
```CoinbasePro```
```CryptoCom```
```Binance```
```Gemini```
```OkCoin```
```KuCoin```
```Etoro```
```CexIo```
```BinanceInternational```
```Bitstamp```
```GateIo```
```Okx```
```BitFlyer```
```Coinlist```
```Huobi```
```Bitfinex```
```KrakenDirect```
```Vanguard```
```BinanceInternationalDirect```
```Bybit```
```CoinbasePrime```
### Integration-specific notes:
#### Binance:
Because of limitations of Binance API, initial loading of transaction history in Binance can take long time
depending on the size of the portfolio.
#### OkCoin:
Getting transactions history from OkCoin is not currently supported.'
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Transaction
tags_raw:
- Transactions
properties:
- type: OpenAPI
url: openapi/mesh-transactions-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-transfers-api
name: Mesh Transfers API
description: "### Supported integrations:\n```Robinhood```\n```Coinbase```\n```Kraken```\n```CoinbasePro```\n```CryptoCom```\n\
```Binance```\n```Gemini```\n```OkCoin```\n```KuCoin```\n```BinanceInternational```\n```Bitstamp```\n```GateIo```\n```Okx```\n\
```Huobi```\n```Bitfinex```\n```KrakenDirect```\n```BinanceInternationalDirect```\n```Bybit```\n```Paxos```\n```CoinbasePrime```\n\
```DeFiWallet```\n\n\n### Integration-specific notes:\n\n\n#### Robinhood:\n\n\nCryptocurrency transfers should be enabled\
\ in Robinhood settings. Transfers are disabled by default, enabling them for end users requires a review from Robinhood.\n\
\nPlease note:\n * `MfaCode` parameter is required to initiate a transaction in Robinhood.\n * The user's security settings\
\ should be configured to use an authenticator application.\n * Robinhood doesn't allow initiation of transactions if\
\ the authenticator application is not configured.\n\n\n#### Coinbase:\n\n\n`MfaCode` parameter should be used to initiate\
\ transactions in Coinbase.\n * If the end user's Coinbase account is configured to use text messages (SMS) for two factor\
\ authentication,\nthe API will return `MfaRequired` status, and a text code will then be sent by Coinbase. The code is\
\ expected to be provided in the subsequent call using the `MfaCode` request field\n * If the account is configured to\
\ use an authenticator application, the API is expecting to get the\ncode in the `MfaCode` request field.\n\n#### Kraken:\n\
\n\nKraken requires the explicit chain name to be provided (e.g. `Dogecoin` or `Ethereum (ERC20)`). The list of possible\
\ chains can be obtained by calling `symbol/details` endpoint.\n\nTo initiate a transaction, a Kraken Address Key name\
\ should be provided in `TargetAddress` field. Target address should be added using Kraken UI, then its name should be\
\ used.\n\n\n#### CoinbasePro:\n * CoinbasePro does not provide multiple chains per a symbol, so default chains are used\
\ for getting\nDeposit addresses.\n\n#### Binance:\n\n\n`Enable Withdrawals` permission should be given to the user's\
\ API key to initiate transfers with Binance Us.\n\nBinance requires adding the IP address to the list of trusted IPs\
\ to be able to create API keys with transfer permission.\n * Please reach out to Front to get the static IP address.\
\ This address should be provided to the\nend user, and the user should be instructed to add it to the list of trusted\
\ IP addresses.\n * By default, the permission to enable withdrawals is turned off. If the end user's API key does\nnot\
\ have the permission, asset transfers will not be available.\n\n#### KuCoin:\n\n\nKuCoin requires adding the IP address\
\ to the list of trusted IPs to be able to create API keys with transfer permission.\n\n`Fee` parameter should be used\
\ to initiate a transaction in KuCoin.\n\nPlease note:\n * Please reach out to Front to get the static IP address. This\
\ address should be provided to the\nend user, and the user should be instructed to add it to the list of trusted IP addresses.\n\
\ * All currencies have their minimum `fee` and `amount` requirements. Please use `symbol/details`\nendpoint to get this\
\ data for a particular symbol.\n * KuCoin requires chain name to be provided for getting deposit address or initiating\
\ a cryptocurrency\ntransfer. Some cryptocurrencies are supported over multiple chains. It's recommended to use `symbol/details`\
\ endpoint to get the list of supported chains and show it to the end user to select a target one.\n\n#### BinanceInternational:\n\
\n\n`Enable Withdrawals` permission should be given to the user's API key to initiate transfers with Binance International.\n\
\nBinance requires adding the IP address to the list of trusted IPs to be able to create API keys with transfer permission.\n\
\ * Please reach out to Front to get the static IP address. This address should be provided to the\nend user, and the\
\ user should be instructed to add it to the list of trusted IP addresses.\n * By default, the permission to enable withdrawals\
\ is turned off. If the end user's API key does\nnot have the permission, asset transfers will not be available.\n\n####\
\ GateIo:\n\n\nGate.io requires adding IP address to the list of trusted IP addresses to be able to initiate a cryptocurrency\
\ transfers.\n\nWithdrawal address should be already verified or added on the Gate.io UI (in mobile application or on\
\ the web site).\n * Please reach out to Front to get the static IP address for withdrawals. This address should be\n\
provided to the end user, and the user should be instructed to add it to the list of trusted IP addresses.\n * Only verified\
\ withdrawal blockchain addresses are allowed for withdrawal with Gate.io API.\n * Gate.io requires chain name to be provided\
\ for getting deposit address or initiating a cryptocurrency\ntransfer. Some cryptocurrencies are supported over multiple\
\ chains. It's recommended to use `symbol/details` endpoint to get the list of supported chains and show it to the end\
\ user to select a target one.\n\n#### Huobi:\n\n\nWarning: Huobi does not refund executed deposits that are below the\
\ `Minimum Deposit Amount`\n * Please check the MinimumDepositAmount in Get Deposit Address response in order to avoid\
\ making\na deposit below the minimum amount\n * Huobi does not allow withdrawals to addresses that are not white-listed,\
\ please add the address\nthat you would like to withdraw to the white list of addresses through the UI so that a withrawal\
\ can be processed\n\n#### Bitfinex:\n * The hash of transfer is not available when making a transfer in Bitfinex. To\
\ get the hash please\nre-query the transfer using the transaction id.\n * Bitfinex does not separate sub-accounts when\
\ returning the list of transfers.Therefore the same\nlist of transfers is returned for all Bitfinex sub-accounts.\n\n\
#### KrakenDirect:\n\n\nKraken requires the explicit chain name to be provided (e.g. `Dogecoin` or `Ethereum (ERC20)`).\
\ The list of possible chains can be obtained by calling `symbol/details` endpoint.\n\nTo initiate a transaction, a Kraken\
\ Address Key name should be provided in `TargetAddress` field. Target address should be added using Kraken UI, then its\
\ name should be used."
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Transfers
properties:
- type: OpenAPI
url: openapi/mesh-transfers-api-openapi.yml
- type: x-sandbox-baseURL
url: https://sandbox-integration-api.meshconnect.com
- aid: mesh:mesh-blockchainquery-api
name: Mesh Blockchain Query API
description: The BlockchainQuery API from Mesh — 4 operation(s) for blockchainquery.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- BlockchainQuery
properties:
- type: OpenAPI
url: openapi/mesh-blockchainquery-api-openapi.yml
- aid: mesh:mesh-cataloggassponsorship-api
name: Mesh Catalog Gas Sponsorship API
description: The CatalogGasSponsorship API from Mesh — 3 operation(s) for cataloggassponsorship.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- CatalogGasSponsorship
properties:
- type: OpenAPI
url: openapi/mesh-cataloggassponsorship-api-openapi.yml
- aid: mesh:mesh-catalogsubscription-api
name: Mesh Catalog Subscription API
description: The CatalogSubscription API from Mesh — 5 operation(s) for catalogsubscription.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- CatalogSubscription
properties:
- type: OpenAPI
url: openapi/mesh-catalogsubscription-api-openapi.yml
- aid: mesh:mesh-headless-bridging-api
name: Mesh Headless Bridging API
description: Mesh's cross-chain bridging engine as a pure API, with no Mesh-hosted UI or SDK. Discover bridged routes, quote
a pay-in amount and generate a single-use deposit address that bridges funds to the destination the user selected. Enabled
per client; see https://docs.meshconnect.com/resources/headless-bridging.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Headless Bridging
properties:
- type: OpenAPI
url: openapi/mesh-headless-bridging-api-openapi.yml
- aid: mesh:mesh-integrations-account-information-api
name: Mesh Integrations account information API
description: The Integrations account information API from Mesh — 1 operation(s) for integrations account information.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Integrations account information
properties:
- type: OpenAPI
url: openapi/mesh-integrations-account-information-api-openapi.yml
- aid: mesh:mesh-rampkyc-api
name: Mesh Ramp Kyc API
description: The RampKyc API from Mesh — 1 operation(s) for rampkyc.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- RampKyc
properties:
- type: OpenAPI
url: openapi/mesh-rampkyc-api-openapi.yml
- aid: mesh:mesh-ramppayment-api
name: Mesh Ramp Payment API
description: The RampPayment API from Mesh — 3 operation(s) for ramppayment.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- RampPayment
properties:
- type: OpenAPI
url: openapi/mesh-ramppayment-api-openapi.yml
- aid: mesh:mesh-rampsession-api
name: Mesh Ramp Session API
description: The RampSession API from Mesh — 2 operation(s) for rampsession.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- RampSession
properties:
- type: OpenAPI
url: openapi/mesh-rampsession-api-openapi.yml
- aid: mesh:mesh-tokennetworkpairs-api
name: Mesh Token Network Pairs API
description: The TokenNetworkPairs API from Mesh — 1 operation(s) for tokennetworkpairs.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- TokenNetworkPairs
properties:
- type: OpenAPI
url: openapi/mesh-tokennetworkpairs-api-openapi.yml
- aid: mesh:mesh-wallets-api
name: Mesh Wallets API
description: The Wallets API from Mesh — 2 operation(s) for wallets.
humanURL: https://docs.meshconnect.com/overview
baseURL: https://integration-api.meshconnect.com
tags:
- Wallets
properties:
- type: OpenAPI
url: openapi/mesh-wallets-api-openapi.yml
common:
- type: Website
url: https://meshconnect.com
- type: CapabilityMap
url: capabilities/mesh-capability-edges.yml
name: Mesh Business Capability Map
- type: Overlay
url: overlays/mesh-integration-api-overlay.yaml
- type: DeveloperPortal
url: https://docs.meshconnect.com/overview
- type: Documentation
url: https://docs.meshconnect.com/overview
- type: APIReference
url: https://docs.meshconnect.com/api-reference/managed-transfers/get-integrations
- type: GettingStarted
url: https://docs.meshconnect.com/build/15min-quickstart
- type: Login
url: https://dashboard.meshconnect.com/login
- type: Blog
url: https://www.meshpay.com/blog
- type: GitHubOrganization
url: https://github.com/FrontFin
- type: StatusPage
url: https://status.meshconnect.com/
- type: TermsOfService
url: https://www.meshpay.com/terms-of-service
- type: PrivacyPolicy
url: https://www.meshpay.com/privacy-policy
- type: Compliance
url: https://www.meshpay.com/security
- type: TrustCenter
url: https://www.meshpay.com/security
- type: Authentication
url: authentication/mesh-authentication.yml
- type: Conventions
url: conventions/mesh-conventions.yml
- type: ErrorCatalog
url: errors/mesh-problem-types.yml
- type: Lifecycle
url: lifecycle/mesh-lifecycle.yml
- type: ChangeLog
url: changelog/mesh-changelog.yml
- type: Conformance
url: conformance/mesh-conformance.yml
- type: DataModel
url: data-model/mesh-data-model.yml
- type: Sandbox
url: sandbox/mesh-sandbox.yml
- type: Webhooks
url: asyncapi/mesh-transfers-webhooks.yml
- type: X-MCPServerCandidate
url: mcp/mesh-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Packages
url: packages/mesh-packages.yml
- type: SDKs
url: packages/mesh-packages.yml
- type: Components
url: components/mesh-components.yml
- type: LLMsTxt
url: llms/mesh-llms.txt
- type: WellKnown
url: well-known/mesh-well-known.yml
- type: DomainSecurity
url: security/mesh-domain-security.yml
- type: AgentSkill
url: skills/_index.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
x-enrichment:
date: '2026-07-20'
status: enriched
artifacts_added: 22
pass: local-v1
Mesh API — frequently asked questions
Does Mesh have an API?
Yes. APIs.io lists 19 APIs from Mesh, including Mesh Assets API, Mesh Balance API and Mesh BrokerAccountDetail API, and 16 more.
Is there an OpenAPI specification for the Mesh API?
Yes. APIs.io indexes 19 OpenAPI specifications for Mesh, each linked for download from this page.
How do I authenticate with the Mesh API?
Mesh uses bearer-token authentication (apiKey · 2 schemes). The details are profiled on APIs.io as Mesh Authentication.
Is the Mesh API ready for AI agents?
Mesh has a Kin Score of 54.1 out of 100 (developing) and an Agent Readiness score of 33.4 (agent-ready), scored by API Evangelist on 2026-11-06.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: