Trustbase rCB Data Schemav1.3 · 2026-09-15

The open data standard for the global recovered carbon black (rCB) industry. Bilingual (zh-CN / en-US). AI-Agent ready. 124 entities across 5 modules, 9 MCP tools, 1 verified-supplier trust scheme.

Verified MCP Endpoint  |  data.json  |  llms.txt
1. Why this schema exists

The recovered carbon black (rCB) industry has no public, structured, machine-readable data source that an AI agent can rely on. Trustbase Lab fills that gap.

Agent-first

Every record carries a stable id, a confidence grade, and a bilingual description block an LLM can read directly.

Bilingual by default

name_en + description.zh + description.en — no Accept-Language negotiation, no translation lag.

Trust as a field

public.verified: bool is the trust infrastructure for AI-driven procurement — agents filter to A-grade suppliers with one call.
2. Versioning policy
3. Top-level structure
{
  "meta":         { /* dataset-level metadata */ },
  "domestic":     [ /* 31 Chinese companies / projects */ ],
  "international":[ /* 25 international companies */ ],
  "vendors":      [ /* 26 equipment vendors */ ],
  "policies":     [ /* 22 policy & regulation records  (v1.3) */ ],
  "techs":        [ /* 20 technical standards        (v1.3) */ ]
}

Total current count: 124 entities as of data_version: 0.8 — companies 82 (domestic 31 / international 25 / vendors 26), policies 22, techs 20.

4. Entity record structure
{
  "id":          "rcb-cn-008",
  "public":      { /* 7 fields, safe to expose */ },
  "gated":       { /* 5-9 fields, detailed; phones desensitised */ },
  "description": { "zh": "...", "en": "..." },
  "as_of":       "2026-06"
}
4.1 public.* — what every consumer sees
FieldTypeNotes
regionstring"中国" / country name
categorystringe.g. "在运", "在建", "国际企业", "设备厂商"
namestringNative-script name (usually Chinese)
name_enstringEnglish / pinyin name — required (P0-7)
statusstringOperational status in native language
locationstringProvince / city / country (companies, vendors)
jurisdictionstringv1.3 — administrative area (policies)
orgstringv1.3 — issuing body (techs)
doc_numberstringv1.3 — regulation / standard number
verifiedboolv1.2: AI trust signal — see §7
4.2 gated.* — detailed facts
BucketFields
Domestic (Chinese)capacity_tire, capacity_rcb, byproducts, process, investment, certification, update, contact, confidence, source
Internationalcapacity_rcb, feedstock, certification, partners, update, confidence, source
Vendorsproducts, capacity, overseas, highlights, as_of, confidence, source
Policies (v1.3)issuer, policy_type, scope, rcb_impact, compliance_deadline, confidence, source
Techs (v1.3)standard_no, issuer, scope, key_specs, applicability, confidence, source
4.3 description.{zh,en} — AI-readable summaries

These are the most important fields for AI agents. They are pre-shaped, structured summaries designed to be fed directly into an LLM prompt without further parsing. Both description.zh and description.en are required (P0-6).

Example (en):
Pyrum Innovations AG status: Operating + Expanding. Located in 德国 Dillingen/Saar. Tire processing capacity: ~10 (10k t/yr). Process: continuous rotary kiln. Certification: ISCC PLUS.
5. Entity ID rules
PrefixBucketCount
rcb-cnChinese domestic31
rcb-glInternational25
rcb-eqEquipment vendors26
rcb-polPolicy & regulation (v1.3)22
rcb-techTechnical standards (v1.3)20

Format: <prefix>-<3-digit-zero-padded-seq>, e.g. rcb-cn-008. The mapping name → id is persisted in id_map.json. Adding a new entity never changes an existing ID. Agents should hard-code IDs, not infer them from names.

6. Confidence levels
GradeMeaningUse case
AGovernment documents / official announcementsProcurement, auto-matching
BCompany self-report / authoritative mediaResearch, market sizing
CUnverified / speculativeTriage only
7. Verified Supplier scheme (v1.2)

This is the AI trust infrastructure of the schema. Agents auto-deciding procurement partners should filter on verified=true or call the MCP tool get_verified_suppliers.

