# Meso

**Canonical:** https://apis.io/providers/meso/  
**Website:** https://meso.network  
**APIs profiled:** 0

Meso is payment infrastructure designed for crypto. Backed by Ribbit Capital, the company is positioned as a payments-rails provider for the cryptocurrency sector. As of this enrichment pass its public web presence is a single-page marketing site at meso.network with no publicly documented developer portal, API reference, or OpenAPI definition surfaced yet. The one machine-readable artifact the company publishes is a PGP-signed RFC 9116 security.txt at /.well-known/security.txt declaring a security contact and disclosure policy. This profile was added to the API Evangelist network as a Ribbit Capital portfolio lead and is tracked for future API surface as the product launches.

## Kin Score — 6.2 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+1.1 from 5.1).

| Facet | Score |
|---|---|
| Discoverability | 68.5 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 10.5 |
| Developer Ergonomics | 0.0 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

Regulatory layer — **Payments**: 18.8 (matched via tags).

## Agent readiness — 2.6 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | yes |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (2)

- **Meso Domain Security** — TLSv1.3 · HSTS · DMARC
- **Meso Vulnerability Disclosure** — security.txt · contact published

## Tags

Company, Crypto, Payments, Payment Infrastructure, Cryptocurrency, Fintech, Blockchain

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/meso/). Scores are computed from the provider's own public artifacts under a published rubric.