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
New to Lexicor — no corpus, no agents registered yet? This is the path once you have console access. Each step takes minutes; stop at any step and you still have something running.
- Open Lexicor Cloud — sign in at the hosted console, open Settings, and reveal your API key.
- Make your first call — one authenticated round-trip with curl. No install beyond an HTTP client.
- See it in the console — your call shows up in Live Activity and the audit log; the Send request page runs the same pipeline interactively.
- Register your stack — add your agents and tools, attach a policy, and mediate with identity instead of a bare key.
- Bring your local tools — run the MCP Proxy next to tools that never leave your network; evidence still lands in your tenant.
Go deeper
API reference
Every REST endpoint with schemas and examples.
Workflows
Proof of value, production mediate, compliance export, MCP Proxy.
Hosted console
UI map: dashboard, policies, audit, Settings, and billing.
Self-hosting
Running and operating the API yourself.
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
- Introduction — What is Lexicor: the model and the core terms you will see throughout.
- Get started — the Quickstart (authenticated curl walkthrough), Lexicor Cloud (create a trial tenant and reach a first evidence pack), and Workflows (the end-to-end journeys: proof of value, production mediate path, compliance export).
- Product — the Hosted console, Lexicor Edge and the MCP Proxy add-ons, and Plans & pricing.
- API reference — the normative request/response contract for every endpoint.
- Self-host & operate — Self-hosting the API and Troubleshooting.
- Trust & support — Security & trust for reviewers and procurement, and Support.