How to use Ledger Agent Intent with your agent

This guide shows you how to set up Ledger Agent Intent with your AI agent and register it with your Ledger signer.

Ledger Agent Intent is designed to help you review and approve, or reject transactions proposed by your AI agent without your agent needing access to your private keys. The agent prepares the request. You approve or reject it with your Ledger signer.

Before you start

Environment

Ledger Agent Intent is available at agent-intent.ledger-test.com .

This is not a sandbox. The intents you approve produce real signatures and real on-chain transactions. Anything you send is irreversible.

What you need

Choose your agent

Ledger Agent Intent is designed for agents that run on their own, away from your machine.

• Recommended: remote, autonomous agents. For example OpenClaw on a VM, Grok Bot, Hermes, or Muse. The agent keeps working when your laptop is closed, which is the behaviour Ledger Agent Intent is built for: the agent proposes at any time, you approve when you are ready.
• Also supported: local, non-autonomous agents. For example Claude Code, Cursor, or Codex. These work, but the agent only proposes while you are at your machine with a session open, so you lose most of the benefit of an approval queue.

What you need to know before you start

An intent is a structured request for an action. The agent creates an intent from the transaction details that you provide. Send intents are supported today. Swap intents and Solana support are in development.

Every agent is identified by a unique identity key pair. The agent’s secrets are designed to remain in its own environment. Before an intent reaches you for approval, the agent authenticates and signs it with its key pair.

A trustchain is a record of registered identities. During registration, the agent public key is added to your Ledger Agent Intent trustchain. Your signer shows the truncated fingerprint of your public key, your “Agent ID”, before you approve it.

The Ledger backend authenticates the agent against its keypair, which is designed to verify that an intent came from an agent that you registered. The agent is not able to register another agent, change the trustchain, sign a transaction, or broadcast one without your approval.

The agent signature is designed to show which registered agent sent the intent. It does not approve the blockchain transaction.

Your Ledger signature gives the final approval. You review the transaction with Clear Signing and Transaction Check before you sign it. The agent cannot complete this action for you.

Stay safe during the beta

Read these before you approve anything.

• Inspect every prompt on your signer before you act. The amount, the recipient and the fees shown on your Ledger signer are what you are signing. The description your agent wrote is text the agent controls and can differ from the transaction itself. If the two disagree, reject.
• Check the agent fingerprint. When you register an agent, compare the Agent ID on your signer with the one your agent gave you in the channel you use to communicate with it, character by character. Approve only on an exact match.
• Check the full recipient address. Your signer shows the address in hex, not as an ENS name. Address poisoning attacks rely on you checking only the first and last characters. Check the whole string.
• Assume your agent can be manipulated. Agents read web pages, documents and messages, and any of those can carry hidden instructions. A compromised agent cannot sign or move funds, but it can propose a transaction that looks reasonable. Your review is the control.
• Never share credentials or payloads. Keep Ledger Sync tokens, JWTs, enrolment secrets and transaction payloads out of tickets, chat, screenshots and screen recordings.
• Register each agent identity once. Do not reuse the same agent key across two Ledger accounts or two seeds.
• Removing an agent takes two steps. This flow is still being developed. Remove the agent in Ledger Agent Intent to stop it sending intents, then remove it from your sync settings in the Ledger Wallet app to remove its account access. Do both.

Step-by-step

1. Ask your agent to use the skill

Send this prompt to your agent:

Read and follow the Agent Intent skill at https://gist.githubusercontent.com/Justkant/fcf812cd95d82a0d651235155d7de77d/raw/SKILL.md . Use its Node 24 CLI to enroll an agent with the app at https://agent-intent.ledger-test.com , keep all credentials private, and return the generated enrollment URL to me.

The skill tells the agent how to install the package, create its identity, and send intents. It also gives the agent the current security rules and supported actions. If the skill is not available, the agent must stop and tell you.

2. Register the agent

The agent will create a key pair and give you a registration link. The link contains only its public key.

