Mesh Payments

Mesh Payments is a global travel and expense (T&E) and spend management platform for finance teams, combining corporate virtual and physical card issuing, expense management, accounts payable, procurement (ProcurePay), travel booking and accounting automation in a single system. Mesh exposes a RESTful API on api.meshpayments.com for virtual card lifecycle management, merchant and category controls, metadata tagging, authorization and settlement retrieval and real-time balance queries, authenticated with either HMAC-SHA256 request signing or OAuth 2.0 client credentials. It also publishes an OAuth-protected Model Context Protocol (MCP) server at api.meshpayments.com/mcp and a configurable webhooks surface, plus ERP, HRIS and TMC integrations.

Mesh Payments is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Payments, Spend Management, Expense Management, and Corporate Cards.

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

Mesh Payments’ developer surface includes documentation, support, engineering blog, pricing, signup flow, changelog, authentication, and 24 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

47.3/100 developing ▬ flat Agent 45/100 agent ready Front door AI 5/6 prominent Heartbeat 82/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

2 APIs 1 MCP Servers

Company Payments Spend Management Expense Management Corporate Cards Travel Accounts Payable Fintech Card Issuing Accounting Automation

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 47.3/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 5.7 / 17

Access Clarity 10.3 / 17

Operational Transparency 4.1 / 11

Contract Governance 1.9 / 10

Discoverability 6.4 / 9

Regulatory Posture 7.2 / 15

Agent readiness — 45/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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-payments/"><img src="https://apis.io/badge/mesh-payments/card.svg" alt="Mesh Payments 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):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 39.0 — up to +15.3 composite points
Developer Ergonomics scores 33.3 — up to +13.3 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/mesh-payments/apis.yml: open an issue on github.com/api-evangelist/mesh-payments to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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
Procurement and B2B Buying (source-to-pay suites, spend management)	regulated	19.2 (thin)	-	-
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	19.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.

Model Context Protocol (MCP)

measured — observed by APIs.io (verified)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 2

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

Mesh Payments API

