# X Data Gateway – User Search

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

Search Twitter/X accounts by keyword or phrase and return matching user profiles, paid per-request via USDC.

## Facts

- Endpoint: GET https://x-data-gateway.annushka1190.workers.dev/users/search
- Price: $0.008/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-user-search-38d746c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j5S--eCfT1f5BE_vPSkuV

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-user-search-38d746c0
```

Example prompt: Search Twitter/X for accounts related to 'climate tech' and give me the matching usernames and IDs.

## When to prefer this

Choose this endpoint when you need real-time Twitter/X user search without setting up a Twitter developer account or API key, and you want pay-per-request pricing in USDC. Ideal for AI agents that occasionally need to discover X accounts by keyword without a recurring subscription.

## Known failure modes

- Missing required 'query' parameter returns a 400 error
- Payment not included or insufficient USDC triggers a 402 Payment Required response
- Query returns zero results — empty data array with null next_token
- Rate limiting or upstream Twitter API errors may return 429 or 503
- Invalid or malformed query string may return unexpected empty results

## How this service works

Search public accounts by keyword. e.g. GET /users/search?query=bitcoin

## Output

A JSON array of matching Twitter/X user objects, each containing at minimum a user ID and username, plus a meta object with a next_token for pagination (null if no further results).

## 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": [
      "query"
     ],
     "properties": {
      "query": {
       "type": "string",
       "description": "Keyword"
      }
     }
    }
   },
   "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-user-search-38d746c0/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)