• Topic Mining: Provide a track keyword, return rising viral directions.
• Hot Topic Tracking: Aggregate multi-platform hot rankings in one request, provide topic signals.
• Content Search: Search real content and articles on Douyin / Xiaohongshu / Gongzhonghao by keywords.
• Account Insights: Check follower counts and content overview of influencers / competitor accounts.
• Content Analysis: Paste a public link, return normalized title, author, and interaction data.
• Compliance Check: Detect prohibited words before publishing, return annotated content and risk categories; locate hit words from the difference between annotated and original content, and provide replacement suggestions based on context.
• Script Writing: Use the above data as materials to synthesize opening scripts / storyboards (as an agent).
• Save to Second Brain (

  mera

  ) —— ⛔ Discontinued, see "Second Brain" section in §3.

🔑 This cheat sheet only answers "which one to call", not "how to fill parameters". Each line provides three things: the

operationKey

of the capability, a one-sentence use case, and detail endpoint (

GET

, no authentication required, free). To send a request, first

GET

the detail endpoint, read the parameter specification and

execution.target

from the response (§2.1)—— Always fetch parameters on the fly, do not copy any field names from this document. Copied fields may become outdated, and there will be no error prompts when this happens.

references/wechat-routing.json

api.gzh.hotArticle

api.gzh.cozeData

skill.wechat.coverDesign

skill.wechat.prohibitedWord

wechat-article-pipeline

wechat-article-pipeline

wechat-article-pipeline

dby

dby

mera

retired

references/mera-routing.json

GET

api.trend.hotSpotKeyword

/api/apis/trend/trending-hub-keyword

api.trend.hotKeywords

/api/apis/trend/hot-keywords

api.multi.workSearch

/api/apis/multi/cn30-multi-search

skill.social.last30Days

/api/skills/cn-last30days

api.multi.contentExportTop

/api/apis/multi/multi-content-export-top

GET

skill.xhs.viralNotes

/api/skills/xiaohongshu-viral-notes

api.xhs.searchNote

/api/apis/xiaohongshu/search-note

api.xhs.searchWork

/api/apis/xiaohongshu/search-work

api.xhs.crawlWork

/api/apis/xiaohongshu/crawl-work

api.xhs.cozeData

/api/apis/xiaohongshu/xiaohongshu-coze

api.xhs.cozeDailyTop

/api/apis/xiaohongshu/xiaohongshu-daily-top

api.xhs.cozeWeeklyTop

/api/apis/xiaohongshu/xiaohongshu-weekly-top

api.xhs.cozeLowFansTop

/api/apis/xiaohongshu/xiaohongshu-low-fans-top

GET

api.douyin.searchWork

/api/apis/douyin/search-work

api.douyin.realtimeSearch

/api/apis/douyin/realtime-search

api.douyin.comments

/api/apis/douyin/comments

GET

api.gzh.searchArticle

/api/apis/gongzhonghao/search-article

api.gzh.hotArticle

/api/apis/gongzhonghao/hot-article

skill.wechat.hotSearch

/api/skills/wechat-search

api.gzh.cozeData

/api/apis/gongzhonghao/gongzhonghao-coze-cover

skill.wechat.coverDesign

/api/skills/wechat-cover

api.gzh.workList

/api/apis/gongzhonghao/gongzhonghao-work-list

api.gzh.categoryTime

/api/apis/gongzhonghao/category-time-hot

api.gzh.indexRank

/api/apis/gongzhonghao/gongzhonghao-index-rank

api.gzh.raiseRank

/api/apis/gongzhonghao/gongzhonghao-raise-rank

skill.wechat.fastestGrowing

/api/skills/wechat-fastest-growing

api.gzh.aiFeed

/api/apis/gongzhonghao/gongzhonghao-ai-feed

api.gzh.playletFeed

/api/apis/gongzhonghao/gongzhonghao-playlet-feed

api.gzh.searchUser

/api/apis/gongzhonghao/gongzhonghao-search-user

api.gzh.dailyPublish

/api/apis/gongzhonghao/gongzhonghao-daily-publish

