# glim.sh Twitter Trending Topics by Location

> glim.sh Twitter Trending Topics by Location is a paid API for AI agents from glim.sh, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-08).

Returns live Twitter/X trending topics for a specific geographic location using a Yahoo Where On Earth ID (WOEID)

## Facts

- Endpoint: POST https://glim.sh/api/v1/twitter/users/%7Bref%7D
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-08
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-twitter-trending-topics-by-location-b2151989
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gkFskDR3mD9ZkMAc6ffVj

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 glim-sh-twitter-trending-topics-by-location-b2151989 -d '<json body>'
```

Example prompt: What are the top 20 trending topics on Twitter right now worldwide? Use WOEID 1 for global trends.

## When to prefer this

Use this endpoint when you need live, real-time Twitter/X trending data for a specific geographic location without managing your own Twitter API keys or scraping infrastructure. Ideal for agents that need to monitor what is currently viral or trending on X for any country, city, or worldwide.

## Known failure modes

- Invalid or unsupported WOEID returns empty results or error
- Count exceeding available trends returns fewer results than requested
- Twitter API rate limits or downtime causing 5xx errors
- Invalid {ref} path parameter causing 404 not found
- Payment failure via x402 protocol blocking the request

## How this service works

One remote endpoint gives your agent live data from Twitter, Reddit, the open web, GitHub and more. No API keys, no scraping stack - just connect the URL and go.

## Output

A JSON object with a data array of trending topic entries (each containing id and username or topic identifiers) and a meta object with result_count indicating how many results were returned.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json",
      "form-data",
      "text"
     ]
    },
    "body": {
     "type": "object",
     "properties": {},
     "description": "No body parameters - the user @handle or id is taken from the URL path"
    },
    "pathParams": {
     "type": "object"
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "data": {
       "type": "object",
       "propertyNames": {
        "type": "string"
       },
       "additionalProperties": {}
      }
     },
     "required": [
      "data"
     ]
    }
   },
   "required": [
    "type"
   ]
  }
 },
 "required": [
  "input"
 ]
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": "44196397",
   "username": "cascade_fyi"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/glim-sh-twitter-trending-topics-by-location-b2151989/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from glim.sh](https://www.zero.xyz/host/glim.sh/llms.txt)