# Twitter/X Trends Locations List

> Twitter/X Trends Locations List is a paid API for AI agents from twitter.use.x402atlas.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Returns all geographic locations available for Twitter/X trends, including WOEIDs, place types, country codes, and parent location details.

## Facts

- Endpoint: GET https://twitter.use.x402atlas.com/locations
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-x-trends-locations-list-917dd3fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YZNCqFv8n5A7f4RDK2ASj

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 twitter-x-trends-locations-list-917dd3fc
```

Example prompt: Can you pull the full list of geographic locations available for Twitter/X trends, so I can see all the WOEIDs, place types, and country codes I can use to look up trending topics?

## When to prefer this

Use this endpoint as the first step before querying Twitter/X trends by WOEID — it is the canonical source for discovering which geographic locations and WOEIDs are valid for the trends API. Prefer it when you need to programmatically enumerate all supported regions, validate a WOEID before use, or build a location picker for a trends workflow.

## Known failure modes

- API rate limiting or payment failure returns an HTTP 402 or 429 error
- Twitter/X backend unavailability may return 5xx errors
- The list of supported locations may be incomplete if Twitter has deprecated certain WOEIDs
- Empty or partial location arrays if the upstream Twitter API restricts access

## How this service works

List the geographic locations available for Twitter/X trends, including WOEIDs, place types and country details.

## Output

A JSON object containing a timestamp of when the query was made, the total count of available locations, and an array of location objects each with a WOEID (integer), name, country, country code, place type label, place type code, and parent WOEID.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "locations": [
   {
    "name": "Worldwide",
    "woeid": 1,
    "place_type": "Supername",
    "place_type_code": 19
   },
   {
    "name": "Los Angeles",
    "woeid": 2442047,
    "country": "United States",
    "place_type": "Town",
    "country_code": "US",
    "parent_woeid": 23424977,
    "place_type_code": 7
   }
  ],
  "queried_at": "2026-07-26T12:00:00Z",
  "location_count": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/twitter-x-trends-locations-list-917dd3fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twitter.use.x402atlas.com](https://www.zero.xyz/host/twitter.use.x402atlas.com/llms.txt)