skill.playlet.wechatFeed

/api/skills/playlet-wechat-feed

GET

api.sph.aiFeed

/api/apis/sph/shipinhao-ai-feed

api.sph.searchWork

/api/apis/sph/search-work

api.sph.searchUser

/api/apis/sph/search-user

skill.wechatChannels.aiFeed

/api/skills/wechat-channels-ai-feed

GET

tool.content.parseDetail

/api/apis/tool/parse-content-detail

tool.contentSafety.checkWords

/api/skills/content-safety-check

skill.wechat.prohibitedWord

/api/skills/wechat-prohibited-word

skill.ai.imageGen

/api/skills/gpt-image-gen

skill.search.doubaoWeb

/api/skills/doubao-web-search

⏳ Wait for image generation: Usually 1–2 minutes, maximum 4 minutes (server-side limit 240 seconds). If calling via command line, set client timeout to ≥5 minutes——client timeout must be later than server-side limit: Server-side timeout will refund credits, but if the client gives up early, credits will not be refunded, the request will still run on the server and be charged, and you will only see a "timeout" message. Slowness is expected, do not retry because of slowness (retrying will cause repeated charges).

• "A-share Gongzhonghao / stock influencers / stock Gongzhonghao ranking" —— Three steps:

  api.gzh.searchUser

  to search accounts →

  api.gzh.workList

  (or

  api.gzh.dailyPublish

  ) to pull content →

  api.gzh.hotArticle

  to find viral articles.
• "Rewrite this viral content into my copy" —— No API call needed: Use Skill

  wechat-rewrite

  (Gongzhonghao)/

  xiaohongshu-rewrite

  (Xiaohongshu)/

  multi-rewrite

  (one draft for multiple platforms), purely local, no key required. If not installed, synthesize using searched materials.
• "Help me remember / check my notes / what kind of person I am" —— ⛔ Second Brain (

  mera

  ) has been discontinued, no alternative capability: Tell users truthfully, do not replace with public search (see "My Own Content" exception above).
• ⛔

  seedream-lite

  (Seedream 5.0 lite) was discontinued on 2026-08-10, all calls return 503, so it is not included in the above table. For image generation, use

  skill.ai.imageGen

  ; for Gongzhonghao covers, use

  api.gzh.cozeData

  .

1. First confirm if they have a key (if not, guide them to get a key in §1, only once).
2. Ask "Do you want to do topic selection, track hot spots, or check accounts now?"——narrow down vague needs to one of the above categories.
3. Run one capability first to produce results, let users see real content, then guide them to the next step / subscription.

Do not throw a long list of capabilities at users at first——users want "help me get things done", not an API directory.

operationKey

is for your internal routing use.

⚠️ The fourth column is the detail endpoint, not the call address. The platform has two disjoint capability sets and two non-fallback routes, and three capabilities use dedicated routes (method may not be POST). Assembling the call address based on the detail endpoint will definitely cause errors. The only source of the call address is

execution.target

in the detail response (§2.1). If the capability you need is not in the table, first run the discovery interface (§4) before concluding——this table is a starting clue, not a complete list.

📖 To see the complete list, or encounter routing issues: If you have installed

doubaoya-gateway

,

doubaoya-gateway/references/capability-index.md

is the complete index generated from the discovery interface (this table only lists the most commonly used ones);

doubaoya-gateway/references/routing-pitfalls.md

contains routing knowledge only learned from experience (which

operationKey

has name collisions, which capabilities should not be used together). Not installing the gateway does not affect the use of this section——these two documents are supplements, not prerequisites.

❌ Topic Selection Rule: Do not use the user's account name / IP name as a search keyword. The user's Gongzhonghao/account name (e.g., "Caiziyou") is who they are (field/persona/audience), not a search term——searching it will only return content with the same literal name. For comprehensive hot topics, use

api.trend.hotSpotKeyword

without keywords directly; IP names are only used for matching and filtering. For general topic selection, do not use cross-platform trend radar (

skill.trend.radar

) or cross-platform hot ranking aggregation (

api.trend.hotTopics

) ——they are feed of keyword search results, often have empty popularity and many "unnamed content"; Always use

