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 publishes 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 22 more developer resources.

🌐 Visit website 📡 Source on GitHub

52.5/100 developing ▬ flat Agent 41/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0

2 APIs 1 MCP Servers

CompanyPaymentsSpend ManagementExpense ManagementCorporate CardsTravelAccounts PayableFintechCard IssuingAccounting Automation

Kin Score

Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0

Composite quality — 52.5/100 · developing

Contract Quality 11.0 / 21

Developer Ergonomics 7.4 / 17

Commercial Clarity 10.3 / 17

Operational Transparency 4.4 / 11

Governance 1.3 / 10

Discoverability 7.4 / 9

Regulatory Posture 10.8 / 15

Agent readiness — 41/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

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

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.

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/.

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-payments: 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 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.

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 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

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.
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.20'
created: '2026-08-04'
modified: '2026-08-04'
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: 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