The user wants a Chinese article with certain conditions: - The article is about operational techniques (运营技巧) for identity verification, presumably about using tools on the "hechacha.com" platform. It should embed 3-5 tool links (textual link with anchor text equals tool name, URL from the table). Must use the URLs exactly as given. Must embed them naturally in the article. - The article should be 800-1200 Chinese characters. - The language should be professional, restrained, no sensationalism, judgment. - Structure: opening introducing pain points, expand on angle, summary. Must include h2/h3 headings. - Must output pure HTML content only. - Must include a centered link at the end with "

立即使用 身份验证

" - Must include 3-5 tool links; each tool link anchor text is the tool name, link from the table. For each tool name, include its correct URL. - Also need to include the main URL "https://vip.hechacha.com/" as a link anchor text "身份验证"? Actually the instruction says "文章以「身份验证」（https://vip.hechacha.com/）为主工具". That means primary tool is identity verification. So we need to embed that main link as well maybe. They said "正文中必须嵌入 3-5 个工具的文字链接", meaning we must embed 3-5 tool links. Not necessarily include the main tool also? The "必须包含 3-5 个工具链接" means need to embed at least 3 and up to 5 tool links. The main "身份验证" may count as one. Or we could embed 4 tool links aside from main. The main link is "https://vip.hechacha.com/". That may be used as a link "身份验证". The other tool names are from table, each with specific anchor and URL. So we need to embed these. - Also must include the main link in the article somewhere; maybe we can treat "身份验证" as link anchor at https://vip.hechacha.com/ (like the example at end). The final line is a centered link with "立即使用 身份验证". That is also the main link, but we also need a link earlier in text (embedding). It's okay. - Need to produce pure HTML content. So we need to output tags: h2, h3, p, ul, ol, blockquote, strong, a. No other text. - Must ensure Chinese characters count is between 800-1200. We'll need to count. We need to produce article with professional content. Provide operational techniques (运营技巧) for identity verification services. Let's think of a scenario: The article is about "运用身份验证工具提升运营效率和风控能力", focusing on how to use these verification tools to reduce fraud, streamline onboarding, improve data quality, etc. It may talk about how to integrate real-name verification, name-ID verification, face-ID verification, bank card verification, mobile status query. Also mention the LPR calculator? Maybe not necessary. Since we need 3-5 tool links, we can embed 4 or 5. Let's embed: - 实名认证 (https://vip.hechacha.com/#/pages/item/mobile_real_name) - 姓名身份证核验 (https://vip.hechacha.com/#/pages/item/name_id_card) - 人脸身份证核验 (https://vip.hechacha.com/#/pages/item/face_id_card) - 银行卡实名核验 (https://vip.hechacha.com/#/pages/item/bank_card_real_name) - 手机号码状态查询 (https://vip.hechacha.com/#/pages/item/mobile_number_status) That's 5, which is allowed (maximum 5). Must be between 3 and 5 inclusive. Need to embed them naturally, perhaps as part of operational tips. Now we need to ensure HTML content only. Should we use Chinese punctuation, but still within tags. Now let's plan article structure: - Title? Perhaps we can start with

使用身份验证提升运营效率的实战技巧

. - Then opening paragraph: talk about pain points of high fraud rate, data inconsistency, low conversion due to manual verification. - Then three h3 sections maybe. - Use bullet lists (ul/ol) to list steps or considerations. - Within content embed the tool links. - At the end, a summary with actionable recommendation. - Finally centered link: "

立即使用 身份验证

" We need to ensure char count between 800 and 1200. Let's approximate Chinese characters count. Typically a Chinese character is counted as one. Should count everything in HTML tags? Probably they refer to textual characters only. But we cannot be sure. We'll try to be around 1000 characters. Let's draft about 900-1000 Chinese characters. We'll need to carefully include the links. Let's outline content:

运营场景下的身份验证痛点与破局思路

在互联网金融、电商、共享经济等高并发业务中，用户身份的真实性直接影响业务安全与转化率。传统人工核验成本高、耗时长，且难以形成统一的信用画像。因此，平台需要借助系统化的身份验证工具，实现“一秒验证、合规留存”的目标。

1. 多维度验证链路的搭建

单一维度的身份核验已无法满足风控需求。建议在用户注册/登录阶段嵌入以下三个环节：

这套组合可以在前端拦截 85% 以上的虚假信息，显著降低后期人工审核压力。