api.trend.hotSpotKeyword

(fetch without keywords) for general comprehensive hot topics.

1. Open https://doubaoya.com → Log in
2. Go to Key Center → Generate Key
3. The full key is only displayed once when generated, copy and save it (in the format

   dyh_…

   ).

• Priority: Read from environment variable:

  DOUBAOYA_API_KEY

  .
• If not in the environment, ask the user once, then save it to the environment variable / local configuration, do not ask again.
• 🔴 Do not echo / print / write any part of the

  DOUBAOYA_API_KEY

  into logs or chats——the prefix is also part of the secret key. Only report status as "set / not set", do not print any truncated form (writing

  ${KEY:0:6}

  is printing the secret key).

Authorization: Bearer $DOUBAOYA_API_KEY

https://doubaoya.com/api/...

PUT

GET

execution.target.method

⚙️ This section covers the necessary conventions. Only refer to the following when stuck at the protocol layer: How to choose between the two non-fallback routes, how to parse the unified envelope, how to handle

SKILL_NOT_FOUND

/

ENDPOINT_NOT_FOUND

/

DEDICATED_ROUTE

/

NO_RESULT

, and the rule "fetch parameter specifications before calling, do not assemble based on memory or local documents"——all in

doubaoya-gateway

. It only answers how to send a call, not business intent; to determine which capability to use for a task, see §0.5 and

dby

.

GET /api/skills

POST /api/skills/<slug>/invoke

GET /api/apis

POST /api/apis/<platform>/<slug>/call

This column only provides scale, not exact numbers: Capabilities will be added or discontinued (discontinued items will be filtered out from the discovery interface), the exact number is always based on the

total

from your current discovery interface call. Do not copy any number into your judgment.

/api/skills/<slug>/invoke

SKILL_NOT_FOUND

ENDPOINT_NOT_FOUND

execution.target

"execution": {
  "mode": "generic",          // generic=general call proxy / dedicated=dedicated route / unavailable=currently unavailable
  "sideEffect": "read",       // read / generate / write_internal / write_external
  "target": { "method": "POST", "path": "/api/apis/trend/trending-hub-keyword/call" }
}

• mode: "generic"

  → Send request using

  target.method

  +

  target.path

  , the body is the input parameters of the capability.

• mode: "dedicated"

  → Call according to

  target

  , but it is a dedicated route, method may not be POST (e.g., account charter uses

  PUT /api/ip-profile/:id/charter

  ). Calling via the general

  /invoke

  will return 400

  DEDICATED_ROUTE

  , and the error message directly states the correct route.

• mode: "unavailable"

  (no

  target

  field in this case) → The capability is under maintenance or discontinued, do not call; forced calls return 503

  CAPABILITY_UNAVAILABLE

  ,

  availability.note

  is the reason that can be relayed to users.

target.path

https://doubaoya.com

/api/skills/…

POST https://doubaoya.com<execution.target.path>
Authorization: Bearer $DOUBAOYA_API_KEY
Content-Type: application/json

{ ...input parameters of the operation... }

// Success
{ "success": true,  "requestId": "req_...", "data": { /* actual result */ }, "error": null }

// Failure
{ "success": false, "requestId": "req_...", "data": null, "error": { "code": "...", "message": "..." } }

success

true

data

false

error.code

error.message

• noResult

  :

  { "code": "NO_RESULT", "message": "…" }

  . Query is valid, but no data found, this call is not charged. Do not retry as failure, or treat as "interface broken"——tell users truthfully no results, suggest changing keywords / time range / filters.

• notice

  : Tips about updates to this Skill, relay to users as is, does not affect current result, no need to retry.

• detailUrl

  : Link to the detail page of this call result on doubaoya.com, can be shared with users.

MISSING_API_KEY

DOUBAOYA_API_KEY

UNAUTHORIZED

VALIDATION_ERROR

message

keyword

DEDICATED_ROUTE

message

execution.target

