Meow
Meow is a business banking and treasury platform for companies, offering FDIC partner-bank checking accounts, corporate and virtual cards, domestic and international payments (ACH, wire, book, FedNow), USDC crypto transfers, invoicing and bill pay, treasury yield on idle cash, and business onboarding (KYB). Meow exposes all of this through a unified REST API at developer.meow.com (OpenAPI 3.1, 119 operations across accounts, transfers, cards, billing, bills, onboarding, webhooks, and partner APIs) plus a first-party hosted MCP server that lets AI assistants read balances and draft human-approved payments. Authentication is via scoped API keys (x-api-key) or OAuth 2.1 with PKCE on the MCP surface.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Meow the way a machine reads it — 32 machine-readable artifacts across 26 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Meow scores 58.6/100 (developing), with a separate agent-readiness read of 80/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Meow
Each block below is one kind of artifact we hold for Meow. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 26
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Meow Accounts API
Access and manage accounts.
Meow API Keys API
Retrieve metadata about API keys and their accessible entities.
Meow Approvals API
The Approvals API from Meow — 1 operation(s) for approvals.
Meow Balances API
Retrieve account balances and available funds.
Meow Bills API
View and manage bills for vendor payments.
Meow Cards API
Manage virtual and physical cards, and view transactions and insights.
Meow Collection Accounts API
Manage accounts for payment collection.
Meow Contacts API
Manage contacts for crypto and USDC transfers.
Meow Customers API
Manage invoicing customers and their details.
Meow Entities API
The Entities API from Meow — 12 operation(s) for entities.
Meow Health API
The Health API from Meow — 1 operation(s) for health.
Meow Invoices API
Create and manage invoices.
Meow Limits API
The Limits API from Meow — 1 operation(s) for limits.
Meow Line Items API
Manage invoice line items.
Meow Partner Onboarding API
Onboard entities using your partner API key.
Meow Partner Webhooks API
The Partner Webhooks API from Meow — 6 operation(s) for partner webhooks.
Meow Payment Methods API
View available payment method types.
Meow Payment Networks API
Manage payment networks and routing information.
Meow Products API
Manage products and pricing for invoicing.
Meow Routing Numbers API
Validate routing numbers and retrieve bank information.
Meow Security Policies API
The Security Policies API from Meow — 1 operation(s) for security policies.
Meow Simulations API
Trigger simulated events — inbound transfers, card authorizations, application approval — to test integrations end-to-end without real money movement. **Not available in product...
Meow Tax Forms API
Retrieve IRS tax forms (1099 family) issued for accounts.
Meow Transactions API
Retrieve account transaction history and details.
Meow Transfers API
Initiate ACH, wire, book, and crypto transfers, and retrieve transfer details.
Meow Webhooks API
Manage webhook subscriptions and inspect delivery history.
Scroll within the panel for all 26 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
meow-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Meow Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Meow — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/meow · machine-readable index on apis.io