RESTful API for the Mesh spend management platform. Documented capabilities include connectivity verification, virtual card lifecycle management (issuance, suspension, cancellat...

Mesh Payments MCP Server

OAuth-protected Model Context Protocol (MCP) server operated by Mesh at api.meshpayments.com/mcp. The endpoint advertises RFC 9728 OAuth 2.0 Protected Resource Metadata at /.wel...

MCP Servers 1

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

Mesh Payments MCP Server

Remote MCP server at api.meshpayments.com over HTTP.

MCP SERVER

Mesh Payments API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Mesh Payments Plans Pricing

0 plans

PLANS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Mesh Payments Finops

FINOPS

Event Specifications 1

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

Mesh Payments Webhooks

ASYNCAPI

Security Posture 4

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

Mesh Payments Authentication

http/oauth2/custom-hmac · 3 schemes

SECURITY

Mesh Payments Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Mesh Payments Vulnerability Disclosure

security.txt · contact published

SECURITY

Mesh Payments Trust Center

SOC 1 Type II, SOC 2 Type II, PCI DSS, GDPR, CCPA, Vendor Security Alliance (VSA)

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Mesh Payments Scopes

1 scope · authorizationCode/clientCredentials/deviceCode

1 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

MCPServer

MCPServer

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

Lifecycle

Conformance

Webhooks

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 7

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Compliance

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

TrustCenter

TrustCenter

Scroll for all 7

Operate 4

Status, limits, changes, and where to get help

Support

HelpCenter

ChangeLog

ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Source (apis.yml)

aid: mesh-payments
name: Mesh Payments
description: Mesh Payments is a global travel and expense (T&E) and spend management platform for finance teams, combining
  corporate virtual and physical card issuing, expense management, accounts payable, procurement (ProcurePay), travel booking
  and accounting automation in a single system. Mesh exposes a RESTful API on api.meshpayments.com for virtual card lifecycle
  management, merchant and category controls, metadata tagging, authorization and settlement retrieval and real-time balance
  queries, authenticated with either HMAC-SHA256 request signing or OAuth 2.0 client credentials. It also publishes an OAuth-protected
  Model Context Protocol (MCP) server at api.meshpayments.com/mcp and a configurable webhooks surface, plus ERP, HRIS and
  TMC integrations.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://meshpayments.com/wp-content/uploads/2026/05/meshpayments.png
url: https://raw.githubusercontent.com/api-evangelist/mesh-payments/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-10-06'
tags:
- Company
- Payments
- Spend Management
- Expense Management
- Corporate Cards
- Travel
- Accounts Payable
- Fintech
- Card Issuing
- Accounting Automation
apis:
- name: Mesh Payments API
  description: RESTful API for the Mesh spend management platform. Documented capabilities include connectivity verification,
    virtual card lifecycle management (issuance, suspension, cancellation), merchant and category limitation configuration,
    metadata tagging for tracking, authorization and settlement data retrieval, and real-time account balance access. Authentication
    is HMAC-SHA256 request signing or OAuth 2.0 client credentials. Full endpoint reference and code samples (Python, Node.js,
    Java, C#, PHP) are published on the Mesh Developers Portal, which is served behind HTTP Basic authentication.
  humanURL: https://developers.meshpayments.com
  baseURL: https://api.meshpayments.com
  tags:
  - Payments
  - Corporate Cards
  - Card Issuing
  - Spend Management
  properties:
  - type: Documentation
    url: https://developers.meshpayments.com
  - type: Authentication
    url: authentication/mesh-payments-authentication.yml
  - type: OAuthScopes
    url: scopes/mesh-payments-scopes.yml
  - type: Webhooks
    url: asyncapi/mesh-payments-webhooks.yml
- name: Mesh Payments MCP Server
  description: OAuth-protected Model Context Protocol (MCP) server operated by Mesh at api.meshpayments.com/mcp. The endpoint
    advertises RFC 9728 OAuth 2.0 Protected Resource Metadata at /.well-known/oauth-protected-resource/mcp and challenges
    unauthenticated JSON-RPC calls with a WWW-Authenticate Bearer header. Mesh describes its orchestration layer as MCP-compatible
    so customers can connect their own AI agents and build workflows on top of Mesh policy governance.
  humanURL: https://meshpayments.com/orchestration/
  baseURL: https://api.meshpayments.com/mcp
  tags:
  - MCP
  - Agents
  - Spend Management
  properties:
  - type: MCPServer
    url: mcp/mesh-payments-mcp.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/mesh-payments-plans-pricing.yml
- url: https://meshpayments.com/feed/
  type: BlogRSS
- type: DomainSecurity
  url: security/mesh-payments-domain-security.yml
- type: Website
  url: https://meshpayments.com/
- type: DeveloperPortal
  url: https://developers.meshpayments.com
- type: Documentation
  url: https://kb.meshpayments.com/support/integrators-corner/
- type: Support
  url: https://kb.meshpayments.com/
- type: HelpCenter
  url: https://kb.meshpayments.com/
- type: Blog
  url: https://meshpayments.com/blog/
- type: GitHubOrganization
  url: https://github.com/mesh-payments
- type: Pricing
  url: https://meshpayments.com/pricing/
- type: SignUp
  url: https://app.meshpayments.com/
- type: Login
  url: https://app.meshpayments.com/
- type: TermsOfService
  url: https://meshpayments.com/legal/
- type: PrivacyPolicy
  url: https://meshpayments.com/privacy/
- type: ChangeLog
  url: https://meshpayments.com/feature-updates/
- type: ChangeLog
  url: changelog/mesh-payments-changelog.yml
- type: Integrations
  url: https://meshpayments.com/partners-and-integrations/
- type: WellKnown
  url: well-known/mesh-payments-well-known.yml
- type: LLMsTxt
  url: llms/mesh-payments-llms.txt
- type: MCPServer
  url: mcp/mesh-payments-mcp.yml
- type: Authentication
  url: authentication/mesh-payments-authentication.yml
- type: OAuthScopes
  url: scopes/mesh-payments-scopes.yml
- type: Conventions
  url: conventions/mesh-payments-conventions.yml
- type: Lifecycle
  url: lifecycle/mesh-payments-lifecycle.yml
- type: Conformance
  url: conformance/mesh-payments-conformance.yml
- type: Compliance
  url: https://meshpayments.com/security-is-our-priority/
- type: Security
  url: https://meshpayments.com/vulnerability-disclosure-policy/
- type: VulnerabilityDisclosure
  url: security/mesh-payments-vulnerability-disclosure.yml
- type: TrustCenter
  url: security/mesh-payments-trust-center.yml
- type: Webhooks
  url: asyncapi/mesh-payments-webhooks.yml
- type: Packages
  url: packages/mesh-payments-packages.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 18
  pass: local-v1

Mesh Payments API — frequently asked questions

Does Mesh Payments have an API?

Yes. APIs.io lists 2 APIs from Mesh Payments, including Mesh Payments API and Mesh Payments MCP Server.

How do I authenticate with the Mesh Payments API?

Mesh Payments documents its authentication (http/oauth2/custom-hmac · 3 schemes). The details are profiled on APIs.io as Mesh Payments Authentication.

Does Mesh Payments have an MCP server?

Yes. APIs.io lists 1 MCP server for Mesh Payments: Remote MCP server at api.meshpayments.com over HTTP.

Is the Mesh Payments API ready for AI agents?

Mesh Payments has a Kin Score of 47.3 out of 100 (developing) and an Agent Readiness score of 44.6 (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.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/mesh-payments"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/mesh-payments/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/mesh-payments/evidence"

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.

GitHub Google LinkedIn

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