| status | current |
|---|---|
| version | v10 |
| audience | human+agent |
| doc_type | reference |
The canonical route contract is generated from the running daemon and exposed to agents through the DKG Node Skill:
packages/cli/skills/dkg-node/SKILL.mdGET /.well-known/skill.mdon a running daemon
Use this page as a lookup pointer, not as a duplicate API definition. The highest-risk route families are:
| Area | Route family |
|---|---|
| Context graphs | /api/context-graph/* |
| Knowledge Assets and VM publish | /api/knowledge-assets/* |
| SWM substrate operations | /api/shared-memory/catchup, /api/shared-memory/host-mode/*, /api/shared-memory/verify-batch |
| Query | /api/query |
| Agents and messaging | /api/agents, /api/chat, /api/messages, /api/invoke-skill |
| Node identity and Core profile registration | /api/identity, /api/identity/ensure |
| Publishing Conviction Accounts | /api/pca/* |
| Messaging SLOs | /api/slo |
| Node status and peers | /api/status, /api/peer-info, /api/wallets/balances |
Named Knowledge Assets use the lifecycle route family below. The active publishing path is create, write, finalize, share, then publish; VM publishing always operates on a named KA that has already been shared to SWM.
| Lifecycle step | Route |
|---|---|
| Create/open WM draft | POST /api/knowledge-assets |
| Write RDF quads | POST /api/knowledge-assets/{name}/wm/write |
| Import a document | POST /api/knowledge-assets/{name}/wm/import-file |
| Check import status | GET /api/knowledge-assets/{name}/wm/extraction-status |
| Finalize/seal | POST /api/knowledge-assets/{name}/wm/finalize |
| Share WM to SWM | POST /api/knowledge-assets/{name}/swm/share |
| Enqueue async WM to SWM share | POST /api/knowledge-assets/{name}/swm/share-async |
| Inspect async share jobs | GET /api/knowledge-assets/swm/share-jobs, GET /api/knowledge-assets/swm/share-jobs/{jobId} |
| Cancel/recover async share jobs | DELETE /api/knowledge-assets/swm/share-jobs/{jobId}, POST /api/knowledge-assets/swm/share-jobs/{jobId}/recover |
| Publish SWM to VM | POST /api/knowledge-assets/{name}/vm/publish |
| Enqueue async VM publish | POST /api/knowledge-assets/{name}/vm/publish-async |
| Seed/edit from SWM or VM | POST /api/knowledge-assets/{name}/wm/pull-from |
| Discard WM draft | POST /api/knowledge-assets/{name}/wm/discard |
| Read WM quads | GET /api/knowledge-assets/{name}/wm/quads |
| Read lifecycle descriptor | GET /api/knowledge-assets/{name} |
Both VM publish routes accept options.publisherNodeIdentityIdOverride. Use a non-negative decimal string; 0 means explicit no-attribution. Omit the option to use the publisher wallet's resolved default identity, which may also be 0. Optional node attribution for a separate publisher wallet can be configured through /api/operational-wallets.
For exact request bodies, response shapes, and MCP tool names, use Node Skill.