> For the complete documentation index, see [llms.txt](https://hxz-1.gitbook.io/redelegator-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hxz-1.gitbook.io/redelegator-finance/inroduction/overview.md).
# Overview
**Redelegator Finance** is an autonomous DeFi portfolio manager built on **agent-to-agent (A2A) redelegation**. A user states an intent in plain language — *"Stake my USDC on Lido"* — signs **one** scoped permission, and a chain of specialist agents coordinates on **Base mainnet** to execute it: reasoning with AI, narrowing authority at every hop, paying gas in stablecoin, and delivering the resulting asset **straight back to the user's wallet**.
No agent ever holds the user's funds. Authority flows down a chain of agents and **every hop can only narrow it — never widen it** — using MetaMask's Delegation Framework (ERC-7710 / ERC-7715 + EIP-7702 smart accounts).
> One intent. One signature. Authority only narrows — and the result lands in your wallet.
Built for the **MetaMask Smart Accounts Kit × 1Shot API × Venice AI** hackathon — *Best A2A Coordination* track. Everything runs live on Base mainnet (chainId 8453) and has been executed end-to-end: real USDC in, real wstETH back in the user's wallet.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hxz-1.gitbook.io/redelegator-finance/inroduction/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
