> 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/core-concepts/agentic-wallets.md).

# Agentic Wallets

An **agentic wallet** is not a new kind of wallet. It is a composition of three things Neucron already provides:

```mermaid
flowchart TB
    subgraph B["Your business"]
        APP["Dedicated app<br/>(governed team member)"]
        WAL["Server-side wallet<br/>(single-shard or MPC)"]
        AGT["Your AI agent"]
        APP -->|controls within permissions| WAL
        AGT -->|Neucron MCP service| APP
    end
    POL["Permissions, approval thresholds, MFA"] -.->|govern| APP
```

1. **A dedicated app** created by the business. The app is a governed team member with exactly the permissions you grant: which wallets it can use, whether it can create invoices or bills, whether it can initiate payouts, and under which approval thresholds.
2. **A server-side wallet** associated with the app, holding the assets the agent operates with: a budget, an operational float, or a collection address.
3. **The Neucron MCP service**, which exposes the app's permitted capabilities as tools (`neucron_*`) that any MCP-compatible AI agent can call.

The result: **an AI agent that can autonomously operate a wallet and business resources, inside a permission envelope you fully control.** Change the app's role and the agent's power changes with it. Every action is authenticated, scoped, policy-checked, and auditable, exactly as if a human team member had acted.

## Why the permission model is the product

Giving an agent a raw private key is how funds get lost. The Neucron model instead gives the agent **no keys at all**: it holds only the authority of its app, subject to:

* Resource scoping (which wallets, which modules)
* [Payout approval thresholds](https://timechain.gitbook.io/neucron/payments/bills-payouts-and-approvals) (the agent initiates; humans approve above limits)
* Role-based permissions (the agent can draft an invoice but not release treasury funds)
* Full audit trail of every tool call

## Agentic finance vs financial agents

Two distinct categories of agent workload run on this foundation:

|                         | **Agentic finance**                                                                                                                                                                                          | **Financial agents**                                                                                                                                                                |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| What it is              | Automation of a business's **existing finance-department workflows**                                                                                                                                         | Business agents with **their own budgets**, making decisions and achieving goals autonomously                                                                                       |
| Examples                | AR agent chasing and reconciling receivables; AP agent processing bills and scheduling payouts; accounting agent posting entries; treasury agent rebalancing across rails; controller agent enforcing policy | A procurement agent that negotiates and pays suppliers within a monthly budget; a marketing agent that pays for services it needs; a treasury agent pursuing yield within a mandate |
| Money movement          | Moves the business's money under existing approval policies                                                                                                                                                  | Moves its **own** budget under a mandate, escalating exceptions to humans                                                                                                           |
| Neucron building blocks | App + permissions + invoicing/bills/payout tools + approval thresholds                                                                                                                                       | App + dedicated budget wallet + scoped permissions + spend thresholds                                                                                                               |

Both patterns use the identical primitive: **an app with a wallet, a permission envelope, and an agent speaking MCP.** The difference is only in how you scope the mandate.

## Getting started

1. Create an app in your business and grant it the minimal role for the workflow.
2. Create (or associate) a server-side wallet as the agent's operating wallet.
3. Connect your agent to the [Neucron MCP server](https://timechain.gitbook.io/neucron-mcp) with the app's credentials.
4. Set approval thresholds so material amounts route to human approvers.

Full tool reference and flows: [Neucron MCP documentation](https://timechain.gitbook.io/neucron-mcp).