Five-minute integration
Make your first governed request.
Start with text governance. Then use the same key to connect an MCP client when you need action and tool-call governance. Every successful request returns constitutional state and an audit receipt.
1. Try the public demo
No key is required for a small number of demo requests. Use a stable session ID for an application so its trajectory and receipts remain coherent.
curl -sS https://www.lexaureon.com/api/lex/govern \
-H 'content-type: application/json' \
-d '{"prompt":"Summarize this text safely.","session_id":"quickstart-demo","turn":1}'2. Create a key for an integration
Open API Keys, enter your email, and copy the key immediately. It is shown only once. Keep it server-side and never send it in a model-visible prompt or commit it to source control.
curl -sS https://www.lexaureon.com/api/lex/govern \
-H 'content-type: application/json' \
-H 'x-lex-api-key: lex_sk_YOUR_KEY' \
-d '{"prompt":"Summarize this text safely.","session_id":"my-app","turn":1}'3. Inspect and verify the receipt
Save the returned receipt_id. The public audit page exposes persisted evidence without exposing your prompt or response text.
# Replace RECEIPT_ID with the returned KRN-... value curl -sS https://www.lexaureon.com/api/audits/RECEIPT_ID # Browse recent public receipts curl -sS 'https://www.lexaureon.com/api/audits/recent?limit=5'
4. Connect an MCP client
Use this server URL in an MCP-compatible client:
https://www.lexaureon.com/api/mcp
For API-key clients, send x-lex-api-key or Authorization: Bearer at the transport layer. OAuth-capable clients can use the protected-resource metadata at /.well-known/oauth-protected-resource. Do not put operator secrets in an agent prompt.