> For the complete documentation index, see [llms.txt](https://divigent.gitbook.io/divigent-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://divigent.gitbook.io/divigent-docs/getting-started/introduction.md). # Introduction Divigent is a treasury infrastructure layer for agent wallets that hold and spend stablecoins. Agent wallets are operational accounts: they receive revenue, hold working balances, sign paid requests, and may need liquidity without human intervention. Divigent solves the wallet-level treasury problem: assess whether a wallet has enough liquid capital before it transacts, maintain adaptive reserves, recall only the shortfall when liquidity is low, and deploy surplus stablecoins into monitored yield venues. Divigent combines payment hooks, a Reserve Intelligence API, audited onchain contracts, a 4-hour time-weighted routing oracle, venue monitoring, and non-custodial receipt accounting. The current production deployment supports Base mainnet USDC and x402 agent-wallet flows; Base is deployment proof, not the category boundary. The backend does not custody funds or sign transactions; it produces reason-coded liquidity assessments and recall/deploy recommendations that the wallet's execution layer can apply under operator policy. Predictive Reserves makes the reserve layer personalized. Divigent learns from registered wallet behavior, trains per-wallet quantile models, runs forecasts in shadow mode, evaluates predictions against realized future outflows, and only allows calibrated models to raise live reserves above deterministic safety floors. As integrations accumulate, this creates a proprietary behavioral dataset around agent-wallet spend, reserve, recall, and deployment patterns, improving reserve priors, policy templates, calibration, and anomaly detection. ## The Agentic Treasury Problem Agent wallets differ from human wallets because their balances are operational capital. They receive stablecoins, hold working buffers, sign paid actions, and may need to transact again without a human watching the wallet. Once agent wallets hold real balances, the treasury question becomes continuous: how much capital must remain liquid for near-term demand, and how much can be deployed without making the wallet fragile? Divigent models each agent wallet as having three capital states: committed capital for a pending action, reserve capital kept liquid for near-term operations, and productive capital deployed to vetted yield venues. The goal is not to maximize APY in isolation. The goal is to keep the wallet liquid enough to operate first, then make the surplus productive. ## Why Divigent Is Different Existing yield products are built for human treasury management or passive deposits. Agent wallet float has different requirements: liquidity at unpredictable times, reserve logic, automation without arbitrary custody, and principal-aware accounting. Divigent is built around those constraints: * **Agent-native.** Designed for idle intervals between x402 payment and settlement events. * **Non-custodial by design.** Agent wallets retain ownership of principal and dvUSDC receipt shares. * **Yield-only fee model.** The protocol earns only when the wallet realizes yield. * **x402-aware.** SDK hooks can recall liquidity before a paid request is signed and redeploy idle USDC after settlement. * **Base-native.** Routes USDC into supported Base lending venues with transparent on-chain accounting. ## Where to Go Next * [Architecture](/divigent-docs/architecture/overview.md) covers the three-layer system, core contracts, and dvUSDC accounting. * [Deposit Flow](/divigent-docs/protocol/deposit.md) and [Withdrawal Flow](/divigent-docs/protocol/withdrawal.md) walk through what happens on-chain. * [Oracle & Routing](/divigent-docs/protocol/oracle-and-routing.md) explains how venues are selected and rate data is time-weighted. * [SDK Integration](/divigent-docs/integration/sdk-integration.md) shows how to wrap an agent's payment lifecycle. * [MCP Server](/divigent-docs/quick-start/mcp.md) documents the tools exposed to agent frameworks. * [Fees & Accounting](/divigent-docs/protocol/fees.md) details the realized-yield fee. * [Security Model](/divigent-docs/protocol/security.md) covers risk surfaces and emergency controls. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://divigent.gitbook.io/divigent-docs/getting-started/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.