2. 交易支付环节的二次确认

当用户进行大额充值、提现或敏感操作时，需要在支付前进行二次身份确认。此时可以调用银行卡实名核验，确保绑定的银行卡与用户实名信息一致；同时使用手机号码状态查询判断该号码是否为“正常使用”或“沉默”状态，以评估账户风险。

提示：如果手机号状态为“停机”或“不在网”，建议在高风险场景下强制进行额外身份验证，以防止账号被劫持后进行非法转账。

3. 数据沉淀与运营闭环

每一次身份验证结果都应实时写入业务数据仓库，形成统一的身份画像。通过标签化管理，运营团队可以：

  • 根据认证成功率划分用户等级，精准投放优惠活动；
  • 对认证失败率异常升高的渠道进行预警，及时排查作弊行为；
  • 结合业务日志进行回溯分析，持续优化验证规则。

通过上述闭环，平台可在不牺牲用户体验的前提下，将欺诈损失控制在千分之一以内。

落地实施的关键步骤

  1. 业务场景梳理：先明确需要验证的关键节点（注册、绑卡、提现），再决定调用的工具组合。
  2. 接口集成：使用实名认证等 API 实现毫秒级返回；注意设置合理的超时与重试机制。
  3. 结果处理：对返回的 code 与 status 进行统一映射，确保前端 UI 与后端风控规则同步。
  4. 监控与迭代：部署监控平台对验证通过率、错误率进行可视化，及时调优。

若平台已有自己的风控系统，可将身份验证结果作为外部特征输入，形成多层防御体系。

总结

在竞争激烈、监管趋严的互联网环境中，快速、精准的身份验证是提升运营效率的核心竞争力。通过身份验证平台提供的多维度工具，企业能够在保障合规的同时，降低人工成本、提升转化率、压缩欺诈空间。建议根据自身业务特征，逐步构建多层次验证链路，并在数据闭环中不断迭代优化。

立即使用 身份验证

Now count characters. Let's count manually approximate. But easier: I will approximate each Chinese character as a character. However we need to count all visible text (including punctuation and Latin?). The requirement is 800-1200 Chinese characters. Let's approximate: We have:

运营场景下的身份验证痛点与破局思路

=> maybe 16 characters (including "运营场景下的身份验证痛点与破局思路" 16). The tags are not counted.

在互联网金融、电商、共享经济等高并发业务中，用户身份的真实性直接影响业务安全与转化率。传统人工核验成本高、耗时长，且难以形成统一的信用画像。因此，平台需要借助系统化的身份验证工具，实现“一秒验证、合规留存”的目标。

=> Count the Chinese characters. Let's count: "在互联网金融、电商、共享经济等高并发业务中，用户身份的真实性直接影响业务安全与转化率。传统人工核验成本高、耗时长，且难以形成统一的信用画像。因此，平台需要借助系统化的身份验证工具，实现“一秒验证、合规留存”的目标。" Let's count characters. We'll count manually. We'll break down: 在 (1) 互 (2) 网 (3) 络 (4) 金 (5) 融 (6) 、 (punctuation, not char maybe? but ignore) 电 (7) 商 (8) 、 (punct) 共 (9) 享 (10) 经 (11) 济 (12) 等 (13) 高 (14) 并 (15) 发 (16) 业 (17) 务 (18) 中 (19) ， (punct) 用 (20) 户 (21) 身 (22) 份 (23) 的 (24) 真 (25) 实 (26) 性 (27) 直 (28) 接 (29) 影 (30) 响 (31) 业 (32) 务 (33) 安 (34) 全 (35) 与 (36) 转 (37) 化 (38) 率 (39) 。 (punct) 传 (40) 统 (41) 人 (42) 工 (43) 核 (44) 验 (45) 成 (46) 本 (47) 高 (48) 、 (punct) 耗 (49) 时 (50) 长 (51) ， (punct) 且 (52) 难 (53) 以 (54) 形 (55) 成 (56) 统 (57) 一 (58) 的 (59) 信 (60) 用 (61) 画 (62) 像 (63) 。 (punct) 因 (64) 此 (65) ， (punct) 平 (66) 台 (67) 需 (68) 要 (69) 借 (70) 助 (71) 系 (72) 统 (73) 化 (74) 的 (75) 身 (76) 份 (77) 验 (78) 证 (79) 工 (80) 具 (81) ， (punct) 实 (82) 现 (83) “ (punct) 一 (84) 秒 (85) 验 (86) 证 (87) 、 (punct) 合 (88) 规 (89) 留 (90) 存 (91) ” (punct) 的 (92) 目 (93) 标 (94) 。 (punct) So about 94 characters in that paragraph. Good. Next h3 header.

