Lorum

Lorum (developer brand "Fuse") is a fintech providing banking-grade clearing, settlement, and treasury infrastructure - "built for clearing, not lending." Through one API it offers multi-currency clearing across 30+ markets, programmable segregated account infrastructure (including virtual IBANs), and cash management with FX and liquidity sweeps. It targets payroll/EOR platforms, fintechs and PSPs, trading and investment platforms, and marketplaces that need to move and settle funds across global payment rails without standing up local banking entities. The API (OAuth2 client-credentials auth, idempotency-keyed money movement, and webhook event notifications) covers customers/KYC, accounts, payments, internal transfers, currency exchange, documents, batch payments, and full sandbox scheme simulation. Lorum is backed by Northzone.

Lorum publishes 10 API contracts indexed on the APIs.io network, including Accounts API, Customers API, Customers V2 API, and 7 more. Tagged areas include Company, Fintech, Payments, Banking, and Clearing.

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

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

🌐 Visit website 📡 Profile data on GitHub

44.7/100 developing ▬ flat Agent 46/100 agent native Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 4 Agent Skills

Company Fintech Payments Banking Clearing Settlement Treasury Multi-Currency Account Foreign Exchange Webhook

What this lets a business do 4

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

Payments & Card Management

BC-1340

Internal TransfersPayments

POST /v1/accounts/{account_id}/payments POST /v1/internal-transfers

Treasury Management

BC-210

Exchange

POST /v1/exchange GET /v1/exchange/quote

Deposits & Savings Management

BC-1330

Accounts

POST /v1/customers/{customer_id}/accounts GET /v1/accounts/{account_id}/history GET /v1/accounts/{account_id} GET /v1/accounts

Banking Customer Management

BC-1300

Customers

POST /v1/customers/{customer_id}/onboarding/{currency} POST /v1/customers/{customer_id}/documents

Kin Score

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

Composite quality — 44.7/100 · developing

Contract Quality 10.5 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 2.6 / 15

Operational Transparency 2.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.5 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 46/100 · agent native

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 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 6 / 6

Protected Resource Metadata 0 / 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 Banking & Open Finance 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/lorum/"><img src="https://apis.io/badge/lorum/card.svg" alt="Lorum 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
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
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)
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

4 more unmet checks in the Agent Readiness table above.

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

Access Clarity scores 17.1 — up to +16.6 composite points
Contract Quality scores 56.1 — up to +11.0 composite points
Operational Transparency scores 23.7 — up to +9.9 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/lorum/apis.yml: open an issue on github.com/api-evangelist/lorum 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	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.

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 10

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

Lorum Accounts API

The Accounts API from Lorum — 5 operation(s) for accounts.

Lorum Customers API

The Customers API from Lorum — 10 operation(s) for customers.

Lorum Customers V2 API

The Customers V2 API from Lorum — 1 operation(s) for customers v2.

Lorum Documents API

The Documents API from Lorum — 2 operation(s) for documents.

Lorum Exchange API

The Exchange API from Lorum — 2 operation(s) for exchange.

Lorum Internal Transfers API

The Internal Transfers API from Lorum — 1 operation(s) for internal transfers.

Lorum Payments API

The Payments API from Lorum — 2 operation(s) for payments.

Lorum Simulation API

The Simulation API from Lorum — 4 operation(s) for simulation.

Lorum Transactions API

The Transactions API from Lorum — 8 operation(s) for transactions.

Lorum OAUTH API

The Oauth API from Lorum — 1 operation(s) for oauth.

Scroll for all 10

Open Collections 10

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

Fuse Accounts API

OPEN COLLECTION

Fuse Accounts Customers API

OPEN COLLECTION

Fuse Accounts Customers V2 API

OPEN COLLECTION

Fuse Accounts Documents API

OPEN COLLECTION

Fuse Accounts Exchange API

OPEN COLLECTION

Fuse Accounts Internal Transfers API

OPEN COLLECTION

