The same engine behind our verification cards, programmatic. Resolve entities, pull US customs trade history, get transparent risk scores, manage monitoring — over REST, or natively inside Claude via MCP.

https://china-verify.lovable.app/api/trpc

Anonymous checks work out of the box. For higher quotas, create an API key in the dashboard (Developers → API keys) and send it as a Bearer token. Keys are prefixed vcn_live_…

curl "https://china-verify.lovable.app/api/trpc/verify.search?input=%7B%22json%22%3A%7B%22query%22%3A%22midea%20group%22%7D%7D" \
  -H "Authorization: Bearer vcn_live_…"

curl "https://china-verify.lovable.app/api/trpc/verify.search?input=%7B%22json%22%3A%7B%22query%22%3A%22midea%20group%22%7D%7D"

{
  "result": {
    "data": {
      "json": {
        "candidates": [
          {
            "name": "Midea Group Co., Ltd.",
            "legalName": "美的集团有限公司",
            "uscc": "91440606722473344C",
            "status": "ACTIVE",
            "address": "Beijiao, Foshan, Guangdong, CN",
            "source": "registry"
          }
        ],
        "live": true,
        "isUrl": false
      }
    }
  }
}

curl -X POST "https://china-verify.lovable.app/api/trpc/verify.runCheck" \
  -H "Content-Type: application/json" \
  -d '{
    "json": {
      "query": "Midea Group Co., Ltd.",
      "entityName": "Midea Group Co., Ltd.",
      "claimsExport": true
    }
  }'

{
  "checkId": 1042,
  "identity": { "name": "Midea Group Co., Ltd.", "status": "ACTIVE" },
  "trade": {
    "totalBols": 11978,
    "firstShipment": "2012-03",
    "lastShipment": "2026-09",
    "topBuyers": [{ "name": "Midea America Corp", "bols": 4210 }]
  },
  "risk": {
    "score": 86,
    "band": "low",
    "reasons": [
      { "signal": "trade_history_depth", "delta": 15,
        "source": "Public trade records · Oct 2026" }
    ]
  }
}

curl "https://china-verify.lovable.app/api/trpc/verify.marketContext?input=%7B%22json%22%3A%7B%22hsCode%22%3A%228516%22%7D%7D"

Prefer a typed client? These endpoints are standard tRPC — point any @trpc/client at the same base URL. See the endpoint reference.

Resolve a supplier name or Alibaba storefront URL to legal-entity candidates with registration status and address.

Run the full L0 verification check: identity resolution, US customs trade history, storefront signals, and the 15-signal risk score. Saves the report and returns a checkId.

Aggregate China → US trade value for an HS code, from UN Comtrade. Aggregates only — no company-level data exists in this source.

Over the limit you get 429 with a Retry-After header. Back off exponentially; don't hammer.

Five tools map 1:1 onto the same connectors as the web app — one data brain, two faces. Click a row for its input schema.

The score is rules-based — no AI. Every report starts at 100; each rule below adds or deducts points, and every deduction on your report names its rule and source. The final score is clamped to 0–100.

Deductions

Bonuses

Bands

Automatic fail

If the registry status is not active (e.g. revoked, cancelled), the score is capped at 20 — automatic fail.

Fail-closed: "not checked"

A rule only fires when its source answered. If a source was unavailable, its group is listed as "not checked" and nothing is added or deducted. Without a confirmed registry identity there is no score at all ("Insufficient data").

Factory vs trader classifier

Signals are summed per side. A margin under 3 points reads "Unclear — mixed signals"; 3–4 is medium confidence, 5+ high. It does not change the score.