tregWeiboSocial

weibo.post.detail — routed: best of 3 providers, own keys first

treg.weibo.post.detail

One Weibo post by id — the provider's own object in `post`

Price
$0.001/successAt provider cost
Success rate
60%Last 30 days · 5 calls
Latency p50
——
Last verified
—Not verified yet
POSThttps://toolswitch.dev/v1/tools/treg.weibo.post.detailPreview
Try onlineComing soon
  • Uses platform quota
  • Synchronous response
  • Reads public data

Parameters

Send everything you know about the subject — treg derives the rest (full_name ⇄ first+last), matches each provider on the variants it accepts ({post_id}) and sends each provider only the fields it wants. On a miss treg keeps trying providers, cheapest first, within X-Treg-Route-Max-Cost (default $1 per call; misses on per-success providers are free). Options ride as headers, never in the body: X-Treg-Route-Waterfall: 0 (stop at the first miss), X-Treg-Route-Max-Cost: <usd>, X-Treg-Route-Prefer / X-Treg-Route-Exclude: <provider>. The response is {output, raw, _treg: {served_by, tried}}; X-Treg-Served-By names the child.

This tool has no parameters. See provider docs ↗

Code samples

Replace $TOOLSWITCH_KEY with the key you created in the console.

Preview
curl -X POST 'https://toolswitch.dev/v1/tools/treg.weibo.post.detail' \
  -H "X-Toolswitch-Key: $TOOLSWITCH_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"post_id":"…"}'

This gateway API is in preview; its URL and authentication may change. The example parameters are sample data. Calls are billed at $0.001/success, including the service fee.