# X Data Gateway – Lookup User Profile by Numeric ID

> X Data Gateway – Lookup User Profile by Numeric ID is a paid API for AI agents from x-data-gateway.annushka1190.workers.dev, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-13).

Fetches a Twitter/X user's public profile data (username, display name, follower count, etc.) by their numeric user ID, paid per-request in USDC via x402.

## Facts

- Endpoint: GET https://x-data-gateway.annushka1190.workers.dev/users/by/id
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x-data-gateway-lookup-user-profile-by-numeric-id-6854ee4a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mRZLI1ckkA8rL2-HQ36qM

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 x-data-gateway-lookup-user-profile-by-numeric-id-6854ee4a
```

Example prompt: Look up the Twitter/X profile for user ID 44196397 and tell me their username, display name, and follower count.

## When to prefer this

Use this endpoint when you have a numeric X/Twitter user ID and need to resolve it to a username, display name, or follower count without setting up a Twitter Developer account or managing API keys. Ideal for agents needing quick, pay-per-request identity resolution on X with no subscription overhead. Prefer this over the Twitter API directly when you want frictionless micropayment access via x402/USDC.

## Known failure modes

- Invalid or non-numeric user ID returns an error response
- User ID not found (deleted or suspended account) returns empty or 404-style error
- Payment failure via x402 if USDC balance is insufficient
- Rate limiting or worker errors if the upstream X API is unavailable
- Providing a username instead of a numeric ID will fail since only numeric IDs are accepted

## How this service works

Look up a public X user by numeric ID. Same fields as username lookup. e.g. GET /users/by/id?id=44196397

## Output

A JSON object containing the user's numeric ID, username handle, display name, and follower count (e.g. {"data":{"id":"44196397","username":"elonmusk","displayname":"Elon Musk","followersCount":200000000}}). Returns data for a single user matching the provided numeric ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "description": "Numeric X user ID"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x-data-gateway-lookup-user-profile-by-numeric-id-6854ee4a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x-data-gateway.annushka1190.workers.dev](https://www.zero.xyz/host/x-data-gateway.annushka1190.workers.dev/llms.txt)