Fuse Accounts Oauth API

OPEN COLLECTION

Fuse Accounts Payments API

OPEN COLLECTION

Fuse Accounts Simulation API

OPEN COLLECTION

Fuse Accounts Transactions API

OPEN COLLECTION

Scroll for all 10

Agent Skills 4

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

Estimate and create an outbound payment

AGENT SKILL

Quote and execute a currency exchange or internal transfer

AGENT SKILL

Onboard a customer and open an account

AGENT SKILL

Simulate payment scheme actions in the sandbox

AGENT SKILL

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Lorum

SLA

Event Specifications 1

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

Lorum (Fuse) Webhooks

Real-time webhook events emitted by Lorum for payments, transfers, currency exchanges, account changes, and customer onboarding. Generated from the provider's published webhook ...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Lorum API Rules

64 rules · 53 errors 8 warnings 3 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.

Lorum Openapi Overlay

3 actions · update · lorum-openapi-original.json

DERIVED

Security Posture 2

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

Lorum Authentication

oauth2/http · 2 schemes

SECURITY

Lorum Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Login

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

AsyncAPI

AsyncAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

WellKnown

AgentSkill

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Scroll for all 7

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Blog

Blog

Website

Website

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: lorum
name: Lorum
description: Lorum (developer brand "Fuse") is a fintech providing banking-grade clearing, settlement, and treasury infrastructure
  - "built for clearing, not lending." Through one API it offers multi-currency clearing across 30+ markets, programmable
  segregated account infrastructure (including virtual IBANs), and cash management with FX and liquidity sweeps. It targets
  payroll/EOR platforms, fintechs and PSPs, trading and investment platforms, and marketplaces that need to move and settle
  funds across global payment rails without standing up local banking entities. The API (OAuth2 client-credentials auth, idempotency-keyed
  money movement, and webhook event notifications) covers customers/KYC, accounts, payments, internal transfers, currency
  exchange, documents, batch payments, and full sandbox scheme simulation. Lorum is backed by Northzone.
url: https://raw.githubusercontent.com/api-evangelist/lorum/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- northzone
x-tier: enriched
x-tier-reason: portfolio-lead
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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/691dc048eb27bd1d29e459b1/692b0683e9466303595474d6_1ddad7f49147abb7075cab3048b9487b_Opengraph.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Company
- Fintech
- Payments
- Banking
- Clearing
- Settlement
- Treasury
- Multi-Currency
- Account
- Foreign Exchange
- Webhook
tags_raw:
- Company
- Fintech
- Payments
- Banking
- Clearing
- Settlement
- Treasury
- Multi-Currency
- Accounts
- Foreign Exchange
- Webhooks
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: lorum:lorum-accounts-api
  name: Lorum Accounts API
  description: The Accounts API from Lorum — 5 operation(s) for accounts.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/lorum-accounts-api-openapi.yml
- aid: lorum:lorum-customers-api
  name: Lorum Customers API
  description: The Customers API from Lorum — 10 operation(s) for customers.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/lorum-customers-api-openapi.yml
- aid: lorum:lorum-customers-v2-api
  name: Lorum Customers V2 API
  description: The Customers V2 API from Lorum — 1 operation(s) for customers v2.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Customers V2
  properties:
  - type: OpenAPI
    url: openapi/lorum-customers-v2-api-openapi.yml
- aid: lorum:lorum-documents-api
  name: Lorum Documents API
  description: The Documents API from Lorum — 2 operation(s) for documents.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Documents
  properties:
  - type: OpenAPI
    url: openapi/lorum-documents-api-openapi.yml
- aid: lorum:lorum-exchange-api
  name: Lorum Exchange API
  description: The Exchange API from Lorum — 2 operation(s) for exchange.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Exchange
  properties:
  - type: OpenAPI
    url: openapi/lorum-exchange-api-openapi.yml
