MPPtempoquality 0.75

Pay-per-request TikTok profile data via MPP/x402 — $0.06 per call, no API keys needed.

Price
$0.06 / call
Protocol
mpp
Verified
no

What it does

This endpoint retrieves TikTok user profile information on demand. It is part of StableSocial, a unified pay-per-request social media data API covering TikTok, Instagram, Facebook, and Reddit (36 endpoints total). Every call costs a flat $0.06 USD, settled via USDC on Base, Solana, or Tempo (MPP and x402 protocols supported). No API keys, accounts, or subscriptions are required — payment itself serves as authentication.

The flow is asynchronous: you POST `{"handle": "username"}` to `/api/tiktok/profile` with a payment header. On success you receive a 202 response containing a signed JWT token. You then poll `GET /api/jobs?token=...` (free, but requires SIWX wallet authentication proving you are the paying wallet) until the job status is "finished" and profile data is returned. Jobs typically complete in 5–60 seconds; tokens expire after 30 minutes. If the trigger POST itself fails (e.g. bad parameters), you are not charged.

The TikTok profile endpoint is a prerequisite for several dependent endpoints (posts, followers, following). Data is fetched fresh from TikTok on each request. The full OpenAPI 3.1 spec is published at `https://stablesocial.dev/openapi.json`, and an LLMs.txt file is available for agent discovery.

Capabilities

tiktok-profile-lookupsocial-media-dataasync-job-pollingpay-per-requestmpp-tempox402-paymentsiwx-wallet-authno-api-keypagination-supporton-demand-scraping

Use cases

  • Retrieve TikTok user profile metadata (bio, follower count, etc.) for influencer research
  • Feed TikTok profile data into an AI agent pipeline for social media monitoring
  • Enrich CRM or marketing databases with up-to-date TikTok account information
  • Competitive analysis by programmatically collecting TikTok creator profiles
  • Automated social listening across TikTok as part of a multi-platform workflow

Fit

Best for

  • AI agents needing on-demand social media data without managing API keys
  • Developers who want pay-per-call pricing instead of monthly subscriptions
  • Workflows requiring fresh TikTok profile data fetched at request time
  • Multi-platform social data collection through a single unified API

Not for

  • High-frequency bulk scraping (async polling adds latency per request)
  • Use cases requiring real-time streaming of TikTok data
  • Users who need free or open-access TikTok data without crypto wallet infrastructure

Quick start

# Step 1: Trigger profile fetch (requires MPP/x402 payment header)
curl -X POST https://stablesocial.dev/api/tiktok/profile \
  -H 'Content-Type: application/json' \
  -d '{"handle": "charlidamelio"}'
# → 202 {"token": "eyJ..."}

# Step 2: Poll for results (requires SIWX wallet auth)
curl 'https://stablesocial.dev/api/jobs?token=eyJ...'

Example

Request

{
  "handle": "charlidamelio"
}

Response

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
}

Endpoint

Transporthttp
Protocolmpp
CurrencypathUSD

Quality

0.75/ 1.00

Full OpenAPI 3.1 schema with clear request body definitions, detailed guidance documentation embedded in the spec, and explicit pricing. The endpoint is a POST-only route so the HEAD/GET probe returning 405 is expected and does not indicate a problem. Docked slightly because no example response schema for the actual profile data is provided (only the job token response), and the /docs page returns 404.

Warnings

  • Probe returned 405 because HEAD/GET were used on a POST-only endpoint; the endpoint is likely live but liveness could not be confirmed via 402 challenge
  • No response schema is documented for the actual TikTok profile data payload — only the 202 job token response is specified
  • The /docs page returns 404; all documentation is embedded in the OpenAPI x-guidance field
  • Async two-step flow (POST then poll) requires SIWX wallet auth for polling, adding integration complexity

Citations

Provenance

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

Agent access