Search Anchor

Provider operation: GET /api/v1/douyin/xingtu_v2/search_anchor. Supply a keyword and optionally set a page number. Use it to surface relevant records in a search or discovery tool. The GET request schema also lists sort_field. Use the data to compare content across accounts or review audience feedback by video.

Selected price
$0.001 / 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
搜索关键词,可为主播昵称、抖音号、星图ID或直播内容词/Search keyword: nickname, Douyin ID, Xingtu ID or live content word
Optional parameters (28)
页码/Page number
排序字段,默认score综合排序/Sort field, default score (comprehensive)
排序方式,1=升序,2=降序/Sort type, 1=asc, 2=desc
合作对象/Cooperation target
营销目标/Marketing target
适配行业ID/Industry ID
主题推荐达人清单ID/Featured creator list ID
直播报价类型,固定为9;仅与price_min/price_max配合使用/Live-stream price type, fixed to 9
主播报价下限,提供时必须同时提供price_type/Minimum anchor price
主播报价上限,提供时必须同时提供price_type/Maximum anchor price
达人类型ID,多个用逗号分隔,如`1,6`/Creator category IDs, comma-separated
达人人设/学历/认证/调性ID。逗号分隔=满足任一;分号分组=每组都要满足,如`1129,110401;110213`/Persona IDs. Comma=match any, semicolon=group AND
达人性别,1=男,2=女/Creator gender, 1=male, 2=female
粉丝数下限/Minimum followers
粉丝数上限/Maximum followers
预期播放量下限/Minimum expected plays
预期播放量上限/Maximum expected plays
预期CPM下限/Minimum expected CPM
预期CPM上限/Maximum expected CPM
预期CPE下限/Minimum expected CPE
预期CPE上限/Maximum expected CPE
互动率下限,0-1小数,0.02=2%/Minimum interaction rate, 0-1 decimal
互动率上限,0-1小数/Maximum interaction rate, 0-1 decimal
完播率下限,0-1小数/Minimum play-completion rate, 0-1 decimal
完播率上限,0-1小数/Maximum play-completion rate, 0-1 decimal
爆文率下限,0-1小数/Minimum viral-post rate, 0-1 decimal
爆文率上限,0-1小数/Maximum viral-post rate, 0-1 decimal
额外画像筛选的JSON数组字符串,每项必须包含非空字符串field_name和field_value;支持内容主题、观众/粉丝画像、八大人群和地域等维度/Extra profile filters as a JSON-array string; field_name and field_value must be non-empty strings

Sample response

{
  "cache_message": "This response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again.",
  "cache_message_zh": "本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。",
  "cache_url": "<cache_url>",
  "code": 200,
  "data": null,
  "docs": "<docs>",
  "message": "Request successful. This request will incur a charge.",
  "message_zh": "请求成功,本次请求将被计费。",
  "params": {},
  "request_id": "<request_id>",
  "router": "",
  "support": "Discord: https://discord.gg/aMEAS8Xsvz",
  "time": "<time>",
  "time_stamp": 0,
  "time_zone": "America/Los_Angeles"
}

Response result

Response structure

Inferred from examples
  • cache_messagestring
  • cache_message_zhstring
  • cache_urlstring
  • codeinteger
  • datanull
  • docsstring
  • messagestring
  • message_zhstring
  • paramsobject
  • request_idstring
  • routerstring
  • supportstring
  • timestring
  • time_stampinteger
  • time_zonestring

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 Search Anchor with your agent

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