Documentation
Build on the meaning layer
Lexicor is a semantic mediation and encoding layer for multi-agent systems. Canonicalize human, agent, and tool output into one IntentGraph; carry it across hops as versioned, compact transport packets; and render it to any surface — with fail-closed versioning and deterministic round-trip equivalence.
Start here
What is Lexicor
Concepts and vocabulary: IntentGraph, packets, symbol tables, fail-closed.
Quickstart
Make your first authenticated round-trip in a few minutes.
API reference
Every REST endpoint with schemas, examples, and a Try-it console.
Self-hosting
Run the API in your own environment behind your own controls.
How Lexicor works
Natural input enters at the edge. Lexicor converts it to a canonical semantic graph at the first trusted boundary, encodes it into a compact, codec-agnostic form for inter-agent transport, and renders output into any target language, schema, or protocol. Three verbs describe the whole surface:
- Canonicalize — parse any input into one IntentGraph of entities, predicates, and constraints. Language-neutral and versionable.
- Transport — encode the graph into a typed, versioned packet envelope. Unknown or incompatible versions are rejected at decode time — no silent fallback.
- Render — turn a graph back into natural language, tool-shaped JSON, or a protocol payload for the next hop.
Lexicor defines what crosses the wire. Packets ride inside the carrier your system already uses — HTTP bodies, gRPC fields, MCP tool results, or agent-to-agent messages.
How these docs are organized
- What is Lexicor — the model and the core terms you will see throughout.
- Quickstart and the Python / TypeScript SDKs — task-first guides with runnable code.
- API reference — the normative request/response contract for every endpoint.
- Self-hosting — running and operating the API yourself.