1. Receive the content.
2. Detect per platform - call the Doubaoya API once for each of

   xiaohongshu

   ,

   douyin

   ,

   gongzhonghao

   . If the user doesn't specify platforms, first ask which ones they want; by default, each of the three platforms is billed once.
3. Risk comparison - put the results of each platform side by side in a table: platform / verdict / risk category / matched words / suggestions.
4. Unified rewrite - synthesize all platforms' marketing-context hits, and provide one safe version that can be published on all platforms after revision.

Each platform is an independently billed call. If the user only cares about certain platforms, use

--platforms

to narrow the scope.

• Endpoint:

  POST https://doubaoya.com/api/apis/tool/check-banned-words/call

• Authentication: request header

  Authorization: Bearer $DOUBAOYA_API_KEY

• Request body (once per platform, parameters strictly as follows):

{ "platform": "xiaohongshu", "content": "<content to check>" }

platform

"xiaohongshu"

"douyin"

"gongzhonghao"

• Response envelope:

{
  "success": true,
  "requestId": "req_xxx",
  "data": {
    "source": "contentSafety.sensitiveWords",
    "content": "这款美白神器三天见效，<span class=\"sensitive-word\">全网</span><span class=\"banned-word\">最低</span>价",
    "originalContent": "这款美白神器三天见效，全网最低价",
    "prohibitedWordsType": ["禁用词", "敏感词"],
    "raw": {}
  },
  "error": null
}

success

true

data

false

error.code

error.message

originalContent

content

<span>

banned-word

sensitive-word

industry-banned-word

prohibitedWordsType

prohibitedWordsType

source

raw

🔴 The API does not return the three fields "risk level", "list of matched words", or "replacement suggestions" - don't read fields that don't exist. Extract the matched words from the

<span>

in

content

as described above; provide replacement suggestions yourself based on context.

🔴 Zero hits are still billed (unrelated to the

NO_RESULT

free tier), don't report it as a bug.

• Marketing-context hit → fix: extreme words / efficacy claims / medical terms that fall into selling, promising, or comparative sentences ("全网最低" "三天见效").
• Report only, don't fix: degree adverbs outside marketing context ("最后一步" "第一次" "一定要备份" "完全免费开源" - 最后 / 第一 / 一定 / 完全) and false positives from English substrings (

  Assistant

  hits

  ass

  ). Still list matched words in the comparison table, but the "suggestion" column says "context doesn't constitute an advertising claim, keep as-is". The non-applicable situations listed in Articles 5 and 6 of the 《Guidelines for Law Enforcement on Absolute Advertising Terms》(State Administration for Market Regulation 2023) also fall into this tier: statements of business philosophy / wishes ("顾客第一"), self-comparison within the same brand ("我们最贵的一款"), consumption tips ("最佳食用时间"), national standard grading terms, product names / trademarks / awards that inherently contain extreme words, time- and region-limited facts ("2025 年本市销量第一" - but must be provable).
• Must fix and treated severely: efficacy / returns / effect promises in medical, medical aesthetics, pharmaceuticals, medical devices, health foods, investment and financial management, and education and training ("有效率 100%" "保过" "稳赚"), Article 11 of the Guidelines states these three categories are not minor and do not enjoy first-offense exemption.
• Platform-specific standards the API may not catch: Xiaohongshu throttles exaggerated grass-planting terms (绝绝子 / yyds / 闭眼买), silences and deducts points for off-platform diversion (加 vx / 私信 / 留言扣 1); Douyin judges "exaggerated efficacy expression" as low-quality marketing. If you see these types in the content, even if all three platforms return "no hits", mention it in the "suggestion" column of the comparison table.

• Has hits:

  prohibitedWordsType

  is a non-empty array, or

  content

  differs from

  originalContent

  (either condition holds).
• Definitely no hits: both

  content

  and

  originalContent

  are present (proving the check ran), and neither of the above conditions holds.
• No result obtained: the platform entry has

  error

  , or both

  content

  and

  originalContent

  are missing / null. 🔴 In this case, mark that platform as "check failed" - never fill in "compliant" / "low", don't draw compliance conclusions for the user.

• Platform names in Chinese (小红书 / 抖音 / 公众号).
• The "verdict" column strictly follows the criteria above, choose one of three, don't invent risk levels - the API doesn't return levels.
• When a platform takes the "no result obtained" branch (has

  error

  , or content fields all missing), mark that row's verdict as check failed and include the

  code

  ／which field is missing; 🔴 don't fill in "no hits", and don't fabricate results.
• The "suggestion" column is given by this duck based on context - the API doesn't provide suggestions.
• If all platforms are judged "no hits", still list the comparison table normally, with "no hits" in the verdict column.

1. First output the per-platform risk comparison table, then the all-platform safe rewrite, with no opening or closing remarks.
2. After the script returns JSON, you must parse and fill in the template - never output raw JSON directly.
3. The safe rewrite must satisfy all platforms' standards simultaneously: use the platform with the most hits as the baseline to eliminate words.
4. When a platform fails, output the other platforms' results normally, and note the failure reason for that platform in the comparison table; 🔴 when a platform fails the check, MUST end with the note "该平台未完成检测，别当它通过" (this platform's check is incomplete, don't treat it as passed), don't write that it's ready for all platforms.
5. If all platforms are judged "no hits": state it truthfully in the table, and write "原文已可全平台发布，无需改动" (the original text is already publishable on all platforms, no changes needed) in the safe rewrite section.
6. Never echo

   DOUBAOYA_API_KEY

   .

• PROVIDER_FAILED

  (502) is a temporary upstream hiccup, auto-refunded, just retry, no double charge.
• Content is sent to the Doubaoya backend over HTTPS; the script doesn't persist original text or results locally.