Use case · Supplier identity
Verify a Chinese Supplier Before Your Agent Trusts It
A supplier name is a starting point, not a confirmed legal entity. Use China supplier verification to establish who your agent is dealing with before paying for a deeper report.
Remote MCP is a Streamable HTTP endpoint for client configuration, not a browser search form.
Resolve the legal entity before you buy evidence
Chinese supplier due diligence starts with company identity. A trading name, English translation or shortened name can point to a different business from the legal name on a contract. Even an exact-looking name can have multiple candidates in the configured sources. Chinese vendor verification should preserve that ambiguity, not silently choose the first result.
The Unified Social Credit Code (USCC) is the enterprise identifier used to distinguish the intended legal entity. An 18-character value passing a format check is not, by itself, proof that it belongs to your supplier. Compare the code and legal Chinese name against the intended counterparty.
- Use
resolve_china_companywith a Chinesecompanyname. The free resolver returns identity candidates within configured coverage; it does not accept ausccinput. - If multiple candidates remain, ask the counterparty for its exact legal name and USCC. Do not attach another entity’s awards or regulatory records.
- Pass a confirmed
usccto Basic or Full. Keep the returned linkage state and unknown values in your AI agent’s decision process.
Choose evidence depth for this task
| Tool | Price | When to use it |
|---|---|---|
resolve_china_company | Free | Resolve the company name and inspect ambiguity first; obtain the intended USCC before using paid tools when multiple candidates remain. |
get_china_supplier_evidence_basic | Basic $0.002 USDC | Use Basic for low-cost onboarding screening: company identity, procurement and regulatory summaries, linkage and source scope, without detailed evidence rows. |
get_china_supplier_evidence_full | Full $0.01 USDC | Use Full when approval needs the records behind a summary. Request available evidence rows and preserve provenance; a paid response is not an identity or compliance certification. |
No signup. No API key. No prepaid account. x402 · Base USDC. Paid calls still require a compatible funded wallet and explicit spending authorization.
For Full, include_evidence defaults to true; evidence_limit is an integer from 0 to 100. Available rows depend on source coverage; check evidence_meta rather than assuming completeness.
Example structure, not live facts
Example structure: a reduced excerpt of the public Full request schema, not a company result or a complete API request. No real supplier facts are asserted. Basic/Full accept company or uscc; the free resolver requires company.
{
"type": "object",
"properties": {
"company": {
"type": "string",
"minLength": 2,
"maxLength": 200
},
"uscc": {
"type": "string",
"minLength": 18,
"maxLength": 18,
"pattern": "^[0-9A-Z]{18}$"
}
},
"anyOf": [
{
"required": [
"company"
]
},
{
"required": [
"uscc"
]
}
]
}Static example / not_live_query. This is a schema excerpt or field projection, not a complete success response or evidence of any supplier’s current state.
Inspect the original free static example · Inspect the complete schema
Keep source scope attached to the conclusion
A dataset locator identifies a source dataset; record identifiers and source-file locators, when returned, provide finer traceability. Keep both the evidence and its provenance. A match within configured coverage does not establish nationwide registration completeness or guarantee a supplier’s reliability.
Results are limited to configured official/open datasets and must not be interpreted as nationwide completeness.
Use the existing service
Remote MCP: https://cn-evidence-mcp-public.mikeyang7789.workers.dev/mcp