# glim.sh Twitter Tweet Search

> glim.sh Twitter Tweet Search is a paid API for AI agents from surf.cascade.fyi, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Search Twitter/X for live tweets matching a query, returning tweet IDs and text without requiring Twitter API credentials

## Facts

- Endpoint: POST https://surf.cascade.fyi/api/v1/twitter/tweets/search
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-twitter-tweet-search-fe460d87
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZYHl5vyG1oINtue4R_PKQ

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-tweet-search-fe460d87 -d '<json body>'
```

Example prompt: Search Twitter right now for the latest tweets about 'OpenAI GPT-5' and show me the most recent results — no Twitter API key needed.

## When to prefer this

Use this endpoint when your agent needs live Twitter/X search data without managing Twitter API credentials, OAuth flows, or a scraping infrastructure. Ideal for lightweight, pay-per-call agent workflows that need social media signals on-demand via the x402 micropayment protocol at $0.005 per call.

## Known failure modes

- No matching tweets found — returns empty data array with result_count 0
- Invalid or missing search query — returns 4xx error
- Payment not attached or insufficient — returns HTTP 402 requiring USDC payment
- Rate limiting or downstream Twitter API unavailability — returns 5xx error
- Query too broad returning truncated results with no pagination token

## 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

Returns a JSON object with a 'data' array of tweet objects (each with 'id' and 'text' fields) and a 'meta' object containing 'result_count' indicating how many tweets were returned.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "q"
     ],
     "properties": {
      "q": {
       "type": "string",
       "minLength": 1,
       "description": "Twitter search query with operators"
      },
      "sort": {
       "enum": [
        "Latest",
        "Top"
       ],
       "type": "string",
       "default": "Top",
       "description": "Sort order"
      },
      "limit": {
       "type": "integer",
       "default": 20,
       "maximum": 200,
       "minimum": 1,
       "description": "Maximum tweets to return"
      },
      "cursor": {
       "type": "string",
       "description": "Pagination cursor. Ranking is strongest on page 1 - paged results under sort=Top trend toward recency (upstream behavior)."
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "data",
      "meta"
     ],
     "properties": {
      "data": {
       "type": "array",
       "items": {
        "type": "object",
        "propertyNames": {
         "type": "string"
        },
        "additionalProperties": {}
       }
      },
      "meta": {
       "type": "object",
       "required": [
        "result_count"
       ],
       "properties": {
        "next_cursor": {
         "type": "string"
        },
        "result_count": {
         "type": "integer",
         "maximum": 9007199254740991,
         "minimum": -9007199254740991
        },
        "has_next_page": {
         "type": "boolean"
        }
       }
      },
      "summary": {
       "type": "object",
       "propertyNames": {
        "type": "string"
       },
       "additionalProperties": {}
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "id": "1234567890",
    "text": "Example tweet"
   }
  ],
  "meta": {
   "result_count": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/glim-sh-twitter-tweet-search-fe460d87/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from surf.cascade.fyi](https://www.zero.xyz/host/surf.cascade.fyi/llms.txt)