Everything you need to consult Knowledge from your stack, wrap a business tool with signed authorization, or wire an MCP host to Knowledge tools.
Getting started
| Page | Description |
|---|---|
| What is Knowledge ? | Two minutes on the mental model and vocabulary. |
| Quickstart : create your first policy | From empty tenant to first /resolve returning a real verdict, in about 30 minutes. The author path. |
| Quickstart : governed tool in Python | Two patterns for signed-verdict enforcement on a Python tool : verify a verdict you receive, or let a decorator self-consult. |
| Quickstart : Knowledge as an MCP server | Wire the Knowledge MCP server into Claude Desktop / Cursor / any MCP host so the agent can query, check, and request approvals as tool calls. |
Concepts
Deeper explanations of the core abstractions.
| Page | Description |
|---|---|
| Policies, rules and targets | The three core aggregates. |
| Verdicts and decisions | Severity ladder, precedence, Consultation record. |
| Signed verdicts and PEP | The JWS envelope, binding checks, spent-verdicts. |
| Progressive context resolution | The /resolve loop and dependency inversion. |
| Overrides, approvals, pauses | The three governed exception mechanisms. |
| Four-actor trust model | Who signs, who verifies, what each edge guarantees. |
API reference
| Endpoint | Description |
|---|---|
| Authentication | API keys, session cookies, principal binding. |
| POST /v1/check | Deterministic verdict, strict context. |
| POST /v1/resolve | Progressive verdict, tolerant context. |
| GET /v1/tenants/{slug}/jwks | JWKS for signature verification. |
| GET /v1/consultations/{id} | Retrieve a Consultation record. |
| /v1/approvals | Create, poll, decide. |
Full OpenAPI spec at docs/api/openapi-v3.json in the monorepo. Postman collection : docs/api/postman/knowledge-v3.postman_collection.json.
SDK reference
| Page | Description |
|---|---|
| knowledge-runtime (Python) | @governed_tool, verify_verdict, JWKS cache, guard-rails. |
| TypeScript SDK [Roadmap] | Feature parity with Python planned for Q4-2026. |
MCP server
| Page | Description |
|---|---|
| Tools reference | The eight tools the Knowledge MCP server exposes, with parameters and return format. |
Guides
| Page | Description |
|---|---|
| Wrap your own MCP server with enforcement | The pattern for gating an MCP server's tool calls with Knowledge signed verdicts. Reference example in the monorepo. |
| Rotate signing keys | Scheduled + emergency rotation. |
| Multi-tenant setup | Run multiple tenants on one deployment. |
| Migrate from advisory to enforcement | The three-stage playbook. |
| Emergency response | Kill switch, key rotation, downgrade. |
Security + compliance
| Page | Description |
|---|---|
| Trust model deep dive | Four-actor chain, edge-by-edge threats. |
| Keys inventory | All four cryptographic keys, storage, rotation. |
| Deployment shapes | SaaS, VPC, on-prem trade-offs. |
| Compliance posture | Certifications, residency, retention, threat model. |
Send feedback to contact@asplenz.com.