ComplianceCN market-access API docs
Free public beta. ComplianceCN is one market-access readiness workflow for AI agents, seller workflows and cross-border sellers. It has two automated stages: Stage 1 runs automated preflight; Stage 2 runs after Stage 1 and generates the practical next-step pack and official/standardised form drafts. Human evidence review is an optional continuation when judgement is needed.
Machine-readable entry points
- /llms.txt — agent instructions and canonical resources.
- /openapi.json — REST API contract.
- /coze-openapi.json — Coze-compatible plugin import file.
- /.well-known/mcp.json — MCP discovery pointer.
- /.well-known/agents.json — agent discovery card list.
- /.well-known/agent-card.json — single agent/service card.
- /api/consultancy/next-step-pack — editable website/reviewer pack endpoint.
Stage 1: market-access preflight
Use this first when an agent has product facts and target markets and needs to know what usually blocks market entry: applicable rules, missing evidence and review gates. The response also includes suggested_evidence_testing_route: non-binding lab/supplier/reviewer discussion suggestions that must not be presented as additional legal requirements.
curl -X POST "https://compliancecn.netlify.app/api/v1/preflight" \
-H "Content-Type: application/json" \
-d '{"category":"battery-electronics","markets":["EU"],"has_radio":true}'
Stage 2: generate the market-access next-step pack
Use this after Stage 1 preflight when the seller needs something practical to do next. The response selects one of four routes: supplier evidence required, lab/testing route needed, marketplace submission review pack, or specialist referral. It also creates prefillable official or standardised form-field drafts where relevant, such as EU DoC, CPSC CPC, EU food-contact DoC, and cosmetics notification/PIF workflow fields. Suggestions are for preparing conversations with labs, suppliers and reviewers; they are not legal requirements unless supported by the source-linked checklist.
curl -X POST "https://compliancecn.netlify.app/api/v1/next-step-pack" \
-H "Content-Type: application/json" \
-d '{"product_profile":{"product_name":"Bluetooth speaker","category":"battery-electronics","markets":["EU"],"language":"en","has_radio":true}}'
For the interactive website/reviewer version, call the consultancy pack endpoint. It returns editable_fields, chinese_text, english_text, checklist and official_form_drafts for editing and human-review handoff.
curl -X POST "https://compliancecn.netlify.app/api/consultancy/next-step-pack" \
-H "Content-Type: application/json" \
-d '{"product_intake":{"product_name":"Bluetooth speaker","category":"battery-electronics","markets":["EU"],"language":"en","has_radio":true}}'
Optional continuation: human review
Agents should only create a human-review handoff after Stage 1 or Stage 2, with explicit user consent and a valid contact email. Do not upload certificates or test reports through chat; ComplianceCN provides private upload links if the case proceeds.
- /api/consultancy/leads — GET describes the handoff endpoint; POST creates a consenting lead.
- /consultancy.html — human-facing version of the same handoff.
Boundaries
ComplianceCN provides market-access readiness checks using source-linked regulatory data and human review where needed. It is not legal advice, not certification, not product approval, and not a marketplace approval guarantee.