Mesh

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 9 APIs on the APIs.io network, including Assets API, Balance API, BrokerAccountDetail API, and 6 more. Tagged areas include Company, Crypto, Cryptocurrency, Payments, and Digital Assets.

The Mesh catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Mesh’s developer surface includes documentation, API reference, getting-started guide, engineering blog, authentication, changelog, sandbox, and 22 more developer resources.

🌐 Visit website 📡 Source on GitHub
58.1/100 developing ▬ flat Agent 61/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
9 APIs 1 MCP Servers
CompanyCryptoCryptocurrencyPaymentsDigital AssetsFinancial ServicesWalletsExchangesTransfersStablecoinsEmbedded FinanceFintechOn-RampBlockchain

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 58.1/100 · developing
Contract Quality 15.8 / 25
Developer Ergonomics 15.2 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 5.8 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 61/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/mesh: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

Mesh Assets API

The Assets API from Mesh — 2 operation(s) for assets.

Mesh Balance API

### Supported integrations: ```Robinhood``` ```ETrade``` ```Alpaca``` ```WeBull``` ```Stash``` ```InteractiveBrokers``` ```Public``` ```Coinbase``` ```Kraken``` ```CoinbasePro``...

Mesh BrokerAccountDetail API

The BrokerAccountDetail API from Mesh — 1 operation(s) for brokeraccountdetail.

Mesh Managed Account Authentication API

The recommended approach for account authentication. Front manages multiple authentication flows and handles all authentication steps such as MFA codes and OAuth redirect throug...

Mesh Managed Transfers API

The Managed Transfers API from Mesh — 10 operation(s) for managed transfers.

Mesh Portfolio API

### Supported integrations: ```Robinhood``` ```ETrade``` ```Alpaca``` ```WeBull``` ```Stash``` ```InteractiveBrokers``` ```Public``` ```Coinbase``` ```Kraken``` ```CoinbasePro``...

Mesh Self Managed Account Authentication API

Not recommended approach. Using this approach, the API client is responsible for handling multiple authentication flows and supporting future updates and changes.

Mesh Transactions API

### Supported integrations: ```Robinhood``` ```ETrade``` ```Alpaca``` ```WeBull``` ```Stash``` ```InteractiveBrokers``` ```Public``` ```Coinbase``` ```Kraken``` ```CoinbasePro``...

Mesh Transfers API

### Supported integrations: ```Robinhood``` ```Coinbase``` ```Kraken``` ```CoinbasePro``` ```CryptoCom``` ```Binance``` ```Gemini``` ```OkCoin``` ```KuCoin``` ```BinanceInternat...

Scroll for all 9

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

mesh-mcp.yml

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Mesh Transfers Webhooks

ASYNCAPI

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Mesh Authentication

apiKey · 2 schemes

SECURITY

Mesh Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Mesh Trust Center

SOC 2 Type II

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 Login
Login
 Sandbox
Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 WellKnown
WellKnown
 AgentSkill
AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conformance
Conformance
 DataModel
DataModel
 Webhooks
Webhooks
 Components
Components

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs

Access & Security 4

Authentication, authorization, and security posture

Compliance
Compliance
 TrustCenter
TrustCenter
 Authentication
Authentication
 DomainSecurity
DomainSecurity

Operate 2

Status, limits, changes, and where to get help

StatusPage
StatusPage
 ChangeLog
ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 1

The organization behind the API

Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
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
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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.20'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Crypto
- Cryptocurrency
- Payments
- Digital Assets
- Financial Services
- Wallets
- Exchanges
- Transfers
- Stablecoins
- Embedded Finance
- Fintech
- On-Ramp
- Blockchain
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:
  - 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:
  - 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
common:
- 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: MCPServer
  url: mcp/mesh-mcp.yml
- 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