Product

Lexicor Edge

A small client you run next to your agents. It queues mediate requests locally and flushes them to Lexicor Cloud in batches — so flaky networks and burst jobs do not block on a live round-trip.

What it is

Every Cloud request normally needs a live call to POST /v1/envelope/mediate. Edge adds:

A local JSONL spool (lexicor-edge enqueue)
Batch flush to POST /v1/envelope/mediate-batch (max 100 items)
Optional daemon (lexicor-edge run) that flushes on an interval and caches policy IDs for enqueue-time warnings

Each flushed item still runs full mediation (policy, ledger, metering). There is no raw ledger append from the client.

Edge vs MCP Proxy

Edge ($79/mo) — request sync: spool / batch flush / policy pull. Use for flaky networks, burst traffic, VPC jobs that must not block on Cloud RTT, or batch backfill of requests.
MCP Proxy ($129/mo) — tool-data plane: private MCP upstreams; tool payloads never leave your network.
Both — local tools + durable request sync ($208/mo combined on Standard/Pro). Enterprise includes both.

Entitlement

Requires the edge_client add-on ($79/mo on Standard or Pro). Included on Enterprise. Without it, /v1/envelope/mediate-batch and /v1/edge/status return 403. Tier availability and other limits: Plans & pricing.

Get the add-on

Sign in at console.lexicor.io on Standard or Pro.
Open Add-ons → Edge and buy, or ask support to grant edge_client.

Install and run

bash

pip install lexicor
export LEXICOR_API_URL=https://api.lexicor.io
export LEXICOR_API_KEY=lx_...
lexicor-edge doctor
lexicor-edge enqueue --policy-id YOUR_POLICY \
  --envelope env.json --correlation-id c1
lexicor-edge flush
# or daemon:
lexicor-edge run

Entitlement errors

If doctor or flush returns 403, the API key is not entitled. Purchase Edge in the console, upgrade to Enterprise, or ask support to set addon_features including edge_client.

Next steps

MCP Proxy for private tool servers
Workflows for common Cloud patterns
Lexicor Cloud for tiers and upgrade