为什么值得关注

它引入了一个与提供商无关的抽象层，同时面向金融科技应用和 AI 代理，内置清晰的策略引擎，使自主性可配置且安全，并提供无需凭据即可运行的交互式演示。

适合谁使用

构建可复用金融原语的金融科技开发者
需要安全、受限金融工具的 AI 代理开发者
探索新银行或嵌入式金融产品的初创公司
评估策略控制金融 API 的工程师

典型使用场景

快速原型化一个包含开户、KYC、余额、存款和转账的新银行应用
为 AI 代理提供类型化 SDK 和 MCP 工具，在策略护栏下执行金融操作
通过将演示数据替换为实时 Swipelux 沙箱来测试与提供商无关的集成
Fork 启动器并自定义品牌以适配新的金融科技产品

项目优势

无需凭据或 .env 文件即可在本地运行的完全交互式演示
与提供商无关的设计，通过清晰的 DataSource 边界便于未来适配器集成
明确的执行生命周期（验证→评估→授权→执行→规范→审计），确保代理交互安全
类型化的 TypeScript 原语和将 UI 与领域逻辑分离的模块化架构

使用前须知

早期构建——MCP 服务器、独立 SDK、策略引擎和完整 KYB 功能尚未发布
演示数据和地址不得用于真实资金，并非生产级合规或托管系统
用户需自行负责提供商接入、凭据、司法管辖要求和运营控制

README 快速开始

Neobank Primitives

Agent-native financial primitives for fintechs and software that can act.

Build accounts, identity flows, deposits, payouts, wallet transfers, and compliance-aware operations on a provider-neutral contract. Start with the working neobank demo; extend it into policy-controlled MCP tools and a TypeScript SDK.

Run locally · Explore the primitives · See the architecture · Read the roadmap

Money movement should be composable

Most financial APIs expose endpoints. Autonomous software needs a safer abstraction: explicit intent, policy evaluation, normalized execution, durable state, and receipts it can reason about.

Neobank Primitives is building that layer for two consumers:

Fintech applications that want reusable identity, account, balance, and transaction building blocks.
AI agents that need narrowly scoped financial tools, machine-readable outcomes, and human approval when policy requires it.

The repository is useful now as a fully interactive neobank starter with realistic demo data and a Swipelux sandbox integration. The MCP server, standalone SDK, policy engine, and full KYB surface described below are the direction of the project and are not yet shipped as a production runtime.

The primitive surface

Primitive	Working product flow	Target MCP + SDK contract
Identity	Customer onboarding and KYC state	Create, retrieve, and monitor customer identity
Businesses	Business account persona	Create organizations and track KYB requirements
Accounts	Fiat accounts, stablecoin wallets, and balances	Provision and query normalized financial accounts
Transactions	Quotes, bank payouts, and wallet transfers	Quote, authorize, execute, and inspect money movement
Storage	Local demo ledger and provider-backed state	Persist normalized operation state, receipts, and metadata
Controls	Human-readable execution explainers	Evaluate policies, require approval, and expose audit history

The contract is designed to stay provider-neutral. Swipelux is the first adapter, not the shape every integration must inherit.

neobank-primitives