> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reinx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Receiving Funds

> Deposit addresses for agent wallets — send USDC on an EVM chain or Solana and inbound payments are converted and credited to the agent's balance automatically

Every agent can receive funds from outside Reinx — payouts from other agents, refunds, revenue from services the agent sells. Each agent has **two deposit addresses**, and anything sent to them is converted and credited to the agent's balance automatically.

## The two deposit addresses

| Channel    | Send | Networks                                                              |
| ---------- | ---- | --------------------------------------------------------------------- |
| **EVM**    | USDC | Any supported EVM chain — Ethereum, Base, Polygon, Arbitrum, Optimism |
| **Solana** | USDC | Solana                                                                |

The EVM address accepts USDC on any of the supported chains — the sender doesn't need to pick a specific network beyond "an EVM chain".

<Warning>
  Send **USDC only**, and only to the addresses shown on the receive surfaces below. Deposits in other assets aren't supported, and transfers that can't be converted are bounced back to the sender. Never reuse an address you saw elsewhere for a different agent — addresses are per-agent.
</Warning>

## Where to find the addresses

**Dashboard** — the agent's detail page shows both addresses on the Crypto Wallet card, with one-click copy.

**MCP** — agents fetch their own addresses with the `get_wallet_addresses` tool. It returns a channel per network family:

```json theme={null}
{
  "addresses": {
    "usdc_evm": { "status": "available", "address": "0x...", "asset": "USDC" },
    "usdc_solana": { "status": "available", "address": "...", "asset": "USDC" }
  }
}
```

A channel can be `unavailable` while it's being provisioned (see below) — in that case `address` is `null`. Never substitute a different address when a channel is unavailable; retry shortly instead.

## What happens after a deposit

1. The deposit is detected on-chain and converted into the agent's balance asset.
2. The credited amount lands in the agent's balance — typically within minutes, though settlement can occasionally take longer.
3. An **inbound payment** appears in the agent's transaction history (and the org's Transactions feed), recording the sender's wallet address and the on-chain transaction hash.
4. Dashboards refresh in real time; agents can confirm with `check_balance`.

Deposits add to the agent's **balance**. They don't change budget limits or spending policy — an agent that receives funds still spends under the same rules.

## Provisioning

Deposit addresses are provisioned automatically when an agent is created. For a brief window a new agent's receive card may show **Provisioning…** and `get_wallet_addresses` may report a channel as `unavailable` — this self-heals within minutes. If a channel stays unavailable for longer, [contact support](/support/contact).