- aid: lorum:lorum-internal-transfers-api
  name: Lorum Internal Transfers API
  description: The Internal Transfers API from Lorum — 1 operation(s) for internal transfers.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Internal Transfers
  properties:
  - type: OpenAPI
    url: openapi/lorum-internal-transfers-api-openapi.yml
- aid: lorum:lorum-payments-api
  name: Lorum Payments API
  description: The Payments API from Lorum — 2 operation(s) for payments.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Payments
  properties:
  - type: OpenAPI
    url: openapi/lorum-payments-api-openapi.yml
- aid: lorum:lorum-simulation-api
  name: Lorum Simulation API
  description: The Simulation API from Lorum — 4 operation(s) for simulation.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Simulation
  properties:
  - type: OpenAPI
    url: openapi/lorum-simulation-api-openapi.yml
- aid: lorum:lorum-transactions-api
  name: Lorum Transactions API
  description: The Transactions API from Lorum — 8 operation(s) for transactions.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/lorum-transactions-api-openapi.yml
- aid: lorum:lorum-oauth-api
  name: Lorum OAUTH API
  description: The Oauth API from Lorum — 1 operation(s) for oauth.
  humanURL: https://docs.lorum.com/docs/getting-started
  baseURL: https://api.fuse.me
  tags:
  - OAuth
  - Authentication
  tags_raw:
  - Oauth
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/lorum-oauth-api-openapi.yml
common:
- type: CapabilityMap
  url: capabilities/lorum-capability-edges.yml
  name: Lorum Business Capability Map
- type: Overlay
  url: overlays/lorum-openapi-overlay.yaml
- type: DeveloperPortal
  url: https://docs.lorum.com/docs/getting-started
- type: Documentation
  url: https://docs.lorum.com/docs/getting-started
- type: APIReference
  url: https://docs.lorum.com/reference/getting-a-bearer-token
- type: GettingStarted
  url: https://docs.lorum.com/docs/getting-started
- type: Authentication
  url: authentication/lorum-authentication.yml
- type: Conventions
  url: conventions/lorum-conventions.yml
- type: Idempotency
  url: conventions/lorum-conventions.yml
- type: ErrorCatalog
  url: errors/lorum-problem-types.yml
- type: Lifecycle
  url: lifecycle/lorum-lifecycle.yml
- type: StatusPage
  url: https://status.lorum.com/
- type: Conformance
  url: conformance/lorum-conformance.yml
- type: Sandbox
  url: sandbox/lorum-sandbox.yml
- type: DataModel
  url: data-model/lorum-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/lorum-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: WellKnown
  url: well-known/lorum-well-known.yml
- type: AsyncAPI
  url: asyncapi/lorum-webhooks-asyncapi.yml
- type: Webhooks
  url: asyncapi/lorum-webhooks-asyncapi.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/lorum-llms.txt
- type: DomainSecurity
  url: security/lorum-domain-security.yml
- type: Blog
  url: https://www.lorum.com/blog
- type: PrivacyPolicy
  url: https://www.lorum.com/legal/privacy-policy
- type: Login
  url: https://app.lorum.com/
- type: Support
  url: https://www.lorum.com/contact-us
- type: Website
  url: https://www.lorum.com
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 16
  pass: local-v1

Lorum API — frequently asked questions

Does Lorum have an API?

Yes. APIs.io lists 10 APIs from Lorum, including Lorum Accounts API, Lorum Customers API and Lorum Customers V2 API, and 7 more.

Is there an OpenAPI specification for the Lorum API?

Yes. APIs.io indexes 10 OpenAPI specifications for Lorum, each linked for download from this page.

How do I authenticate with the Lorum API?

Lorum documents its authentication (oauth2/http · 2 schemes). The details are profiled on APIs.io as Lorum Authentication.

Is the Lorum API ready for AI agents?

Lorum has a Kin Score of 44.7 out of 100 (developing) and an Agent Readiness score of 46.1 (agent-native), 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/lorum"

All providers

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

Every operation they expose

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

How their score was established

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