---
title: "Verify Coldkey Signature"
method: POST
path: "/tao/pay/token/verify"
tags: ["General APIs with JWT"]
---

# Verify Coldkey Signature

`POST /tao/pay/token/verify`

## Request

- Base URL: `https://lium.io/api`
- URL: `https://lium.io/api/tao/pay/token/verify`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Bind a coldkey to the CALLER, proven by its signature over an access key from GET /token/generate.

## Request body

- VerifyWalletRequest: POST /token/verify's body. ``stripe_customer_id`` may be omitted; if sent it must be the caller's. ``application_id`` is accepted for the old callers and ignored, like ``app_id`` on /wallet/company/: staging's dashboard sends an id that is not this deployment's, and the binding is always this deployment's app.
  - `coldkey_address` string, required
  - `access_key` string, required
  - `signature` string, required
  - `stripe_customer_id` string, nullable
  - `application_id` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-13** `17de96e3dd55`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/lium/apis/lium-backend-api/changes/tao/pay/token/verify/post.md)

---

[API](https://skmtc.dev/lium/apis/lium-backend-api.md) · [All operations](https://skmtc.dev/lium/apis/lium-backend-api/llms.txt) · [OpenAPI document](https://skmtc.dev/lium/apis/lium-backend-api/revisions/a682d3ef1e07?raw)
