# LensCrypt Wallet Transaction History by Chain

> LensCrypt Wallet Transaction History by Chain is a paid API for AI agents from lemscrypt.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Retrieves the on-chain transaction history for a given wallet address on a specified blockchain network

## Facts

- Endpoint: GET https://lemscrypt.vercel.app/api/history/%7Bchain%7D/%7Baddress%7D
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lenscrypt-wallet-transaction-history-by-chain-ee01844b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JwvgM8JjgnzovDKxy1Dt6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability lenscrypt-wallet-transaction-history-by-chain-ee01844b
```

Example prompt: Pull the full transaction history for wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum — I want to see every on-chain move this address has made.

## When to prefer this

Use this endpoint when you need a quick, pay-per-call lookup of on-chain transaction history for a specific wallet address on a supported chain, especially within the LensCrypt ecosystem where you are already using other wallet analytics, smart money tracking, or whale alert endpoints. Prefer this over building your own node queries when you need a managed, aggregated history feed without running your own indexer.

## Known failure modes

- Invalid or malformed wallet address returns an error response
- Unsupported chain identifier results in a 400 or 404 error
- No transaction history found for a new or inactive wallet
- Payment failure via x402 protocol results in a 402 Payment Required response
- Rate limiting or quota exhaustion may return a 429 error
- Node or data provider downtime may cause delayed or failed responses

## How this service works

81 paid REST endpoints covering wallet analytics, DeFi yields, token safety, smart money tracking, whale alerts, sniper detection, GMX perps, Solana tools, protocol stats, gas tracking, DEX quotes, NFT analytics, social signals, and 8 AI-powered endpoints (MiMo V2.5). Pay USDC via x402 protocol on Base.

## Output

Returns a JSON object containing the on-chain transaction history for the specified wallet address on the given chain, including transaction records such as hashes, timestamps, token transfers, and interaction details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "ok"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lenscrypt-wallet-transaction-history-by-chain-ee01844b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lemscrypt.vercel.app](https://www.zero.xyz/host/lemscrypt.vercel.app/llms.txt)