Veem

Veem is a global payments network that lets businesses send, receive, and request payments domestically and across borders. Its Public API covers account creation and KYC (including beneficial ownership), bank accounts and funding methods, claimless payments, invoices, multi-currency wallets, virtual bank accounts, crypto wallets, exchange-rate quotes, and webhooks, with embeddable Web SDK plugins for collecting card, bank, and identity data inside partner apps.

Veem publishes 14 API contracts indexed on the APIs.io network, including Attachment Controller API, Bank Account Controller API, Beneficial Owner Information Controller API, and 11 more. Tagged areas include Payments, B2B Payments, Cross-Border Payments, Invoicing, and Wallets.

The Veem catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

43.4/100 developing ▬ flat Agent 33/100 agent ready Heartbeat 45/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessSelf serve

1 published contract 4 Agent Skills

Payments B2B Payments Cross-Border Payments Invoicing Wallets Fintech Global Payments

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Treasury Management

BC-210

exchange-rate-controller

POST /veem/v1.2/exchangerates/quote/enhanced

Financial Management

BC-200

invoice-controller

POST /veem/v1.2/invoices/{invoiceId}/approve POST /veem/v1.2/invoices/{invoiceId}/cancel POST /veem/v1.2/invoices

Kin Score

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

Composite quality — 43.4/100 · developing

Contract Quality 9.6 / 19

Developer Ergonomics 10.6 / 15

Access Clarity 1.0 / 15

Operational Transparency 2.6 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.6 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 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 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 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 applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

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

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 6.6 — up to +18.7 composite points
Contract Quality scores 51.1 — up to +12.2 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/veem/apis.yml: open an issue on github.com/api-evangelist/veem 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
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	34.8	-	-

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 2

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.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 14

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

Veem Attachment Controller API

Attachment Controller

Veem Bank Account Controller API

Bank Account Controller

Veem Beneficial Owner Information Controller API

Beneficial Owner Information Controller

Veem Claimless Payment Controller API

Claimless Payment Controller

Veem Contact Controller API

Contact Controller

Veem Crypto Wallet Controller API

For managing crypto wallets, including balances, details, transactions and pay-ins

Veem Customer Controller API

Customer Controller

Veem Exchange Rate Controller API

Exchange Rate Controller

Veem Invoice Controller API

Invoice Controller

Veem Meta Controller API

Meta Controller

Veem Open Account Controller API

Open Account Controller

Veem Payment Controller API

Payment Controller

Veem Wallet Controller API

Wallet Controller

Veem Webhook Controller API

Webhook Controller

Scroll for all 14

Open Collections 14

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Veem API v1.2 attachment-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller bank-account-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller beneficial-owner-information-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller claimless-payment-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller contact-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller crypto-wallet-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller customer-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller exchange-rate-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller invoice-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller meta-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller open-account-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller payment-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller wallet-controller API

OPEN COLLECTION

Veem API v1.2 attachment-controller webhook-controller API

OPEN COLLECTION

Scroll for all 14

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

Configure and verify webhooks

AGENT SKILL

Onboard a customer account

AGENT SKILL

Request money with an invoice

AGENT SKILL

Send money with a claimless payment

AGENT SKILL

Event Specifications 1

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

Veem Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Veem API Rules

52 rules · 35 errors 10 warnings 7 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Veem Api Overlay

3 actions · security · veem-api-openapi.yml

DERIVED

Security Posture 2

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

Veem Authentication

oauth2 · 1 scheme

SECURITY

Veem Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Veem Scopes

1 scope · clientCredentials/authorizationCode

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Veem Agentic Access

50 operations · 25 acting · 25 human-in-the-loop

50 operations · 25 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Idempotency

Webhooks

Components

DataModel

Scroll for all 8

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Postman

Packages

SDKs

Access & Security 3

Authentication, authorization, and security posture

OAuthScopes

OAuthScopes

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

StatusPage

StatusPage

Company 3

The organization behind the API

Blog

Blog

BlogRSS

BlogRSS

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: veem
name: Veem
description: Veem is a global payments network that lets businesses send, receive, and request payments domestically and across
  borders. Its Public API covers account creation and KYC (including beneficial ownership), bank accounts and funding methods,
  claimless payments, invoices, multi-currency wallets, virtual bank accounts, crypto wallets, exchange-rate quotes, and webhooks,
  with embeddable Web SDK plugins for collecting card, bank, and identity data inside partner apps.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://logo.clearbit.com/veem.com
