Knowledge Domain · Data Integration

Data Integration Knowledge Retrieval

Data-integration knowledge lives in the data-integration domain of the unified website knowledge MCP (POST /api/mcp): 784 upstream-governed documents chunked semantically, organized into three categories with scenario and category hard filters. Public layers (platform profiles, field pairs, value presets, mechanisms, ops runbooks — 9 layers) are searchable with a Standard key; solutions, cases and failure knowledge stay restricted for authorized keys.

Three categories (K1 / K2 / K3)

K1 · Platform operations & maintenance

Platform operation and maintenance knowledge, FAQ, troubleshooting runbooks and error-code → remediation SOPs (upstream OPS/PLAY/FAIL layers). For patrol and incident work.

K2 · Platform APIs & metadata

API characteristics, auth, pagination/rate limits and metadata configuration for Kingdee / Wangdiantong / Jushuitan / DingTalk / Yonyou / SAP and more (MECH/PLAT/OBJ/PRESET/SCRIPT layers). Check here before configuring strategies or writing scripts.

K3 · Integration design patterns

Design patterns, best practices and full/incremental/idempotent/reconciliation paradigms for system integration (PAT/PAIR layers; CASE/SOL case details stay restricted). For solution design and review.

Search access

Endpoint: POST https://qeasy.cloud/api/mcp — tools knowledge_search / knowledge_fetch / knowledge_domains, sharing keys and quotas with reconciliation knowledge.

Filters: product="data-integration"; scenario (S1 solution design / S2 configuration, default / S3 operations — hard-filtered before recall); category (K1/K2/K3, comma-separated).

Citations look like docs/knowledge/<doc>#<section>; knowledge_fetch accepts citation#section or citation#chunkId for a single chunk.

Example: required fields for writing a Kingdee Cloud sale order (S2)

curl -s https://qeasy.cloud/api/mcp \
  -H 'content-type: application/json' \
  -H 'Authorization: Bearer qk_live_YOUR_KEY' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"knowledge_search","arguments":{"query":"required fields to write a Kingdee Cloud sale order","product":"data-integration","scenario":"S2","category":"K2"}}}'

Visibility tiers

Public (Standard keys): platform profiles, object cards, field pairs, value presets, mechanism docs, ops runbooks, playbooks, script library and patterns — ~6,079 chunks with zero UUIDs, company names or amounts (vendor names are normal content).
Restricted (Authorized): solutions (anonymous tenant codes), cases (plan names and run volumes), failures (negative cases).
Live counts via knowledge_domains with product=data-integration.

Private deployment & offline

Knowledge retrieval is a public-cloud service; fully private deployments without internet cannot reach it yet (the offline knowledge bundle is scheduled as datahub-side M6-4 and is currently a known limitation).

Operational capabilities for private environments go through the DataHub Platform MCP (/skill/datahub), complementing retrieval: learn “how to configure” from knowledge, then act on the instance via the platform MCP.

Start searching data-integration knowledge

Get a Standard key at /account to search public knowledge; apply for Authorized to unlock solutions and real cases.

Get an API key Platform operations MCP