> For the complete documentation index, see [llms.txt](https://timechain.gitbook.io/neucron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timechain.gitbook.io/neucron/overview.md).

# Overview

## 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:

```mermaid
flowchart TB
    subgraph Concepts["Core concepts"]
        R[Blockchains as rails] --> W[Wallets & keys]
        W --> M[MPC key shards]
        M --> C[Custody models]
    end
    subgraph Org["Your organization"]
        A[Accounts & businesses] --> AP[Apps & whitelabel]
        AP --> AG[Agentic wallets]
    end
    subgraph Move["Moving money"]
        INV[Invoices & payment links]
        PO[Bills, payouts & approvals]
        T[Treasury]
    end
    C --> Move
    Org --> Move
```

### Start with the concepts

| Concept                                                                                                      | What you will learn                                                    |
| ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| [Blockchains as Rails](https://timechain.gitbook.io/neucron/core-concepts/blockchains-as-rails)              | Why each chain is just a payment rail, and how Neucron abstracts them  |
| [Wallets & Keys](https://timechain.gitbook.io/neucron/core-concepts/wallets-and-keys)                        | What a wallet actually is, minus seed-phrase anxiety                   |
| [MPC Key Shards](https://timechain.gitbook.io/neucron/core-concepts/mpc-key-shards)                          | How 2-of-3 shards make keys unstealable and unlosable                  |
| [Custody Models](https://timechain.gitbook.io/neucron/core-concepts/custody-models)                          | Non-custodial, custodial, and server-side MPC, and choosing per wallet |
| [Accounts, Businesses & Teams](https://timechain.gitbook.io/neucron/core-concepts/accounts-businesses-teams) | Individuals vs businesses, members, roles, granular permissions        |
| [Apps & Whitelabel](https://timechain.gitbook.io/neucron/core-concepts/apps-and-whitelabel)                  | Sign in with Neucron vs fully embedded wallets under your own auth     |
| [Compliance Levels](https://timechain.gitbook.io/neucron/core-concepts/compliance-levels)                    | KYC/KYB levels 1 to 4 and what each unlocks                            |
| [Agentic Wallets](https://timechain.gitbook.io/neucron/core-concepts/agentic-wallets)                        | Apps + server-side wallets + MCP = governed AI agents with budgets     |

### Then move money

| Capability                                                                                              | What it covers                                                                        |
| ------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| [Invoices & Payment Links](https://timechain.gitbook.io/neucron/payments/invoices-and-payment-links)    | Customers, invoices, branded payment links, partial and multi-asset clearing          |
| [Bills, Payouts & Approvals](https://timechain.gitbook.io/neucron/payments/bills-payouts-and-approvals) | Vendors, bills, scheduled payouts, amount thresholds, multi-approver and MFA policies |
| [Treasury & Holdings](https://timechain.gitbook.io/neucron/payments/treasury)                           | Business treasury and individual holdings, multi-wallet structures                    |

### And pick your rails

| Reference                                                                                                     | What it lists                                 |
| ------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| [Supported Networks](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks)             | Live rails and the network roadmap            |
| [Asset Protocols & Types](https://timechain.gitbook.io/neucron/networks-and-assets/asset-protocols-and-types) | Token standards, and when each is used        |
| [Assets: Live & Upcoming](https://timechain.gitbook.io/neucron/networks-and-assets/assets-live-and-roadmap)   | 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  | [Neucron TypeScript SDK](https://timechain.gitbook.io/neucron-javascript-sdk) |
| **MCP Server**                                       | AI agents & LLM tools (`neucron_*` tools) | [Neucron MCP](https://timechain.gitbook.io/neucron-mcp)                       |

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

### Base URL (REST API)

```
https://dev.neucron.io
```

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