changelog

Product Update

18 de fev. de 2026

Content

18 de fev. de 2026

MCP

KYC/KYB API, Idempotency and MCP Server

Strengthening Lumx’s infrastructure across compliance orchestration, operational safety, and AI-native integration.

Overview

This release expands Lumx’s API capabilities across identity verification, operational reliability, and AI-native documentation access.

With v2.5.0, clients can now orchestrate KYC and KYB flows programmatically, ensure safe retries through idempotent mutations, and integrate Lumx documentation directly into AI development tools.

1. KYC/KYB orchestration via API

You can now manage the identity verification lifecycle programmatically through the API, without relying on hosted verification links for KYB flows.

For companies (KYB), the flow is fully API-driven.

For individuals (KYC), orchestration is available via API, with the liveness step completed through a hosted verification link.

What’s new:

  • Submit additional KYC/KYB information

  • Upload verification documents programmatically

  • Manage associated parties (UBOs, shareholders, representatives)

  • Start verification processes

  • Track verification status in real time

This enables tighter backend orchestration for regulated environments and removes friction in embedded onboarding flows.

2. Multi-level Corporate Structures

Associated parties now support a parentId field.

This allows representation of nested ownership hierarchies across multiple levels — supporting complex corporate structures and cross-border entities.

Use cases include:

  • Holding companies with layered ownership

  • Multi-entity compliance tracking

  • Structured KYB verification in regulated institutions

3. Idempotency Support

All mutation endpoints (POST, PUT, PATCH) now accept an Idempotency-Key header.

This prevents duplicate operations caused by retries, network issues, or client-side failures.

Details:

  • Keys are valid for 24 hours

  • Repeated requests with the same key return the original response

  • Applies to all state-changing endpoints

This improves transactional reliability and aligns Lumx with modern API infrastructure standards.

Read the Idempotency Guide →

4. MCP Server (Model Context Protocol)

Lumx documentation now exposes an MCP Server endpoint:

https://docs.lumx.io/mcp

This allows AI-powered development tools like:

  • Claude

  • Cursor

  • VS Code

  • Other MCP-compatible agents

to search and retrieve Lumx documentation directly inside the development environment.

This enables:

  • Faster integration cycles

  • Context-aware code generation

  • Reduced developer friction

Learn more about the MCP Server →

Full Changelog

For detailed endpoint-level updates:

https://docs.lumx.io/changelog#kyc/kyb-api-and-idempotency-support-

Stable News

Nesta página

8 de fev. de 2026

Content

Nesta página

API

Individual customers and bank account holders

New feature:

1. Individual customer type

Customers can now be created with type: "INDIVIDUAL" for natural persons. Individual customers require name, taxId, and birthDate fields.

A

{
"type": "INDIVIDUAL",
"name": "William Default",
"taxId": "100.100.100-01",
"birthDate": "1990-01-01"
}

A

{
"type": "INDIVIDUAL",
"name": "William Default",
"taxId": "100.100.100-01",
"birthDate": "1990-01-01"
}

A

{
"type": "INDIVIDUAL",
"name": "William Default",
"taxId": "100.100.100-01",
"birthDate": "1990-01-01"
}

2. Individual bank account holders

Bank accounts now support individual holders with the same structure. For counterparty bank accounts, birthDate is optional.

3. Individual bank account identifier key type as CPF

Bank account now support CPF as a valid keyType identifier for PIX.Enhancement:

4. New relationship types for bank account holders

Added FRIEND, RELATIVE, and EMPLOYEE to the available relationship types for bank account holders.

Stable News

In this page