# Introduction

Divigent is agent-native yield infrastructure for USDC on Base.

It is built around a simple observation. Autonomous agents are beginning to hold real operating balances, but most of that capital sits idle between payment events. An agent may need USDC for execution, settlement, subscriptions, API calls, escrow, or treasury movement, yet only a fraction of its balance is actively committed at any given moment.

That unused balance is *agent wallet float*.

Divigent turns that float into productive capital. It gives agent wallets a way to deploy idle USDC into supported DeFi lending venues, recall liquidity when payments need to happen, and account for principal and yield on-chain.

## The Agent Wallet Float Problem

In traditional finance, treasury teams sweep unused balances into money market instruments or overnight lending. Agent wallets do not have that operational layer by default. They hold USDC because it is liquid, programmable, and payment-ready, but idle USDC earns nothing.

Divigent is designed to close that gap for on-chain agents.

## 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 payment and settlement events.
* **Non-custodial by design.** The router does not hold idle USDC between transactions.
* **Yield-only fee model.** The protocol earns only when the wallet realises yield.
* **x402-aware.** Wraps agent payment lifecycles through SDK hooks.

## 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/mcp/overview.md) documents the tools exposed to agent frameworks.
* [Fees & Accounting ](/divigent-docs/protocol/fees.md)details the 10% realised-yield fee.
* [Security Model ](/divigent-docs/protocol/security.md)covers risk surfaces and emergency controls.


---

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

```
GET https://divigent.gitbook.io/divigent-docs/getting-started/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.