1. Open the registration link and sign in with Ledger Sync.

   Ledger Agent Intent uses Ledger Sync to connect the agent identity to you. If you already use Ledger Sync, you can reuse that setup. If not, follow the hand-off to the Ledger Wallet app to enable it, then return to Ledger Agent Intent.

2. Allow the agent to send intents to Ledger Agent Intent.

   The agent can now send new intents to your queue.

3. Connect your Ledger signer and start the registration.

   Your signer shows the truncated fingerprint of your public key, your “Agent ID”. Make sure that it matches the Agent ID from your agent.

4. Approve the agent registration on your Ledger signer.

   This approval links the agent public key to you. It is designed not to give the agent access to your wallet keys.

5. Allow the agent to see your Ledger accounts.

   The agent can create intents based on your portfolio.

3. Review an intent from your agent

1. Continue to use the agent for its assigned role, such as helping with your trading strategy.

   When the agent identifies a relevant transaction to propose, it creates an intent and sends you a review link.

2. Open the review link.

   The request can wait in your Ledger Agent Intent queue until you are ready.

3. Review the transaction details, then approve or reject the transaction.

   Approval requires physical confirmation on your Ledger signer. The agent does not approve the transaction for you.

Your registered agent can now propose intents as part of its role. You keep final approval for every transaction.

What to do next

Your agent is registered. Use it for its normal role and see how the approval flow holds up around it.

A few directions worth exploring:

• Let your agent propose something while you are away from your machine, then approve it from your queue when you come back.
• Reject a proposal, and check that nothing reaches the network.
• Send a small amount between two of your own accounts, then look at how it reads in your history.
• Disconnect your signer, close the tab, or come back the next day, and see whether you land where you expect.
• Register a second agent, and see whether you can tell which one is asking when a request arrives.

Push on the parts that matter for your own integration. If something broke in this setup, or you hit issues when you put Agent Intent in your own product or agent flow, send it in the Agent Intent beta feedback form .

Important legal notice

Ledger Agent Intent is a technology service, accessible via an online web portal, that lets you register an AI agent, set rules governing what it may propose, and review and approve or reject transactions and other actions it proposes, prior to your confirmation.

Ledger Agent Intent is not itself an AI Agent or AI tool: it is the control and approval layer that is designed to sit between you and any AI agent you choose to use. The AI agent used in connection with Ledger Agent Intent is also a third-party tool and is not provided, operated, or endorsed by Ledger.

Ledger Agent Intent is not, and does not constitute, a financial service, brokerage, investment adviser, custodian, or any other regulated financial activity. Ledger does not provide any AI agent nor recommend such AI agent.

Transactions proposed or initiated by an AI agent or associated software are designed to require your review and approval. Ledger does not hold, manage, or have access to user assets at any time. Ledger exercises no control over, and bears no responsibility for, the logic, prompts, financial parameters, or economic outcomes of any AI agent nor for the accuracy, profitability, suitability, or intent of any AI agent. The user is solely responsible for the logic, instructions, financial parameters, and outcomes of any transaction proposed or initiated by an AI agent. Due to the non-deterministic nature of AI models, instructions generated by AI agents may contain errors, inaccuracies, or unintended parameters. Users should independently verify all transaction details before providing their confirmation.

Crypto transaction services referenced or facilitated through Ledger Agent Intent are provided by third-party service providers. Ledger provides no financial advice or recommendations on the use of these third-party services

Use of Ledger Agent Intent does not establish any advisory or fiduciary relationship between the user and Ledger SAS or its affiliates. Ledger Agent Intent is provided “as is,” in early experimental development, without warranty of any kind. Full terms are set out in the Ledger Agent Intent Terms of Use.

Ledger has collaborated with OpenClaw on a technical integration with Ledger Agent Intent. All other third-party agents and tools named above are referenced only to indicate compatibility with Ledger Agent Intent; Ledger has no partnership, affiliation, sponsorship, or endorsement relationship with those products or their providers, and none is implied. All product names and trademarks are the property of their respective owners. Compatibility may change and is not guaranteed.