For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Neucron is whitelabelled wallet infrastructure for fintechs. Wallets, payments, and agentic finance on every major rail, behind one API.

Whitelabelled wallet infrastructure for fintechs

Neucron is the wallet and payments infrastructure layer for fintechs. You bring your product, your brand, and your customers. Neucron provides the wallets, the key management, the compliance gates, and the money movement, invisibly, behind one API.

Everything in Neucron is built around a few ideas worth understanding before you write a line of code:

Start with the concepts

Concept
What you will learn

Why each chain is just a payment rail, and how Neucron abstracts them

What a wallet actually is, minus seed-phrase anxiety

How 2-of-3 shards make keys unstealable and unlosable

Non-custodial, custodial, and server-side MPC, and choosing per wallet

Individuals vs businesses, members, roles, granular permissions

Sign in with Neucron vs fully embedded wallets under your own auth

KYC/KYB levels 1 to 4 and what each unlocks

Apps + server-side wallets + MCP = governed AI agents with budgets

Then move money

Capability
What it covers

Customers, invoices, branded payment links, partial and multi-asset clearing

Vendors, bills, scheduled payouts, amount thresholds, multi-approver and MFA policies

Business treasury and individual holdings, multi-wallet structures

And pick your rails

Reference
What it lists

Live rails and the network roadmap

Token standards, and when each is used

The live support matrix and the asset roadmap


Ways to integrate

Neucron is documented across three companion surfaces. Use the one that matches how you build:

Surface
Best for
Documentation

REST API (this space)

Direct HTTP, OpenAPI, custom clients

API References below

TypeScript SDK (@timechainlabs/neucron-ts-sdk)

Typed Node / web / React Native backends

MCP Server

AI agents & LLM tools (neucron_* tools)

All three talk to the same Neucron backend. Auth tokens and business context work the same way across them.

Base URL (REST API)

Production host is typically https://api.neucron.io. Paths in this documentation are relative to the selected server (some deployments may prefix /v1).

Last updated