Developer Evaluation
Your code. A governed response.
Evidence you can inspect.
Run a small exercise on your machine, send it through LSAS, and see what was allowed, sanitized, or withheld in your private console.
Start your evaluation
Verify your email, create your workspace, and get an API key. The downloadable evaluation harness requires Node.js 20+. The LSAS API works with any standard server-side HTTP client. No model-provider account is required.
Eight ways to test the boundary
Start with the failure you want to stop.
Choose a scenario to preview its policy and expected outcome. In your private console, inspect ingress and egress decisions, the actual synthetic provider call count, and the content authorized for return.
Block before execution
A supported instruction-override pattern blocks the downstream call.
Required policydeveloper-data-guard@1.0.0- Expected outcome
- BLOCKED
- Expected provider calls
- 0Stopped before the provider
Your first API call
See what changes. In your language.
Send synthetic JSON to LSAS and inspect the governed response. Standard HTTP clients, no LSAS SDK or model-provider account required.
Developer Data GuardVersion 1.0.0 · Default evaluation policy
1. Set your key in a local terminal
export LSAS_API_KEY='<paste your evaluation key>'Replace the placeholder with your key. Keep it in your local environment or server, out of browser code and Git.
Paste into the terminal where you set your key.
curl --disable --silent --show-error --include --max-time 15 \
--request POST 'https://www.lsasplatform.com/v1/payload/sanitize' \
--header "x-lsas-api-key: ${LSAS_API_KEY:?Set LSAS_API_KEY first}" \
--header 'Content-Type: application/json' \
--data-raw '{"payload":{"message":"Contact engineer@example.invalid about the sample project."}}'Application integration requirements
These snippets print the response for inspection. Forward only data when HTTP is 200 and lsas.enforcement.outcome is RELEASED or TRANSFORMED. Check the returned policy ID and version against the policy you intend to use. Never forward the original input.
BLOCKED (400) and HELD (409) withhold data; they are expected policy outcomes. Other errors stop the request. A hold does not create a review or release grant. After signup, the downloadable three-request exercise also proves what a local receiver consumes.
REST integration reference
Content decisions. Action authority. One key.
Send JSON from your server or local program. Authentication and the exact policy assignment are enforced by LSAS.
- Base URL
https://www.lsasplatform.com- Headers
Content-Type: application/jsonx-lsas-api-key: <your evaluation key>
Inspect a payloadPOST /v1/payload/sanitize
{
"payload": {
"message": "Contact engineer@example.invalid about the sample project."
}
}Returns { data, lsas }. Forward only authorized returned data. The six language examples demonstrate inspection; the downloadable middleware protects a downstream handler.
Exercise request and response controlPOST /v1/evaluation/scenarios
{
"scenarioId": "redact-input",
"input": "Contact engineer@example.invalid about the sample project."
}Returns { data, lsas, ingress, demo }. The scenario fixes its synthetic provider response and requires its exact policy. Optional request text is limited to 4,096 UTF-8 bytes; the full request to 8,192 bytes. No provider, policy, tool, or destination overrides are accepted.
Test fixed action authorityPOST /v1/evaluation/actions
{
"caseId": "wrong-destination"
}Returns { data, lsas, action }. Choose allowed-read, wrong-destination, or unregistered-action. Inspect content classification separately from action permission and actual reader invocation count. This is a fixed in-process synthetic reader; caller-defined actions, destinations, credentials, and tools are unavailable.
Response status and safe application handling
| Status | Meaning and application behavior |
|---|---|
| 200 | Governed result. Inspect the decision and ENFORCE outcome. Only RELEASED or TRANSFORMED returned data may proceed; warnings remain visible in the evidence. |
| 400 | Invalid request, or governed BLOCKED with data: null. An action denial is distinct from a content-policy finding. Check for the LSAS envelope; never forward the original content. |
| 409 | Policy mismatch without execution, or governed HELD with data: null. A hold is not an approval; this evaluation cannot approve or resume it. |
| Other / network | Authentication, quota, expiry, or infrastructure failure. Do not call your downstream handler. A transport failure can occur after a decision was recorded; inspect history before retrying. |
The same 14-day period, 10,000-decision allowance, and 30-request/minute budget cover all evaluation routes. Use lsas.audit.requestId to find persisted metadata in your console. Request and response content shown during a scenario is transient and excluded from evidence exports.