url: https://raw.githubusercontent.com/api-evangelist/veem/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- gv
- pantera-capital
x-tier: profile
x-tier-reason: enriched-provider
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-17
tags:
- Payments
- B2B Payments
- Cross-Border Payments
- Invoicing
- Wallets
- Fintech
- Global Payments
apis:
- aid: veem:veem-attachment-controller-api
  name: Veem Attachment Controller API
  description: Attachment Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - attachment-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-attachment-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-bank-account-controller-api
  name: Veem Bank Account Controller API
  description: Bank Account Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - bank-account-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-bank-account-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-beneficial-owner-information-controller-api
  name: Veem Beneficial Owner Information Controller API
  description: Beneficial Owner Information Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - beneficial-owner-information-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-beneficial-owner-information-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-claimless-payment-controller-api
  name: Veem Claimless Payment Controller API
  description: Claimless Payment Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - claimless-payment-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-claimless-payment-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-contact-controller-api
  name: Veem Contact Controller API
  description: Contact Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - contact-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-contact-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-crypto-wallet-controller-api
  name: Veem Crypto Wallet Controller API
  description: For managing crypto wallets, including balances, details, transactions and pay-ins
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - crypto-wallet-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-crypto-wallet-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-customer-controller-api
  name: Veem Customer Controller API
  description: Customer Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - customer-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-customer-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-exchange-rate-controller-api
  name: Veem Exchange Rate Controller API
  description: Exchange Rate Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - exchange-rate-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-exchange-rate-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-invoice-controller-api
  name: Veem Invoice Controller API
  description: Invoice Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - invoice-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-invoice-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-meta-controller-api
  name: Veem Meta Controller API
  description: Meta Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - meta-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-meta-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-open-account-controller-api
  name: Veem Open Account Controller API
  description: Open Account Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - open-account-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-open-account-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-payment-controller-api
  name: Veem Payment Controller API
  description: Payment Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - payment-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-payment-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-wallet-controller-api
  name: Veem Wallet Controller API
  description: Wallet Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - wallet-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-wallet-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
- aid: veem:veem-webhook-controller-api
  name: Veem Webhook Controller API
  description: Webhook Controller
  humanURL: https://developer.veem.com
  baseURL: https://api.veem.com
  tags:
  - WebhookController
  tags_raw:
  - webhook-controller
  properties:
  - type: OpenAPI
    url: openapi/veem-webhook-controller-api-openapi.yml
  - type: Documentation
    url: https://developer.veem.com/docs
  - type: APIReference
    url: https://developer.veem.com/reference
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.veem.com/library/
  type: Blog
- url: https://www.veem.com/library/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/veem-capability-edges.yml
  name: Veem Business Capability Map
- type: Overlay
  url: overlays/veem-api-overlay.yaml
- type: AgenticAccess
  url: agentic-access/veem-agentic-access.yml
- type: Website
  url: https://www.veem.com
- type: DeveloperPortal
  url: https://developer.veem.com
- type: Documentation
  url: https://developer.veem.com/docs
- type: APIReference
  url: https://developer.veem.com/reference
- type: GettingStarted
  url: https://developer.veem.com/docs/intro-to-veem-api
- type: GitHubOrganization
  url: https://github.com/veeminc
- type: Postman
  url: https://www.postman.com/veem/veem-public-workspace/collection/4dtpa4r/veem-public-api
- type: StatusPage
  url: https://status.veem.com
- type: Login
  url: https://apps.veem.com/CustomerApp/o/signin
- type: LLMsTxt
  url: llms/veem-llms.txt
- type: Packages
  url: packages/veem-packages.yml
- type: SDKs
  url: packages/veem-packages.yml
- type: WellKnown
  url: well-known/veem-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/veem-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Conformance
  url: conformance/veem-conformance.yml
- type: ErrorCatalog
  url: errors/veem-error-codes.yml
- type: Lifecycle
  url: lifecycle/veem-lifecycle.yml
- type: OAuthScopes
  url: scopes/veem-scopes.yml
- type: Authentication
  url: authentication/veem-authentication.yml
- type: DomainSecurity
  url: security/veem-domain-security.yml
- type: Sandbox
  url: sandbox/veem-sandbox.yml
- type: Conventions
  url: conventions/veem-conventions.yml
- type: Idempotency
  url: conventions/veem-conventions.yml
- type: Webhooks
  url: asyncapi/veem-webhooks.yml
- type: Components
  url: components/veem-components.yml
- type: DataModel
  url: data-model/veem-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 24
  pass: local-v1

Veem API — frequently asked questions

Does Veem have an API?

Yes. APIs.io lists 14 APIs from Veem, including Veem Attachment Controller API, Veem Bank Account Controller API and Veem Beneficial Owner Information Controller API, and 11 more.

Is there an OpenAPI specification for the Veem API?

Yes. APIs.io indexes 14 OpenAPI specifications for Veem, each linked for download from this page.

How do I authenticate with the Veem API?

Veem uses bearer-token authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Veem Authentication.

Is the Veem API ready for AI agents?

Veem has a Kin Score of 43.4 out of 100 (developing) and an Agent Readiness score of 33.4 (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/veem"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/veem/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.