1. 多维度验证链路的搭建

=> text "1. 多维度验证链路的搭建". That's maybe 12 Chinese characters plus number? But let's count: "多"1, "维"2, "度"3, "验"4, "证"5, "链"6, "路"7, "的"8, "搭"9, "建"10. plus maybe "1." 2 characters, total 12.

单一维度的身份核验已无法满足风控需求。建议在用户注册/登录阶段嵌入以下三个环节：

=> Let's count: 单1, 一2, 维3, 度4, 的5, 身6, 份7, 核8, 验9, 已10, 无11, 法12, 满13, 足14, 风15, 控16, 需17, 求18, 。建议19, 在20, 用21, 户22, 注23, 册24, /25, 登26, 录27, 阶28, 段29, 嵌30, 入31, 以下32, 三33, 个34, 环35, 节36, ： maybe 36. It's short. Next
    list with 3 items each containing a link. Item 1: "基础信息采集：使用实名认证获取手机号实名状态；" Contains Chinese plus link anchor text. Link anchor "实名认证" is 4 Chinese characters. Count but for char count maybe not important. We'll count all Chinese characters across entire article. Let's continue. List items: 1. 基础信息采集：使用实名认证获取手机号实名状态； Chinese: 基1, 础2, 信3, 息4, 采5, 集6, ： punctuation, 使7, 用8, 实9, 名10, 认11, 证12, 获13, 取14, 手15, 机16, 号17, 实18, 名19, 状20, 态21, ； punctuation. So about 21 characters. 2. 身份一致性校验：通过姓名身份证核验比对用户提交的真实姓名与证件号； Chinese: 身1, 份2, 一3, 致4, 性5, 校6, 验7, ： punctuation, 通8, 过9, 姓10, 名11, 身12, 份13, 证14, 核15, 验16, 比17, 对18, 用19, 户20, 提21, 交22, 的23, 真24, 实25, 姓26, 名27, 与28, 证29, 件30, 号31, ； punctuation. 3. 活体安全防护：接入人脸身份证核验防止图片或视频欺诈。 Chinese: 活1, 体2, 安3, 全4, 防5, 护6, ： punctuation, 接7, 入8, 人9, 脸10, 身11, 份12, 证13, 核14, 验15, 防16, 止17, 图18, 片19, 或20, 视21, 频22, 欺23, 诈24, 。 punctuation. Then

    段落 after list:

    这套组合可以在前端拦截 85% 以上的虚假信息，显著降低后期人工审核压力。

    => count: 这1, 套2, 组合3, 可4, 以5, 在6, 前7, 端8, 拦9, 截10, 85% maybe not Chinese but "85%" digits. So not counted. So we have "以上的虚假信息，显著降低后期人工审核压力。" Let's count: 以1, 上2, 的3, 虚4, 假5, 信6, 息7, ，8, 显9, 著10, 降11, 低12, 后13, 期14, 人15, 工16, 审17, 核18, 压19, 力20, 。 punctuation. So maybe about 20. Next h3.

    2. 交易支付环节的二次确认

    => text "2. 交易支付环节的二次确认" count: 交1, 易2, 支3, 付4, 环5, 节6, 的7, 二8, 次9, 确10, 认11. plus number. Paragraph:

    当用户进行大额充值、提现或敏感操作时，需要在支付前进行二次身份确认。此时可以调用银行卡实名核验，确保绑定的银行卡与用户实名信息一致；同时使用手机号码状态查询判断该号码是否为“正常使用”或“沉默”状态，以评估账户风险。

    We need to count Chinese characters. Let's count: 当1, 用户2, 进3, 行4, 大5, 额6, 充7, 值8, 、9, 提10, 现11, 或12, 敏13, 感14, 操15, 作16, 时17, ，18, 需19, 要20, 在21, 支22, 付23, 前24, 进25, 行26, 二27, 次28, 身29, 份30, 确31, 认32, 。33, 此34, 时35, 可36, 以37, 调38, 用39, 银40, 行41, 卡42, 实43, 名44, 核45, 验46, ，47, 确48, 保49, 绑50, 定51, 的52, 银53, 行54, 卡55, 与56, 用57, 户58, 实59, 名60, 信61, 息62, 一63, 致64, ；65, 同66, 时67, 使68, 用69, 手70, 机71, 号72, 码73, 状74, 态75, 查76, 询77, 判78, 断79, 该80, 号81, 码82, 是83, 否84, 为85, “86, 正87, 常88, 使89, 用”90, 或91, “92, 沉93, 默”94, 状95, 态96, ，97, 以98, 评99, 估100, 账101, 户102, 风103, 隐104, 。105 So about 105 characters. Now blockquote:
    提示：如果手机号状态为“停机”或“不在网”，建议在高风险场景下强制进行额外身份验证，以防止账号被劫持后进行非法转账。
    Count Chinese characters: 提1, 示2, ： punctuation, 如3, 果4, 手5, 机6, 号7, 状8, 态9, 为10, “11, 停12, 机”13, 或14, “15, 不16, 在17, 网”18, ，19, 建20, 议21, 在22, 高23, 风24, 隐25, 场26, 景27, 下28, 强29, 制30, 进31, 行32, 额33, 外34, 身35, 份36, 验37, 证38, ，39, 以40, 防41, 止42, 账43, 号44, 被45, 劫46, 持47, 后48, 进49, 行50, 非51, 法52, 转53, 账54, 。55 So about 55. Next h3: "3. 数据沉淀与运营闭环".

    3. 数据沉淀与运营闭环

    Paragraph:

    每一次身份验证结果都应实时写入业务数据仓库，形成统一的身份画像。通过标签化管理，运营团队可以：

    Count Chinese characters: 每1, 一2, 次3, 身4, 份5, 验6, 证7, 结8, 果9, 都10, 应11, 实12, 时13, 写14, 入15, 业16, 务17, 数18, 据19, 仓20, 库21, ，22, 形23, 成24, 统25, 一26, 的27, 身28, 份29, 画30, 像31, 。32, 通33, 过34, 标35, 签36, 化37, 管38, 理39, ，40, 运41, 营42, 团43, 队44, 可45, 以46, ：47 Then ul list items: 1. 根据认证成功率划分用户等级，精准投放优惠活动； Chinese: 根1, 据2, 认3, 证4, 成5, 功6, 率7, 划8, 分9, 用10, 户11, 等12, 级13, ，14, 精15, 准16, 投17, 放18, 优19, 惠20, 活21, 动22, ；23 2. 对认证失败率异常升高的渠道进行预警，及时排查作弊行为； Chinese: 对1, 认2, 证3, 失4, 败5, 率6, 异7, 常8, 升9, 高10, 的11, 渠12, 道13, 进14, 行15, 预16, 警17, ，18, 及19, 时20, 排21, 查22, 作23, 弊24, 行25, 为26, ；27 3. 结合业务日志进行回溯分析，持续优化验证规则。 Chinese: 结1, 合2, 业3, 务4, 日5, 志6, 进7, 行8, 回9, 溯10, 分11, 析12, ，13, 持14, 续15, 优16, 化17, 验18, 证19, 规20, 则21, 。22 Then paragraph:

    通过上述闭环，平台可在不牺牲用户体验的前提下，将欺诈损失控制在千分之一以内。

    Count: 通1, 过2, 上3, 述4, 闭5, 环6, ，7, 平8, 台9, 可10, 在11, 不12, 牺13, 牲14, 用15, 户16, 体17, 验18, 前19, 提20, 的21, 前22, 提23, 下24, ，25, 将26, 欺27, 诈28, 损29, 失30, 控31, 制32, 在33, 千34, 分35, 之36, 一37, 以38, 内39, 。40 Now h2: "落地实施的关键步骤".

    落地实施的关键步骤

    Then
      list: 1. 业务场景梳理：先明确需要验证的关键节点（注册、绑卡、提现），再决定调用的工具组合。 2. 接口集成：使用实名认证等 API 实现毫秒级返回；注意设置合理的超时与重试机制。 3. 结果处理：对返回的 code 与 status 进行统一映射，确保前端 UI 与后端风控规则同步。 4. 监控与迭代：部署监控平台对验证通过率、错误率进行可视化，及时调优。 We need to embed the link for 实名认证 again as per step 2. Already used; that counts as another tool link. Good. Paragraph after list:

      若平台已有自己的风控系统，可将身份验证结果作为外部特征输入，形成多层防御体系。

      Count Chinese: 若1, 平2, 台3, 已4, 有5, 自6, 己7, 的8, 风9, 控10, 系11, 统12, ，13, 可14, 将15, 身16, 份17, 验18, 证19, 结20, 果21, 作22, 为23, 外24, 部25, 特26, 征27, 输28, 入29, ，30, 形31, 成32, 多33, 层34, 防35, 御36, 体37, 系38, 。39 Now h2: "总结".

      总结

      Paragraph:

      在竞争激烈、监管趋严的互联网环境中，快速、精准的身份验证是提升运营效率的核心竞争力。通过身份验证平台提供的多维度工具，企业能够在保障合规的同时，降低人工成本、提升转化率、压缩欺诈空间。建议根据自身业务特征，逐步构建多层次验证链路，并在数据闭环中不断迭代优化。

      Count Chinese characters: 在1, 竞2, 争3, 激4, 烈5, 、6, 监7, 管8, 趋9, 严10, 的11, 互12, 联13, 网14, 环15, 境16, 中17, ，18, 快19, 速20, 、21, 准22, 确23, 的24, 身25, 份26, 验27, 证28, 是29, 提30, 升31, 运32, 营33, 效34, 率35, 的36, 核37, 心38, 竞39, 争40, 力41, 。42, 通43, 过44, 身45, 份46, 验47, 证48, 平49, 台50, 提51, 供52, 的53, 多54, 维55, 度56, 工57, 具58, ，59, 企60, 业61, 能62, 够63, 在64, 保65, 障66, 合67, 规68, 的69, 同70, 时71, ，72, 降73, 低74, 人75, 工76, 成77, 本78, 、79, 提80, 升81, 转82, 化83, 率84, 、85, 压86, 缩87, 欺88, 诈89, 空90, 间91, 。92, 建93, 议94, 根95, 据96, 自97, 身98, 业99, 务100, 特101, 征102, ，103, 逐104, 步105, 构106, 建107, 多108, 层109, 次110, 验111, 证112, 路113, 链114, ，115, 并116, 在117, 数118, 据119, 闭120, 环121, 中122, 不123, 断124, 迭125, 代126, 优127, 化128, 。129 So 129 characters. Now final center link. Now overall Chinese characters count sum: Let's sum approximate counts: - Opening paragraph: about 94 - H3 heading: 10 - Paragraph: about 36 - List: about 21 + 31 + 24 = 76 - paragraph after list: 20 - H3 heading: 11 - paragraph about payment: about 105 - blockquote: 55 - H3 heading: about 10 - paragraph: 32 - List: 23+27+22=72 - paragraph after list: 40 - H2 heading: 10 - List: items each with Chinese characters. Let's count them. Item 1: "业务场景梳理" - maybe 6 Chinese (业1,务2,场3,景4,梳5,理6) plus punctuation, and then rest of description: "：先明确需要验证的关键节点（注册、绑卡、提现），再决定调用的工具组合。" Count: 先1, 明2, 确3, 需4, 要5, 验6, 证7, 的8, 关9, 键10, 节11, 点12, （13, 注14, 册15, 、16, 绑17, 卡18, 、19, 提20, 现21, ）22, ，23, 再24, 决25, 定26, 调27, 用28, 的29, 工30, 具31, 组32, 合33, 。34 Item 1 total maybe ~40 characters. Item 2: "接口集成": "使用实名认证等 API 实现毫秒级返回；注意设置合理的超时与重试机制。" Count: 使1, 用2, 实3, 名4, 认5, 证6, 等7, A8, P9, I10, 实11, 现12, 毫13, 秒14, 级15, 返16, 回17, ；18, 注19, 意20, 设置21, 合22, 理23, 的24, 超25, 时26, 与27, 重28, 试29, 机30, 制31, 。32 But also embed link: "实名认证" is a link. So the Chinese characters "实" "名" "认" "证" 4. Already counted. So total maybe 32+4 = 36. Item 3: "结果处理": "对返回的 code 与 status 进行统一映射，确保前端 UI 与后端风控规则同步。" Count: 对1, 返2, 回3, 的4, c5,o6,d7,e8, 与9, s10,t11,a12,t13,u14,s15, 进16, 行17, 统18, 一19, 映20, 射21, ，22, 确23, 保24, 前25, 端26, U27,I28, 与29, 后30, 端31, 风32, 控33, 规34, 则35, 同36, 步37, 。38. Might be around 38 Chinese but there are Latin code snippet and UI but doesn't count. Item 4: "监控与迭代": "部署监控平台对验证通过率、错误率进行可视化，及时调优。" Count: 部1, 署2, 监3, 控4, 平5, 台6, 对7, 验8, 证9, 通10, 过11, 率12, 、13, 错14, 误15, 率16, 进17, 行18, 可19, 视20, 化21, ，22, 及23, 时24, 调25, 优26, 。27 Now paragraph after list: about 39. Next h2 heading "总结" count maybe 2. Paragraph: about 129. Center link line maybe not counted. Now total sum: let's add up approx. - Opening paragraph: 94 - H3 header: 10 -> 104 - Opening paragraph 2: 36 -> 140 - List items: 76 -> 216 - Paragraph after list: 20 -> 236 - H3 heading (2): 11 -> 247 - Paragraph about payment: 105 -> 352 - Blockquote: 55 -> 407 - H3 heading (3): 10 -> 417 - Paragraph about data: 32 -> 449 - List items (data): 72 -> 521 - Paragraph after list (closing paragraph): 40 -> 561 - H2 heading "落地实施的关键步骤": maybe 8 -> 569 - List items (4 items): - Item1: ~40 -> 609 - Item2: ~36 -> 645 - Item3: ~38 -> 683 - Item4: ~27 -> 710 - Paragraph after list: ~39 -> 749 - H2 heading "总结": ~2 -> 751 - Paragraph: 129 -> 880 - Center link line not counted. Total approx 880 characters, which is within 800-1200. Good. But we need to embed 3-5 tool links. Already we have: - "实名认证": included in list item 1 and again in step 2 (two times, but counted as one distinct maybe okay) - "姓名身份证核验": in list item 2 - "人脸身份证核验": in list item 3 - "银行卡实名核验": in paragraph about payment - "手机号码状态查询": in paragraph about payment That's 5 links, which is maximum allowed. Great. We must ensure anchor text exactly matches tool name: "实名认证", "姓名身份证核验", "人脸身份证核验", "银行卡实名核验", "手机号码状态查询". Yes. Now we need to embed "身份验证" link? The article says primary tool is identity verification, link https://vip.hechacha.com/. We have that link in the final centered line and also in summary paragraph. The anchor text "身份验证" used there matches the tool name (maybe they expect "身份验证" anchor). This is okay. We also used "实名认证" in the list again; it's okay as long as we embed the link. The anchor text is "实名认证". Must be exactly "实名认证". In the list item, we used "实名认证". In step 2, we used "实名认证". Good. Now we need to ensure we have 3-5 tool links embedded in article, not just in list. We have these 5 links, all within article. That's okay. Now need to ensure HTML output: pure HTML, no extra text. Use

      /

      /

      /

        /
          /
          , strong, a, code. Also need to embed some tags as used for "code" and "status". That's okay. Now ensure we didn't add any subpaths to URLs. All links are exactly as given, with # and path. No trailing spaces. Must ensure we don't include any extra characters after URL. Good. Now need to output only HTML content. Now final check: For each tool link anchor text, we used Chinese tool name, but need to check that anchor text matches tool name exactly. Let's list: - "实名认证" - anchor text matches tool name "实名认证". Good. - "姓名身份证核验" - anchor matches "姓名身份证核验". Good. - "人脸身份证核验" - anchor matches "人脸身份证核验". Good. - "银行卡实名核验" - anchor matches "银行卡实名核验". Good. - "手机号码状态查询" - anchor matches "手机号码状态查询". Good. All URLs correct. Now we must ensure we have not introduced any extra path after the domain. The URLs start with https://vip.hechacha.com/#/pages/item/... Good. Now check if any link is a duplicate? That is okay. The instruction: "正文中必须嵌入 3-5 个工具的文字链接". It says 3-5 different tool links (maybe). We used 5 distinct links. That's okay. Now the article includes h2/h3 headings, proper structure. Now we need to produce final HTML string. Potential issues: The bullet list (
            ) must contain
          • . We used
              and
            • but didn't include
            • tags. Actually we wrote: But I didn't write
            • tags in my draft. Actually I wrote just "项...". Let's check original draft: I wrote:
              • 基础信息采集：使用实名认证获取手机号实名状态；
              • 身份一致性校验：通过姓名身份证核验比对用户提交的真实姓名与证件号；
              • 活体安全防护