MPPtempoquality 0.72

Fetch TikTok comment replies on-demand for $0.06 per request via pay-per-call API.

Price
$0.06 / call
Protocol
mpp
Verified
no

What it does

This endpoint retrieves replies to a specific TikTok comment. It is part of StableSocial, a pay-per-request social media data API covering TikTok, Instagram, Facebook, and Reddit (36 endpoints total). The endpoint accepts a POST with a JSON body containing the TikTok profile username, post/video ID, and comment ID, plus optional pagination parameters. It costs $0.06 USD per request, settled via USDC on Base, Solana, or Tempo (MPP/x402 protocols). No API keys or signup required — payment serves as authentication.

The API uses an async two-step flow. Step 1: POST to the endpoint with payment to trigger data collection; you receive a 202 response with a signed JWT token. Step 2: Poll GET /api/jobs?token=... (free, but requires SIWX wallet auth) until the job finishes, typically within 5–60 seconds. Tokens expire after 30 minutes. This endpoint depends on prior data collection — you should first trigger profile collection via /api/tiktok/profile, then posts via /api/tiktok/posts, then comments via /api/tiktok/post-comments before fetching comment replies.

Pagination is supported via a cursor field returned in page_info. Each page requires a new paid POST request. Results per page default to 50 and can be adjusted with max_page_size. If the trigger request itself fails (bad parameters, entity not found), you are not charged — payment only settles on 2xx responses.

Capabilities

tiktok-comment-repliessocial-media-dataasync-job-pollingcursor-paginationpay-per-requestno-api-keywallet-authmulti-chain-payment

Use cases

  • Retrieving threaded reply conversations under TikTok video comments for sentiment analysis
  • Monitoring brand mentions and responses in TikTok comment threads
  • Building datasets of TikTok comment discussions for research
  • Analyzing influencer engagement by examining reply depth and frequency
  • Feeding TikTok conversation data into AI agents for social listening

Fit

Best for

  • AI agents needing on-demand TikTok comment reply data without API key management
  • Social media researchers collecting threaded conversation data
  • Brand monitoring tools that need to drill into comment reply threads
  • Developers who want a unified social API without per-platform signup

Not for

  • High-frequency bulk scraping where per-request costs add up quickly
  • Use cases requiring real-time streaming of new replies as they appear
  • Scenarios where you only need top-level comments (use /api/tiktok/post-comments instead)

Quick start

# Step 1: Trigger (paid POST)
curl -X POST https://stablesocial.dev/api/tiktok/comment-replies \
  -H 'Content-Type: application/json' \
  -d '{"profile_id": "username", "post_id": "7123456789", "comment_id": "987654321"}'
# Returns 202 {"token": "eyJ..."}

# Step 2: Poll (free, SIWX wallet auth required)
curl 'https://stablesocial.dev/api/jobs?token=eyJ...' \
  -H 'SIGN-IN-WITH-X: <wallet-signature>'

Example

Request

{
  "post_id": "7234567890123456789",
  "comment_id": "7234567890123456000",
  "profile_id": "charlidamelio",
  "max_page_size": 50
}

Response

{
  "data": {
    "replies": [
      {
        "id": "7234567890123457001",
        "text": "totally agree!",
        "likes": 42,
        "author": "user123",
        "created_at": "2024-01-15T12:34:56Z"
      }
    ],
    "page_info": {
      "cursor": "abc123cursor",
      "has_next_page": true
    }
  },
  "status": "finished"
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.72/ 1.00

Full OpenAPI schema with clear request parameters, detailed guidance documentation, and explicit pricing. The 402 challenge was not captured because the endpoint only accepts POST (HEAD/GET returned 405), but the OpenAPI x-payment-info confirms it is live and priced. Response schema is not documented — the example_response_json is inferred from the guidance docs' generic pattern.

Warnings

  • Probe returned 405 on HEAD/GET because this endpoint only accepts POST — this is expected, not a failure.
  • Response schema is not formally documented in the OpenAPI spec; the example response is inferred from the guidance documentation's generic job-polling pattern.
  • This endpoint has a dependency chain: you must first collect profile, posts, and post-comments data before fetching comment replies.
  • No dedicated docs page exists (/docs returns 404); all documentation is in the OpenAPI x-guidance field.

Citations

Provenance

Indexed frommpp_dev
Enriched2026-04-19 16:39:12Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access