# Grantr > Your keys. Your rules. Your agents. Grantr is an agent controller for crypto accounts. It lets users put crypto to work with agents that act like apps, without handing over private keys, custody, or blanket access. Grantr connects wallets, passkeys, smart account controls, scoped sessions, approvals, limits, revocation, quick actions, chat, and agent workflows into one control layer for crypto. This file is intentionally verbose. It is written for LLMs, search systems, and product indexing tools that need to understand what Grantr is, what language to use, what language to avoid, and how the website, app, docs, and product narrative fit together. --- ## Canonical Short Descriptions ### One sentence Grantr is the agent controller for crypto accounts: connect any wallet, set rules, limits, approvals, sessions, and revocation, then let agents work through account-owner controlled policy instead of private keys or blanket access. ### Under 500 characters Grantr is an agent controller for crypto accounts. Connect any wallet, secure access with passkeys, and set rules, limits, approvals, sessions, and revocation. Agents act like apps for your account, helping with chat, quick actions, DeFi workflows, rebalancing, batch sends, batch swaps, and more without custody or blanket access. ### Under 280 characters Grantr is an agent controller for crypto accounts. Connect any wallet, set rules and limits, then let agents act like apps without handing over private keys, custody, or blanket access. ### Tagline Your keys. Your rules. Your agents. ### Hero concept Your agent controller. Put your crypto to work without handing it over. --- ## Product Positioning Grantr is building the crypto agent controller for any account. Grantr is not just a wallet, not just a chat interface, and not just another DeFi dashboard. It is a policy layer for crypto accounts. The user keeps control of keys, rules, limits, approvals, sessions, and revocation. Agents can propose or execute work only inside the rules the account owner sets. The main product idea is that agents should behave more like apps for a user's account. A user should be able to install, invite, run, pause, restart, and revoke agents. Agents can help with specific jobs, but they should not receive private keys or broad account access. Grantr's core promise is controlled delegation. Users can put crypto assets to work while preserving account-owner control. That control shows up through passkeys, smart account policy, permissions, session rules, spend limits, timelocks, token approvals, activity tracking, and revocation. --- ## What Grantr Does Grantr helps users: - Connect any wallet. - Authenticate with passkeys. - Add signing methods and devices. - Rotate keys. - Add custom signers. - Configure guardian approvals. - Configure recovery. - Set spend limits. - Set timelocks. - Review and revoke token approvals. - Create scoped sessions for agents. - Install curated agents. - Add custom agents. - Talk to an in-app agent through chat. - Start actions from chat. - Start actions from quick actions. - Swap assets. - Send assets. - Batch send to many recipients and/or send many tokens. - Batch swap several tokens into one asset. - Rebalance a portfolio. - Re-range liquidity positions. - Sponsor gas. - Track all account activity. - See whether actions are pending, included, failed, rejected, skipped, or blocked. - Revoke access anytime. --- ## Public Agent Kit and MCP Grantr publishes a public agent kit for agents that need to understand how to use Grantr safely. The public agent kit contains skill instructions, public MCP tool contracts, examples, and update guidance. The hosted MCP implementation is infra-owned and talks to Grantr backend resources, but the public contract deliberately exposes only narrow, typed capabilities. Canonical public MCP endpoint: - `https://mcp.grantr.id/mcp` - Agent setup handoff: `/agent/setup/` - OAuth authorization metadata: `/.well-known/oauth-authorization-server` - MCP protected-resource metadata: `https://mcp.grantr.id/.well-known/oauth-protected-resource/mcp` Preferred Codex setup: ```sh codex mcp add grantr --url https://mcp.grantr.id/mcp --oauth-client-id grantr-codex --oauth-resource https://mcp.grantr.id/mcp codex mcp login grantr --scopes grantr.mcp ``` Public framing: - The skill tells agents how to behave around Grantr resources. - MCP exposes safe typed capabilities, not raw backend routes. - Bankr is optional. If a Bankr wallet is present in session context, agents can use it as the active signer or funding wallet. If Bankr is not present, agents should use provider-agnostic wallet context. - Fileverse is available as a document connector for confirmed document workflows such as saving research notes or chat transcripts. - Grantr/Morpho savings workflows are available through discovery, position reads, and unsigned transaction preparation. - If Grantr MCP returns `grantr_account_setup_required`, agents should send the user to `/agent/setup/` and stop private-tool work until the user finishes Grantr account setup. Bankr-originated sessions may pass `source=bankr`, a safe Bankr `returnTo`, and non-secret wallet context so the user can return to Bankr after setup. Codex and other MCP clients should prefer OAuth login; the browser passkey approval issues an authorization code and the MCP client exchanges it for a short-lived bearer token. ### Grantr MCP Tool Groups Capabilities and environment: - `grantr_get_capabilities`: returns MCP version, endpoint, available tools, and safety policy. - `grantr_get_execution_targets`: reads the live Grantr execution targets; backend response is authoritative for visible/default targets. Wallet and portfolio context: - `grantr_resolve_wallet_context`: resolves owner, active wallet provider, active wallet address, and optional Bankr wallet context from session metadata. - `grantr_get_balances`: reads live balances for the context owner wallet. - `grantr_get_portfolio_snapshot`: reads a small live portfolio snapshot without polling. Savings: - `grantr_list_savings_opportunities`: discovers live Grantr/Morpho savings opportunities. - `grantr_get_savings_positions`: reads current Grantr/Morpho savings positions for the context owner. - `grantr_prepare_savings_deposit`: prepares unsigned approval/deposit transactions for a live savings opportunity. - `grantr_prepare_savings_withdraw`: prepares unsigned withdraw/redeem transactions for a live savings position. - `grantr_get_transaction_receipt`: reads a Morpho transaction receipt by hash and chain. Bankr interoperability: - `grantr_get_bankr_wallet`: inspects linked Bankr wallet status for the context owner. - `grantr_link_bankr_wallet`: completes a Grantr-issued Bankr link session after explicit owner authorization. Raw Bankr API keys are not accepted. Fileverse documents: - `grantr_get_fileverse_connector`: inspects Fileverse connector status for the context owner. - `grantr_list_fileverse_documents`: lists Fileverse documents available to the Grantr account. - `grantr_get_fileverse_document`: reads one Fileverse document available to the Grantr account. - `grantr_create_fileverse_document`: creates a Fileverse document after confirmation and secret redaction checks. - `grantr_update_fileverse_document`: updates a Fileverse document after confirmation and secret redaction checks. - `grantr_share_fileverse_document`: shares a Fileverse document with a recipient EVM address after explicit confirmation. - `grantr_import_fileverse_document_to_bankr`: imports a selected Fileverse document into Bankr files when Bankr is linked. ### Grantr MCP Safety Model Grantr MCP is designed for agent-safe access. It must not expose: - Raw backend HTTP proxy access. - API keys, vault secret paths, environment config, or database state. - Arbitrary signing, arbitrary transaction submission, digest signing, private key export, or treasury internals. - Recovery, guardian, device policy, contact mutation, or key rotation by default. - Bankr generic prompt execution as an unconstrained transaction path. - Fileverse backend API keys or raw Fileverse tenant endpoints. - Portfolio/history polling loops or broad Zerion polling. - Fallback balances, mock prices, demo vaults, fake routes, or hardcoded wallet addresses. For financial actions, agents should use this pattern: 1. Discover live opportunities. 2. Inspect wallet context, balances, positions, and execution target. 3. Prepare unsigned transactions. 4. Present summary, risks, approvals, transaction payloads, and expiry. 5. Require explicit user or wallet-provider approval. 6. Sign and broadcast only through the active wallet provider, such as Bankr, WalletConnect, a passkey session, or another supported owner-controlled signer. Example public workflows: - Open a savings position from Bankr: Bankr wallet context -> Grantr MCP savings discovery -> prepare deposit transactions -> present APY, net APY, vault, asset, amount, approvals, deposit transactions, and risks -> Bankr or the active wallet provider signs and submits after approval. - Save research to Fileverse: collect the chat transcript or research findings -> redact secrets and signatures -> ask for confirmation -> create or update a Fileverse document -> optionally import the document into Bankr files when Bankr is linked. --- ## What Grantr Is Grantr is: - An agent controller for crypto accounts. - A smart account control layer. - A passkey-first crypto interface. - A way to let agents work through policy instead of direct key access. - A way to treat agents as apps for a user's account. - A way to connect chat, quick actions, account controls, DeFi workflows, and activity tracking. - A product for controlled agentic DeFi. - A product for users who want agents to research, save, trade, invest, borrow, purchase, rebalance, batch swap, batch send, and stitch workflows together. --- ## What Grantr Is Not Grantr is not: - A custodial wallet. - A product that asks users to hand over private keys. - A product that gives agents blanket account access. - A generic chatbot with crypto features bolted on. - A dashboard that only shows balances. - A workflow tool where approvals are hidden from the account owner. - A product that treats agent access as permanent by default. When describing Grantr, avoid implying that Grantr takes custody, controls user assets directly, replaces the user, hides approvals, or lets agents freely spend without rules. --- ## Core Narrative Crypto accounts are hard to control because accounts, wallets, apps, approvals, agents, gas, and permissions are spread across different surfaces. Grantr turns the account into the policy layer. With Grantr, the user can link any wallet. Agents can act, but every action runs through keys, rules, limits, approvals, and revocation controlled by the account owner. In Grantr, agents are apps for your account to control. Users can choose curated agents or plug in their own. Agents can put crypto to work. Users can track every agent action, set the rules, and revoke access anytime. Users can start from chat or one tap. Rules handle execution. Chat is one entry point. Quick actions and installed agents are others. The same account policy applies either way. --- ## Website Sections ### Above the fold The hero communicates the core offer: - Your agent controller. - Put your crypto to work without handing it over. - Primary CTA: Try the app. - Secondary CTA: Read the docs. The hero should not over-explain. It should make the product feel immediate, controlled, and technical without becoming a marketing essay. ### Problems The website introduces the problem area as "The problems". The problems are grouped around three repeated ideas: - It is hard to control your account. - It is hard to use your crypto. - It is hard to put it to work. Problem examples include: - EOAs: one keypair, forever. - Smart wallets: trapped in an app. - Agents and dapps: the app asks nicely. - Token approvals: sign once, allow forever. - No atomicity: every step, a separate transaction. - Gas: in ETH, or rent a paymaster. - Hot wallets: hand bots your key. - Dapp approvals: sign once, allow forever. - Agent permissions: trust, not enforcement. The section should communicate pressure and friction without adding new copy that changes the user's words unless explicitly requested. ### Solutions The solutions section introduces the constructive turn: - Grantr is building the crypto agent controller for any account. This line can be presented as three lines: - Grantr is building - the agent controller - for any account. The important idea is that Grantr is the controller layer between an account owner and the agents, apps, wallets, and workflows that want to act. ### Account Controls The account controls section says: - With Grantr, your account becomes the policy layer. - Link any wallet. Agents can act, but every action runs through keys, rules, limits, approvals, and revocation controlled by the account owner. Account control chips include: - Add custom signers. - Add devices. - Auto approve. - Guardian approvals. - Revoke token approvals. - Rotate keys. - Spend limits. - Timelocks. The point is not just that users have settings. The point is that account policy controls execution. ### Agents The agents section says: - In Grantr, agents are apps for your account to control. - Choose curated agents or plug in your own. - Agents can put your crypto to work. - Track every agent action. - You set the rules and revoke access anytime. The important framing is "agents as apps", not "agents as owners". Agents can be active, past, restarted, revoked, invited, accepted, curated, or custom. ### Features The features section says: - Start from chat or one tap. Rules handle execution. - Chat is one entry point. - Quick actions and installed agents are others. - The same account policy applies either way. Feature directory: The current website uses an alphabetized feature directory instead of a short chip row. The directory is a broad product map, not a set of separate tabs. Product capabilities are balanced across columns and integrations stay in a separate provider column. Product feature directory: - Address book: all addresses including devices, passkeys, recovery, saved, sent, and signers. - Add devices: bring new devices into the account. - Add signers: connect custom signing addresses. - App connections: pair apps and revoke sessions. - Appearance: custom themes for the app shell. - Auto approve: use 1claw for approval prompts. - Balances: track account assets in one view. - Batch send to multiple recipients: route one transfer flow to many addresses. - Batch send tokens: move several token transfers in one flow. - Batch swap many tokens to one: consolidate several assets into one route. - Daily brief: a readable recap of account signals. - Devices: pair and review trusted devices. - Email recovery: add a recovery email for the account. - Explore: browse markets before taking action. - Guardians: recovery helpers and approval contacts. - Guide: tour every feature in context. - Languages: Chinese, English, Japanese, Korean, Spanish. - Multisig: guarded account signing with 1claw. - Networks: Base, BTC, EVM, SOL, Tron. - Passkeys: owner keys and trusted signing methods. - Positions: monitor LPs, debt, and exposure. - Rebalance: move toward target portfolio weights. - Re-range: adjust liquidity ranges as markets move. - Recovery: contacts and methods for account recovery. - Rotate passkeys: add, replace, and retire passkeys. - Security events: security and app changes in context. - Send: move assets from the controlled account. - Sent: recent recipients stay easy to find. - Signers: wallets and co-signers for actions. - Spend limits: cap movement before execution. - Sponsored gas: let account rules handle gas paths. - Swap: token-to-token trading from Grantr. - Timelocks: delay sensitive account actions. - Token approvals: review and revoke allowances. - Tokenized markets: trade tokens, stocks, commodities, and ETFs. - Transactions: a clean ledger for money movement. - Watchlist: save markets to follow. Integration feature directory: - 1claw: signer and policy infrastructure. - Bankr chat: ask Bankr to check, explain, and act. - CowSwap: solver routing for swaps. - Fileverse docs: create and edit encrypted documents. - Uniswap: markets, swaps, and positions. - Xiaomi cloud: connected device surface. - Zerion: wallet and portfolio data. ### Docs The docs page explains how the app works. It includes: - Signing in. - Getting around. - Account. - Portfolio. - Agents. - Activity. - Quick Action. - Recovery. The docs are intended to be practical, table-of-contents driven, and product-like rather than fluffy. --- ## App Mental Model Grantr has four top-level tabs: - Account. - Portfolio. - Agents. - Activity. Each tab has a viewer at the top and a control bar under it to switch between states. Most screens have a grid/list toggle that changes layout. A Quick Action button sits beside the tab bar on every screen. The Quick Action button has two behaviors: - Tap it to start a Swap. - Press and hold it to open the full action menu. --- ## Signing In To create an account: 1. Open the app. 2. Verify an email. 3. Create a passkey on the device. To sign in to an existing account: 1. Open the app. 2. Approve with the passkey already associated with the account. If the user cannot sign, they should start recovery instead of creating a disconnected account. --- ## Account Tab The Account tab opens on Security and switches between: - Security. - Contacts. - Settings. ### Security Security shows the user's identity and a set of mechanisms, each as a tile. Security mechanisms include: - Signer: shows what can sign for the account. Users can add a custom signer or rotate a key. - Guardian: shows or changes who can help approve recovery. - Keys: shows and manages credentials allowed to authorize actions. - Recovery: sets or reviews how the account is recovered. - Spend Limit: sets a cap on how much can be spent over a period. - Timelock: sets a delay that holds an action before it executes. - Approvals: reviews token allowances and revokes them. ### Contacts Contacts are saved addresses. Each contact has a kind: - Agent. - Contract. - Guardian. - Key. - Recovery. Contacts can be reused later in Send, Sponsor, and recovery flows instead of pasting an address again. ### Settings Settings include: - Accent: changes the theme color. - Appearance. - Export. - Name. - Privacy. - Quick action: sets what the Quick Action button does on tap. - Sign out. --- ## Portfolio Tab The Portfolio tab switches between: - Balance. - Positions. - Loans. ### Balance Balance lists tokens with their values. Users can swipe a token row left or right to Send or Swap it directly. ### Positions Positions lists liquidity positions. Each position is marked: - In range. - Near. - Out of range. Users can act on positions by swiping the row to Rebalance or Re-range, or by opening the row for detail. ### Explore and Watchlist Explore and Watchlist cover tokens, stocks, commodities, and ETFs. Users can inspect a market, save it to Watchlist, or start a swap from the same market universe. ### Whole Portfolio Rebalance To rebalance the whole portfolio: 1. Start Rebalance. 2. Set or confirm target weights. 3. Review the trades Grantr proposes. 4. Confirm. --- ## Agents Tab The Agents tab switches between: - Active. - Past. - Chat. ### Active and Past Active lists running agents. Past lists ended agents. Opening an agent shows its session, including: - Who the agent is. - What the agent can do. - Its allowance. - Its status. From an agent session, the user can: - Revoke it, which stops it now. - Restart it. ### Adding Agents To add an agent: 1. Choose Add an agent. 2. Create a new invite or accept one. 3. Set the session's rules and allowance. 4. Approve. Curated agents can be installed directly. Users can also add their own agents. ### Chat Chat is a conversation with the in-app agent. The user types what they want in plain language. The agent sets up the matching action within the current session's rules, then asks the user to confirm. --- ## Activity Tab Activity is a single feed of everything the account has done. Activity can be filtered by: - All. - DeFi. - Security. Each activity row names the action and outcome. Possible outcomes include: - Pending. - Included. - Failed. - Rejected. - Skipped. - Blocked. Users can swipe a row to view details or copy them. --- ## Quick Action Menu The Quick Action button starts a Swap when tapped. Pressing and holding opens the full menu. Quick Action menu items include: - Send: transfer one asset to one recipient. - Swap: exchange one token for another, review the route, then confirm. - Batch send: send to many recipients and/or send many tokens. - Batch swap: swap several tokens into one asset. - Sponsor gas: pay for another account's action. For these actions, users pick assets and recipients, choose from Contacts or paste an address, enter amounts, then confirm with a passkey. The result appears in Activity. --- ## Recovery If the user cannot sign, they should start recovery from the sign-in screen. Recovery flow: 1. Identify the account. 2. Complete the recovery route set up for the account, such as guardian approval. 3. Create a new signing method. 4. Return to the same account. To add a new device instead of recovering, users pair it from the account. The new device joins the same account rather than creating a new one. --- ## Typical Action Flow A typical action starts from: - Quick Action. - A swipe on a row. - An agent. - Chat. Then: 1. Grantr shows the action. 2. Grantr shows what the action affects. 3. The user confirms with a passkey, or lets an agent act inside its session. 4. The outcome appears in Activity. --- ## Account Control Glossary ### Passkey A device-based authentication method used to sign in and approve actions without seed phrases or passwords. ### Signer Something allowed to sign for the account. Users can inspect signers, add a custom signer, and rotate keys. ### Device A device connected to the same account. Adding a device should pair into the same account rather than create a separate account. ### Guardian A person or mechanism that can help approve recovery. ### Guardian approval A recovery or security mechanism where guardians help approve a sensitive change. ### Keys Credentials allowed to authorize account actions. ### Recovery The process for regaining access if the user cannot sign. ### Spend limit A policy that caps how much can be spent over a period. ### Timelock A policy that delays an action before execution. ### Token approval An allowance granted to another contract or app. Grantr should help users review and revoke token approvals. ### Session A scoped permission period for an agent. Sessions can include limits, rules, allowances, and revocation. ### Revocation The account owner's ability to stop an agent or revoke access. --- ## Agent Glossary ### Agent Software that can perform or propose work for a user's crypto account, subject to account-owner controlled policy. ### Curated agent An agent users can install directly from Grantr. ### Custom agent An agent the user adds themselves. ### Agent as app Grantr's framing for agents: agents should be installed, scoped, monitored, and revoked like apps for an account. ### Active agent An agent with a running session. ### Past agent An ended agent session. ### Revoke Stop an active agent session now. ### Restart Start a previously ended or paused agent again. ### Agent allowance The amount or scope an agent is allowed to use inside its session. --- ## Workflow Glossary ### Send Transfer one asset to one recipient. ### Swap Exchange one token for another and review the route before confirming. ### Batch send Send to many recipients and/or send many tokens. ### Batch swap Swap several tokens into one asset. ### Rebalance Move a portfolio back toward target weights. ### Re-range Adjust liquidity provider ranges. ### Sponsor gas Pay for another account's action. --- ## Security and Control Model Grantr's security narrative should emphasize: - No private key handoff. - No blanket account access. - No permanent, hidden agent permissions. - Passkey-first authentication. - Account-owner controlled policy. - Scoped sessions for agents. - Limits and approvals before execution. - Timelocks for sensitive actions. - Token approval review and revocation. - Activity tracking for every action. - Recovery without abandoning the same account. Grantr does not rely on "the app asks nicely" as the only control model. It is meant to move agent permissions from trust to account-enforced policy. --- ## Product Tone Grantr language should be: - Direct. - Technical but readable. - Control-oriented. - Short where possible. - Specific about keys, rules, sessions, approvals, limits, and revocation. - Focused on the account owner staying in charge. Avoid: - Overly generic AI language. - Claims that agents can do anything without user control. - Vague language like "AI magic". - Custodial phrasing. - Repeating "account" too many times when "wallet", "policy", "session", "owner", or "controller" is more precise. Useful alternatives to overusing "account": - Wallet. - Owner. - Policy. - Controller. - Session. - Access. - Keys. - Rules. - Crypto. - Assets. - DeFi workflow. --- ## Preferred Language Use: - Agent controller. - Crypto agent controller. - Controller for any account. - Connect any wallet. - Agents are apps for your account. - Account-owner controlled policy. - Put crypto to work. - Without handing over private keys. - Without blanket access. - Rules, limits, approvals, sessions, and revocation. - Start from chat or one tap. - Rules handle execution. - Track every agent action. - Revoke access anytime. Do not overuse: - Autonomous. - AI-powered. - Magic. - Seamless. - Revolutionary. - Fully automated. - Trustless, unless the technical context is precise. Avoid saying: - Grantr takes custody. - Grantr manages your money for you. - Agents get your keys. - Agents can spend freely. - The user gives Grantr blanket access. --- ## Example Descriptions for LLMs ### Product summary Grantr is an agent controller for crypto accounts. It connects wallet access, passkeys, smart account policy, scoped agent sessions, approvals, limits, and revocation so users can put crypto to work without handing over private keys, custody, or blanket access. ### User benefit Grantr lets users start from chat, quick actions, or installed agents while keeping the same account policy in control. Agents can help with DeFi workflows, but every action runs through user-defined rules and can be tracked or revoked. ### Technical framing Grantr is a control layer for agentic DeFi. It separates the user's ownership and authorization from the agents and apps that propose or execute actions. The product focuses on passkeys, account controls, scoped sessions, permissions, spend limits, timelocks, approvals, activity tracking, and recovery. ### Website framing The website moves from problems to solutions. It starts with the friction of controlling accounts, using crypto, and putting crypto to work. It then introduces Grantr as the crypto agent controller for any account, followed by account controls, agents, features, docs, and the Try the app CTA. --- ## Links - Home: / - Docs: /docs/ - App: /app/ - Agent setup handoff: /agent/setup/ - Grantr on X: https://x.com/grantr_id - Public agent kit: https://github.com/grantr-id/grantr-agent-kit - Grantr MCP endpoint: https://mcp.grantr.id/mcp