# LensCrypt Transaction History by Chain and Address

> LensCrypt Transaction History by Chain and Address is a paid API for AI agents from 67olens.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-12).

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

## Facts

- Endpoint: GET https://67olens.vercel.app/api/history/%7Bchain%7D/%7Baddress%7D?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lenscrypt-transaction-history-by-chain-and-address-5f2fd4cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Wc_-2sI-QdfC4p0nLygzD

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-transaction-history-by-chain-and-address-5f2fd4cd
```

Example prompt: Can you pull the full transaction history for wallet address 0x4a3b...f9c2 on Ethereum using LensCrypt?

## When to prefer this

Use this endpoint when you need historical on-chain transaction records for a specific wallet address on a particular chain. Prefer this over general blockchain explorers when you want structured, API-ready data with programmatic access and pay-per-call pricing via x402 USDC. Ideal for building wallet analytics dashboards, auditing DeFi activity, or feeding transaction history into downstream AI analysis pipelines.

## Known failure modes

- Invalid or malformed wallet address returns error response
- Unsupported chain identifier causes lookup failure
- Address with no transaction history may return empty result set
- Payment failure via x402 protocol blocks access to data
- Rate limiting or quota exhaustion returns payment-required error
- Network timeout if blockchain node is slow to respond

## 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 requested chain, including transaction records such as transfers, swaps, contract interactions, and other on-chain activity with associated metadata (timestamps, amounts, counterparties, etc.).

## 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-transaction-history-by-chain-and-address-5f2fd4cd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 67olens.vercel.app](https://www.zero.xyz/host/67olens.vercel.app/llms.txt)