WeChat Universal Search

Search for universal with the WeChat API. Supply a keyword and optionally set a sort order and a pagination cursor. Use it to surface relevant records in a search or discovery tool. The POST request schema also lists business_type. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.01 / 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
搜索关键词(1-100 字)/Search keyword (1-100 chars)
Optional parameters (6)
垂类字符串键(共 18 个)。**实测有结果**:综合 all / 公众号·服务号·视频号 account / 文章 article / 视频 video / 表情 sticker。其余键(underline / encyclopedia / live_stream / comment / listen / news / photos / book / moments / image / mini_game / weixin_index / ai_search)由微信服务端按账号与地区下发,当前实测恒返回空结果(count=0 + no_more 文案,仍按一次正常调用计费)。当前账号真正可用的 tab 以综合搜索响应里的 categories 为准;传列表外的值直接报错(422)/Vertical key (18 total). **Verified to return data**: all / account / article / video / sticker. The rest (underline / encyclopedia / live_stream / comment / listen / news / photos / book / moments / image / mini_game / weixin_index / ai_search) are gated server-side per account & region and currently always come back empty (count=0 plus a no_more message — still billed as a normal call). Use the `categories` field of an `all` search for the authoritative per-account tab list. Values outside this list are rejected (422)
排序(结果页「排序」下拉,综合与各垂类通用):不限(相关性) default/0 / 最新(发布时间降序) latest/1 / 最热(点赞降序) hot/2,字符串键或整数均可/Sort (result page 'sort' dropdown, common to all verticals): default/0 (relevance) / latest/1 (newest) / hot/2 (most liked); string key or integer
发布时间(结果页「时间」下拉,通用):不限 all/0 / 最近一天 day/1 / 最近七天 week/2 / 最近半年 half_year/3,字符串键或整数均可/Publish time (result page 'time' dropdown, common): all/0 / day/1 / week/2 / half_year/3; string key or integer
首页传 0;翻页请用 cursor(只传 offset 无效,每页都回到第一页)/Pass 0 for the first page; use cursor to paginate (offset alone does not work — it returns the first page every time)
翻页游标:首页留空;翻页时把上一页响应返回的 cursor 原样传回/Pagination cursor: leave empty for the first page; for the next page pass back the cursor returned in the previous response
True=原始搜索响应;False=精简解析结构/True=raw search response; False=simplified parsed structure

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

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