Reconciliation knowledge lives in the reconciliation domain of the unified website knowledge MCP (POST /api/mcp): 12 knowledge domains, platform topics and customer cases, one atom per chunk, Git-traceable. General methodology and accounting standards are public (Standard keys); platform playbooks and customer cases stay restricted for authorized keys. The reconciliation operations MCP is fully privately deployed — the website currently ships only the knowledge base.
Endpoint: POST https://qeasy.cloud/api/mcp with product="reconciliation"; domain/platform/type filters and granularity=atom are supported.
The reconciliation domain has no scenario/category semantics (those belong to the data-integration serves/K filters); call knowledge_domains first to route queries.
Example: when is expense allocation by revenue share reasonable
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":"expense allocation by revenue share","product":"reconciliation","granularity":"atom","includeMeta":true}}}'The reconciliation operations MCP/skills are fully privately deployed private MCPs (governance ruling: split criterion = whether the Agent task differs).
The website currently publishes only the reconciliation knowledge base; contact Qeasy for operations access.
Get a Standard key at /account to search public methodology and standards; apply for Authorized to unlock playbooks and cases.