One call: resolve_compliance(object_id, market). object_id is gtin: plus the 14-digit GTIN; market is the hub market code (AE, AU, BE, BR, CA, CH, DE, ES, EU, FR, UK, IN, IT, JP, KR, MX, NL, PL, SG, TH, US, VN; UK is the label for GB). The answer is the current signed record with a state:
greencleared to sell yellowcleared with a condition (the condition is in the record) rednot cleared noneno record exists — nothing is signed at request time
resolve_compliance — the light, as above.get_record — any record ever issued, by record id, byte-identical; earlier ids stay valid.list_rule_sets — the versioned, hashed, signed rule set behind a market (or apex).list_issuers — the signed issuer registry.publish_record — the certifier's seat: an admitted issuer publishes a record it signed with its own key; the only write path. Issuer admission is through consortium-10060.org; records then verify against the issuer's key and are receipted in the ledger.Every record names its issuer and key. GSC records verify from the keyring at https://dpuone.ai/.well-known/jwks.json (kid gsc-rco-2026-08). Partner records verify against the partner's key. The issuer owns the statement; GSC serves and receipts it.
Each market of record serves its rule set as a file at https://<market>.rco-a2a.ai/rule-sets/ (for example eu.rco-a2a.ai). Hostnames of markets outside the list forward here.
Measured availability: status.rco-a2a.ai. Governed access with identity and logging: portal.rco-a2a.ai/mcp (the same records; only the access policy differs).