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

# Your Wallet

> Your 1Tx non-custodial wallet: what it is, what you approve, and what 1Tx can never do

## Your 1Tx non-custodial wallet

The first time you sign in through the MCP, 1Tx creates **your 1Tx non-custodial wallet**: an
ERC-4337 smart wallet that you own, tied to your Google or email login. The same login opens it at
[app.1tx.fi](https://app.1tx.fi).

* **You hold the keys.** 1Tx never sees or stores your keys, and cannot sign for you.
* **Nothing moves without your approval.** Your agent builds batches; you approve each one.
* **Gas is paid in USDC** from the wallet itself. You never need ETH or any other native token.
* **Funds go straight to the protocol.** The calls target Aave, Morpho, Euler and the others
  directly. There is no 1Tx contract in the path.

Your 1Tx non-custodial wallet works on **Arbitrum, Base and Monad**. Markets on Unichain can be
read but not acted on from the wallet: action tools return `approvalUrl: null` there.

## What you approve

Every action tool returns an `approvalUrl` (`https://app.1tx.fi/approve/{actionId}`). Your agent
gives you the link; you open it, see each call in the batch and what it is expected to produce,
and approve. Your wallet signs and sends the batch as one atomic user operation. Either every call
lands or none does.

<Steps>
  <Step title="The agent proposes">
    For example, `deposit` 500 USDC into a Morpho vault on Base. The server simulates the batch
    against live chain state and refuses it if it would revert.
  </Step>

  <Step title="You approve">
    Open the link, check the calls, approve. A batch is built for a recent block: if it has
    expired, ask the agent to build it again.
  </Step>

  <Step title="It lands">
    The batch ends with an attribution tag, so 1Tx sees it land without the agent reporting
    anything. `status`, `history` and `action_status` update on their own.
  </Step>
</Steps>

## What the sign-in lets your agent do

Signing in grants your client two scopes on your 1Tx non-custodial wallet:

| Scope | Allows |
| - | - |
| `read` | Read your wallet's book, actions and history |
| `trade` | Build batches for your wallet and return approval links |

Neither scope can send a transaction. The agent can only act on your own wallet: a request to act
for another wallet is refused.

An access token lasts one hour and refreshes on its own for up to 30 days. After that, sign in
again.

## Bridging between chains

A bridge burns USDC on one chain over Circle CCTP V2 and names **your own wallet** as the only
account that can redeem it on the other. 1Tx never holds the funds in flight, and an agent that
stops halfway strands nothing.

1. `bridge` builds the burn. Approve it.
2. `action_status(actionId)` shows the CCTP state. Nothing polls for you: ask when you want it.
3. At `destination_ready`, `redeem_bridge` builds the redeem on the destination chain, and
   optionally a deposit of what arrived. Approve it.

## Sending funds to another wallet

`withdraw` brings a position back into your 1Tx wallet. To move funds out of it, `transfer` builds
one token transfer to the address you name, on one chain.

* `max` USDC sends your balance less the gas reserve, since gas is paid in USDC from the same
  wallet. A fixed amount that leaves too little for gas is refused with the most you can send.
* The approval page shows the recipient in full, and warns when the address is a smart contract.
  Check it before you approve: a transfer can't be undone.

## Loops

A levered loop is opened, adjusted and closed as one atomic batch each, with the resulting health
factor measured before you see it. Take a loop off with `close_loop`: `withdraw` does not unwind
it.

If a loop needs `requiresAccountConfig`, the batch changes your wallet's e-mode in that lending
pool, which re-prices any other position you hold in the same pool.

## Tracking

From the first batch that lands, 1Tx takes daily snapshots of your wallet's book, so its value can be
followed over time alongside the actions in `history`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.