Basic
0.032 USDC / report
Registration, operating abnormalities and administrative penalties.
This page explains the Basic sample. Actual field availability varies.
Understand the output before connecting a wallet
What did the supplier check find — and what is still unknown?
For a workflow reviewing a Chinese supplier before onboarding: retrieve company information and recorded-risk modules, preserve their limits, and decide what needs further review.
Entirely fictional. No company was queried and no payment was made. This is a hand-authored explanation of our existing fictional Basic JSON sample, not a real customer case or a live report. The API returns structured data; the review notes below are documentation, not an additional automated assessment feature.
A supplier-onboarding example
Question: “What registration information and recorded issues should my workflow review for this legal entity?” This is narrower than “Can I safely pay this supplier?”
Before a real query: obtain the exact Chinese registered company name or USCC and confirm it refers to the intended entity. A brand, English translation or storefront is not sufficient. This service does not do that mapping for you.
| Observation in this sample | JSON basis | What a buyer or agent should do |
|---|---|---|
| Registration module returned a company-name field. No operating status, licence, address or name/code verification is illustrated. | modules.registration.status = okdata.companyName = 虚构示例企业（不可用于查询） | Treat ok as a module result status, not a verdict that the supplier is legitimate or active. Inspect the actual returned fields; do not invent missing facts. |
| No operating-abnormality records appear in this fictional result. | modules.operating_abnormalities.status = no_records | Say “no records returned by this query,” not “no risk” or “clean company.” Do not infer nationwide completeness or current status. |
| One fictional administrative-penalty placeholder is returned. The example does not provide its date, amount, issuing authority or present legal effect. | modules.administrative_penalties.records[0].description = Fictional record illustrating a list; not a real penalty. | In a real result, review available details and seek missing context before acting. A historical penalty is not automatically present disqualification. Never turn this placeholder into a real allegation. |
| The penalty list may be incomplete. | modules.administrative_penalties.possibly_truncated = truehas_more = null | Preserve the uncertainty. Unknown pagination is not “no more records.” This service does not automatically fetch remaining pages. |
| Six Full-only modules were not requested in this Basic example. | Serious violations, enforcement, dishonesty, bankruptcy, qualifications and customs: not_requested. | Do not display an unqueried module as “passed.” Full adds these modules, but does not remove page, history or coverage limits. |
| This illustration has no real query timestamp. | queried_at = null | Do not call it current evidence. In real output, query time and the underlying records' update time are different concepts. |
A careful summary — not a supplier rating
Fictional worked reading: the Basic sample contains a company-name field, no returned operating-abnormality records, and one penalty placeholder in a potentially truncated list. Six modules were not requested. There is not enough information to determine supplier reliability or payment safety.
Possible workflow use: route a returned record for review, keep its evidence and limits attached, and request the missing context. Your workflow owns this decision. We do not return an automated “approve this supplier” recommendation.
Still outside this check: physical factory existence, production quality or capacity, bank-account ownership, fraud guarantees and a complete legal due-diligence conclusion. A report is a supporting data input, not a substitute for these checks.
Choose the data scope, not a safety score
Full
0.093 USDC / report
Basic plus serious violations, enforcement, dishonesty, bankruptcy, qualifications and customs.
Nine modules, not nine fields. No claim of comprehensive due diligence.
Shared limits
Each list: first page, at most ten records. No automatic history or pagination. Serious violations, enforcement and dishonesty use the current-status option.
Missing or unrequested information is not a clean result.
Check the live quote before authorizing payment. A real purchase requires a compatible x402 payment client, Base USDC and spending approval. Plain MCP discovery does not provide a wallet or buy data. Reading this page or JSON costs nothing and performs no query.
Evaluate first. Integrate only if the output fits.
- Compare the illustrated output and coverage with the fields your workflow needs.
- Confirm the Chinese legal entity; do not turn a guessed English-name match into a purchase.
- Review the integration guide, payment controls and recovery instructions before a real request.
No signup, wallet or payment is required to read the example. This is not an offer of a free live query.
中文说明：买到的是记录，不是“安全保证”
这是完全虚构的 Basic 示例，没有查询真实公司。它演示如何把“查到的记录”“未查的模块”和“未知的覆盖范围”分开。示例中的工商信息只展示名称，不能据此认定企业正常经营；处罚是占位内容，不能用作真实企业证据。
这份页面是对 JSON 的人工编写说明，不代表接口新增了自动风险评分、人工核验或采购建议功能。正式查询仍需准确中文企业名称或统一社会信用代码，且每个列表仅首页、最多十条。看完示例再决定是否值得接入，不必先配置钱包。