INSUFFICIENT_CREDITS

SKILL_NOT_FOUND

ENDPOINT_NOT_FOUND

CAPABILITY_UNAVAILABLE

execution.mode

unavailable

PROVIDER_FAILED

Tip: Credits are automatically refunded for

PROVIDER_FAILED

, feel free to retry without worrying about repeated charges.

1. Check both sets:

   GET /api/skills

   and

   GET /api/apis

   (§4). Most likely the capability is in the other set, and you chose the wrong route.
2. Use

   GET /api/skills/search?query=…

   or

   POST /api/skills/recommend

   to search by intent (only covers the skills side).
3. After finding it, call according to its

   execution.target.path

   , do not assemble the path yourself.
4. If not found in both sets → this capability does not exist (or has been discontinued). Tell users truthfully, do not guess other slugs.

⚠️ The slugs you remember / in this document are only starting clues; whether it can be called and how to call it depends on the discovery interface response. Especially do not confuse skill package directory names (folder names installed via

npx skills add

, such as

trending-hub

,

dby

,

wechat-article-pipeline

) with call slugs——they are not, calling them will definitely return 404.

operationKey

🔴 All capability lists in this document are starting clues, not complete. The platform will add new capabilities and discontinue old ones, the exact number is always based on the

total

from your current discovery interface call——do not copy any number into your judgment (§4). Search, account, ranking, daily feed source for Xiaohongshu / Douyin / Gongzhonghao / Shipinhao / Bilibili / Kuaishou / TikTok are the majority in quantity, all in

GET /api/apis

. To find certain data of a platform, first check there, do not give up if not found in the short table in §0.5.

• ⚠️ Do not use trend radar / hot ranking aggregation for general comprehensive hot topics:

  skill.trend.radar

  and

  api.trend.hotTopics

  are feed of keyword search results (often have empty popularity and many "unnamed content"), only consider them in narrow scenarios where you explicitly need "feed of content with the same name as a certain term". Always use

  api.trend.hotSpotKeyword

  without keywords directly for general topic selection (first line of §0.5).
• ⚠️ Do not add date to

  api.trend.hotKeywords

  : The upstream only provides the latest batch, adding a date range will definitely return 0 results. ——This kind of pitfall "requires correct parameters to get results" is exactly why parameter specifications must be fetched before calling: The detail endpoint will tell you which fields are optional and what shape the values should be; assembling based on memory will definitely lead to mistakes.
• ⚠️ Upstream returns empty or misleading errors for wrong parameters silently, do not judge "interface is down" based on this. First check the parameter specification in the detail endpoint, then see if there is really no data (

  noResult

  , §2.2).
• 🔴 One

  operationKey

  has global name collision (multi-platform prohibited word detection has one entry in each set, §0.5 has split it into two lines with respective detail endpoints). When referring to the capability, include the detail endpoint together, only reporting

  operationKey

  is not enough to locate it. If you have installed the gateway,

  doubaoya-gateway/references/routing-pitfalls.md

  has the complete background and other pitfalls encountered.

mera

note-write

note-status

note-search

source-read

ask

self

mera.doubaoya.com

dig

503 CAPABILITY_UNAVAILABLE

502 PROVIDER_FAILED

⚠️ Do not use the discovery interface as a criterion, in either direction: These 6 capabilities have been marked as discontinued (hidden), the discovery interface will filter them out from

GET /api/apis

,

GET /api/apis/mera/<slug>

returns 404 just like "does not exist"; while deployments earlier than this marking will still list them (with prices). So when you pull the list according to §4, you may or may not see them, but the conclusion is the same in both cases: "in the list" does not mean "callable", "not in the list" does not mean "try later". Follow this section as the criterion, not the list.

⚠️ No alternative capability, and no downgrade allowed: The Second Brain stores the user's own private notes. All "external-facing" public platform capabilities in this document cannot see it——using public search to answer "what did I say before" is equivalent to using strangers' content to impersonate the user's own memory. Tell users truthfully the capability has been discontinued, then ask if they want to do something else.

