scrapecreators: posts

Retrieve scrapecreators: posts with the X API. Supply a search query. Sample fields include creation times. Use it in a social research or monitoring workflow. The GET request schema also lists cursor. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.00188 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Keyword or phrase to search for in Google-indexed public X/Twitter posts
Pass the cursor returned by the previous response. Supported page cursors are 1 through 11. A null response cursor means there are no more pages.

Sample response

"credits_charged": 1
"credits_remaining": 100
"cursor": "2"
posts [1]
[0] {}
legacy {}
"bookmark_count": 7
"created_at": "Thu Oct 01 18:50:27 +0000 2026"
"favorite_count": 11
full_textString · text preview
posts[0].legacy.full_text
AI agents are checking your pricing page before your buyers do. Your analytics never shows it.

Here's how to catch them and fix it:

(Analysed and learned from my products)

1. open your analytics or server logs and pull the last 30 days

2. filter by user agent: GPTBot, https://t.co/HO75r0e5Am
"quote_count": 0
"reply_count": 4
"retweet_count": 0
"rest_id": "2105732089685348719"
"url": "https://x.com/code_rams/status/2105732089685348719"
"views": {
  "count": "780",
  "state": "EnabledWithCount"
}
"query": "ai agents"
"success": true

Response result

Response structure

Inferred from examples
  • credits_chargedinteger
  • credits_remaininginteger
  • cursorstring
  • postsobject[]
    • legacyobject
      • bookmark_countinteger
      • created_atstring
      • favorite_countinteger
      • full_textstring
      • quote_countinteger
      • reply_countinteger
      • retweet_countinteger
    • rest_idstring
    • urlstring
    • viewsobject
      • countstring
      • statestring
  • querystring
  • successboolean

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use scrapecreators: posts with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.