# Meterly.AI Twitter Trends API

> Meterly.AI Twitter Trends API is a paid API for AI agents from meterly-ai.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-14).

Fetches Twitter/X trending topics and trend data based on a search query via pay-per-call USDC payment

## Facts

- Endpoint: POST https://meterly-ai.vercel.app/api/v1/twitter-trends5
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/meterly-ai-twitter-trends-api-208dd9ee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OZw1-fE8jB9Ta-Ke64t6G

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 meterly-ai-twitter-trends-api-208dd9ee -d '<json body>'
```

Example prompt: What's trending on Twitter right now related to artificial intelligence? Give me up to 10 results.

## When to prefer this

Use this endpoint when you need real-time Twitter/X trending topic data for a specific subject area and are operating in an agent context that supports x402 USDC micropayments on Base Mainnet. Prefer this over scraping or manual lookup when you need programmatic, pay-per-call access without a full Twitter API subscription.

## Known failure modes

- Missing required 'query' field returns validation error
- Payment failure on Base Mainnet results in 402 response and no data
- Query returns no trends if topic is not currently trending
- Rate limiting if called too frequently
- Upstream Twitter API unavailability causes service errors

## How this service works

Pay-per-call API infrastructure for AI agents, bots, and developers. Access 95+ premium APIs with USDC payments on Base Mainnet via x402 protocol.

## Output

Returns trending Twitter/X topic data matching the query, potentially including hashtags, trend names, tweet volumes, and related metadata as a JSON object.

## 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": {
      "url": {
       "type": "string",
       "description": "URL to process"
      },
      "limit": {
       "type": "number",
       "description": "Maximum results to return"
      },
      "query": {
       "type": "string",
       "description": "Search query or input data"
      },
      "username": {
       "type": "string",
       "description": "Username or profile identifier"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/meterly-ai-twitter-trends-api-208dd9ee/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from meterly-ai.vercel.app](https://www.zero.xyz/host/meterly-ai.vercel.app/llms.txt)