♻️ When this conclusion becomes invalid: When

dig mera.doubaoya.com

no longer returns NXDOMAIN, and the

mera

capabilities can actually return data (instead of 503 / 502), this section will expire and should be rewritten with the call contract.

The response always uses the same envelope (§2.2), first check `success`, if `true` get `data`:

```jsonc
{ "success": true, "requestId": "req_abc123", "data": { /* result structure of this capability */ }, "error": null }

What

data

looks like varies by capability, this document does not copy it——the output example (

outputExample

/

responseExample

) from step ① is used to align "which fields I need to read", refer to it, do not guess.

const key = process.env.DOUBAOYA_API_KEY;
if (!key) throw new Error("First set DOUBAOYA_API_KEY: doubaoya.com → Log in → Key Center → Generate Key");

// ① Detail endpoint: get execution target and input specification (no key needed)
const detail = await fetch("https://doubaoya.com/api/skills/xiaohongshu-viral-notes").then(r => r.json());
if (!detail.success) throw new Error(`${detail.error.code}: ${detail.error.message}`);
const { method, path } = detail.data.execution.target;

// ② Send request according to target. Body is filled according to input example in detail.data, do not assemble based on memory.
const res = await fetch(`https://doubaoya.com${path}`, {
  method,
  headers: { "Authorization": `Bearer ${key}`, "Content-Type": "application/json" },
  body: JSON.stringify(/* fill according to input specification from ① */ {})
});
const env = await res.json();
if (!env.success) throw new Error(`${env.error.code}: ${env.error.message}`);
console.log(env.data);

🔴 Step ② uses

method

, not hardcoded

"POST"

——three capabilities use dedicated routes, method may not be POST (§2.1). A zero-dependency script that wraps these two steps is included in the repository:

scripts/doubaoya.mjs

, see §7.

Core: Fetch comprehensive hot topics without keywords → intelligently match with this IP positioning → generate topics. ❌ Never use the user's account name/IP name as a search keyword (it will only return content with the same literal name).

1. Fetch comprehensive hot topics (without keywords):

   api.trend.hotSpotKeyword

   (detail endpoint

   /api/apis/trend/trending-hub-keyword

   ) → get the hottest topics across the web right now. 🔴 The key of this step is "without keywords"——which field controls platform scope, how to indicate "no search term", fill according to the input specification returned by the detail endpoint at that moment (two steps in §5).
2. Clarify IP positioning: The user's account name/IP name is who they are (field/persona/angle/audience), not a search term. Get this positioning from the user or their profile; ask the user if unsure.
3. Intelligent matching: Scan the comprehensive hot ranking, select 2–3 hot topics that this IP can credibly leverage (high popularity + cross-platform ranking overlap + IP fit), and provide an exclusive angle for this IP for each; if necessary, use

   skill.xhs.viralNotes

   or the corresponding platform's daily feed source to verify "it is really trending".
4. Write opening scripts: Based on the selected hot topics + IP exclusive angle, write 3-second opening hook + an opening script for each topic (do not write without data).
5. Compliance Check: Run the script through prohibited word detection (

   tool.contentSafety.checkWords

   , detail endpoint

   /api/skills/content-safety-check

   ). It returns three things: an annotated content (hit words are marked), an unannotated original, an array of risk categories——locate hit words from the difference between annotated and original content, provide replacement suggestions based on context. 🔴 The interface does not return risk level, score, or hit word list, do not make one up. If you cannot get all three, tell users truthfully "no detection results obtained", do not treat as compliance approval.