{
  "public": {
    "verified": true,           // bool — AI agent decision signal
    ...
  },
  "gated": {
    "confidence": "A",          // required match for verified=true
    ...
  }
}

Rule: verified=trueconfidence=A. The data steward enforces this in CI.

30
Verified Suppliers
82
Company Entities
36.6%
Verified Coverage

Breakdown: 16 Chinese + 6 international + 8 equipment vendors. The verified count is also surfaced in meta.verified_count (per module).

Full-corpus view (all 5 modules): 124 entities, 63 verified = 50.8% A-grade — policies 17/22 and techs 16/20 are additionally marked verified.

8. i18n / bilingual support
9. MCP integration examples

The schema is the wire format. The MCP server at https://trustbaselab.com/mcp exposes 9 tools: query_companies, get_company, get_verified_suppliers, query_policies, get_policy, query_techs, get_tech, get_price_benchmark, get_database_overview.

9.1 Find verified suppliers (JSON)
curl -X POST https://trustbaselab.com/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc":"2.0","id":1,"method":"tools/call",
    "params":{
      "name":"get_verified_suppliers",
      "arguments":{"language":"en","response_format":"json"}
    }
  }'

Returns a structured object with verified_count, suppliers[] (id / name / name_en / region / location / status / verified / confidence / description / as_of).

9.2 Filter companies by verified status
curl -X POST https://trustbaselab.com/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc":"2.0","id":2,"method":"tools/call",
    "params":{
      "name":"query_companies",
      "arguments":{"region":"international","verified":true,"limit":10}
    }
  }'
9.3 Get one company as JSON
curl -X POST https://trustbaselab.com/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc":"2.0","id":3,"method":"tools/call",
    "params":{
      "name":"get_company",
      "arguments":{"id":"rcb-cn-008","language":"zh","response_format":"json"}
    }
  }'
9.4 Query EU compliance obligations (v1.3)
curl -X POST https://trustbaselab.com/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc":"2.0","id":4,"method":"tools/call",
    "params":{
      "name":"query_policies",
      "arguments":{"region":"欧盟","verified":true,"language":"en"}
    }
  }'

Returns policy records with doc_number, issuer, policy_type, scope, rcb_impact and compliance_deadline.

9.5 Look up an rCB test standard (v1.3)
curl -X POST https://trustbaselab.com/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc":"2.0","id":5,"method":"tools/call",
    "params":{
      "name":"query_techs",
      "arguments":{"keyword":"ASTM","category":"测试标准","language":"en"}
    }
  }'
10. Data sourcing & freshness
11. Changelog
VersionDateChange
v1.32026-09-15Added two top-level modules: policies[] (22 records, prefix rcb-pol) and techs[] (20 records, prefix rcb-tech). Equipment vendors expanded 11 → 26. Added meta.total_records + meta.modules_summary. MCP server v1.2 adds 4 tools (query_policies / get_policy / query_techs / get_tech). Data steward extended to 5 tables + rcb-pol/tech ID patterns.
v1.22026-09-15Added public.verified: bool on every entity (A-confidence mapping). Added meta.verified_scheme + meta.verified_count. Updated P0 data-steward check to enforce verified ⇔ confidence=A.
v1.12026-09-14Bilingual support: description.zh + description.en on every record. public.name_en required. meta.i18n_supported = true.
v1.02026-09-13Initial public schema. 67 entities across three buckets. Stable id per entity with rcb-cn/gl/eq-NNN format.
12. License & citation
Data license: data only for industry reference, cite "Trustbase Lab".
Schema license: CC BY 4.0 — free to implement, attribution required.
MCP server: https://trustbaselab.com/mcp
Contact: business@trustbaselab.com  |  info@trustbaselab.com  |  service@trustbaselab.com
WeChat: zxhjtanhei

When citing this schema in academic or commercial work:

Trustbase Lab. (2026). Trustbase rCB Data Schema v1.3. https://trustbaselab.com/schema
Document version 2026-09-15 · schema v1.3 · data_version 0.8 · 124 entities · 63 verified