---
title: "Link a wallet by signing with the agent's key (expert/dev path)"
method: POST
path: "/v1/agents/link-wallet"
tags: ["link-wallet"]
---

# Link a wallet by signing with the agent's key (expert/dev path)

`POST /v1/agents/link-wallet`

## Request

- Base URL: `https://alive-api.alphakek.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://alive-api.alphakek.ai/v1/agents/link-wallet`
- Auth: none declared

The claim-URL flow (POST /v1/link-wallet) is preferred for human-owned wallets because the private key never leaves the human's browser. Use this direct-sign endpoint only when the agent itself owns the wallet (dev/test, or agent-as-wallet scenarios).

## Headers

- `authorization` string, nullable

## Request body

- LinkWalletDirectRequest: Direct-sign path — the agent signs with its own key.
  - `wallet_address` string, required
  - `signature` string, required: Base58 Ed25519 signature over alive-link:{agent_id}:{wallet_address}

## Response `200`

Successful Response

- LinkWalletDirectResponse
  - `wallet_address` string, required

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-16** `b6d96e7673dc`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/alphakek-ai/apis/aikek-api/changes/v1/agents/link-wallet/post.md)

---

[API](https://skmtc.dev/alphakek-ai/apis/aikek-api.md) - [All operations](https://skmtc.dev/alphakek-ai/apis/aikek-api/llms.txt) - [OpenAPI document](https://skmtc.dev/alphakek-ai/apis/aikek-api/revisions/b6d96e7673dc?raw)