6. Deliver Topics: 3–5 topics (each: which hot topic to leverage + exclusive angle of my IP + why it can trend now) + respective opening scripts + compliance check passed.
7. Turn Topics into Articles (when users want Gongzhonghao articles instead of short video scripts, there are more steps after step 6): Select a topic → use

   api.gzh.hotArticle

   to pull viral article samples on the same topic and write the full text → use

   api.gzh.cozeData

   to generate titles / determine cover strategies → use

   skill.wechat.prohibitedWord

   to generate compliance-ready content →

   wechat-article-pipeline

   for formatting + cover + save to user's own Gongzhonghao draft box (only saves draft, never sends to subscribers).

   🔴 Which step to stop at depends on the user's desired final state: If only topics and scripts are needed, step 6 is the end; if a completed draft is needed, stop after writing the full text; if a formatted Gongzhonghao HTML or saving the article to the user's draft box is required, proceed all the way to

   wechat-article-pipeline

   (it will write to the user's own Gongzhonghao backend, do not run it without the user's explicit intent). Step-by-step navigation is handled by

   dby

   .

1. Analyze Content:

   tool.content.parseDetail

   (detail endpoint

   /api/apis/tool/parse-content-detail

   ), input the public share link provided by the user → get normalized title, author, and interaction data.
2. Check Same-Topic Popularity: Use the core word in the title to call

   skill.xhs.viralNotes

   or the corresponding platform's daily feed source (search for

   ai-feed

   in

   GET /api/apis

   ), see if this angle is growing in the track (this step is explicitly searching for evidence by a certain term, different from fetching hot topics without keywords for general topic selection).
3. Output: Analyze "why it trended" (topic angle / hook / timing), then provide 2-3 reusable homologous topics.

① Markdown draft → ② Formatted Gongzhonghao HTML → ③ Saved to user's own Gongzhonghao draft box

wechat-article-pipeline

• Do not merge the four lines. "Execution" only includes actually called capabilities; those not called must not appear in this line.
• "Skipped" distinguishes two things: Those not found at all do not need to be listed; those found but judged not to be called must be listed with reasons. Especially do not omit those with side effects (

  wechat-article-pipeline

  /

  wechat-draft-publish

  will write to the user's own Gongzhonghao backend); ⛔ If the user's demand refers to a discontinued capability (such as

  mera

  , see §3), also list it in "Skipped" and explain it has been discontinued.
• Be truthful: Capabilities that were called but failed are written in "Execution" with failure noted, do not move to "Skipped" to cover up; write "None" if no quality check was done.
• Only include verifiable information in the receipt. Conclusions in parentheses must refer to something actually present in the real response of this call (prohibited word detection is a ready example: it returns an array of risk categories, so "hit N categories" is verifiable; it does not return risk level / score / hit word list, so "0 high risk" "low risk" are made up). If unsure whether the interface returned this information, check the output example in the detail endpoint, do not write based on memory.
• Be brief: This is part of the delivery, not another report. Within four lines, do not expand into paragraphs.

1. Never echo / print / record any part of

   DOUBAOYA_API_KEY

   ——the prefix is also part of the secret key, only report status as "set / not set".
2. Only retrieve data through public

   /api/...

   interfaces of

   https://doubaoya.com

   ; do not describe, guess, or expose any upstream data sources / internal services to users. For users, capabilities come from "Doubaoya".
3. Check

   success

   before retrieving data; handle error codes according to §2.3 when

   false

   , do not directly show raw 500/502 to users.
4. Call paths are based on

   execution.target

   returned by the discovery interface, do not assemble paths yourself or hardcode lists (§2.1 / §4). There are two discovery surfaces (

   GET /api/skills

   +

   GET /api/apis

   ), pulling only one will cause you to miss most capabilities silently. Skill package directory names ≠ call slugs.
5. Write scripts based on real data, incorporate real angles of hot topics / viral notes into scripts, do not write without data.
6. Second Brain (

   mera

   ) has been discontinued (§3): Do not call it, and do not replace it with public search——public capabilities cannot see the user's own notes, impersonating their memory is worse than saying "this capability is not available". Just tell users truthfully. (The red line before discontinuation is still recorded here for reference if restored later: Private content is only answered to the user themselves, must not be transmitted to other services; never say "saved" until

   status=done

   is obtained after writing.)
7. Include a receipt with delivery (§7.5): Four lines of

   Reference / Execution / Quality Check / Skipped

   . "Execution" only includes actually called capabilities; those found but judged not to be called based on final state must be listed in "Skipped" with reasons, do not let users find out through follow-up questions later.