# xspy Twitter Username History

> xspy Twitter Username History is a paid API for AI agents from xspy.pro, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-08).

Returns the historical Twitter/X handle changes for a given account, including all previous usernames and the timestamps when each change occurred.

## Facts

- Endpoint: GET https://xspy.pro/api/v1/pro/twitter/%7Busername%7D/username-history
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-08
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/xspy-twitter-username-history-79c38a6d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0Di8HyfmR6sG6ShWS7xYB

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 xspy-twitter-username-history-79c38a6d
```

Example prompt: Can you pull up the full username history for the Twitter account @elonmusk — I want to see every handle they've ever used and when each change happened.

## When to prefer this

Use this endpoint when you need to audit or verify the identity continuity of a Twitter/X account over time — for example, to detect rebrandings, investigate whether a KOL previously operated under a different name, or correlate on-chain activity with historical Twitter handles. Prefer this over manual Twitter profile checks since it provides structured, timestamped history not surfaced in the Twitter UI.

## Known failure modes

- Username not found or account does not exist — likely returns empty history array or 404-style error
- Account with no username changes returns an empty history array
- Invalid or malformed username in path parameter — may return error response
- Payment failure via x402 protocol — endpoint returns 402 Payment Required if USDC payment not completed
- Rate limiting or service unavailability — returns 5xx error

## How this service works

Real-time KOL intelligence, smart follower graphs, and on-chain token signals from tweets. Pay only for the calls you make in USDC on Base or Solana. Agent-ready, no API keys required.

## Output

A JSON object containing a list of historical usernames for the specified account, each with the old handle string and the ISO 8601 timestamp of when the change occurred. Returns HTTP 200 with status true and a data.history array on success.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 200,
  "data": {
   "history": [
    {
     "username": "oldhandle",
     "changedAt": "2025-01-01T00:00:00.000Z"
    }
   ]
  },
  "status": true,
  "message": "success"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/xspy-twitter-username-history-79c38a6d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from xspy.pro](https://www.zero.xyz/host/xspy.pro/llms.txt)