Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lasscyber.com/llms.txt

Use this file to discover all available pages before exploring further.

Agnes is an AI security service that protects production LLM applications. You send Agnes the text flowing in or out of your LLM — user prompts, model responses, retrieved documents — and Agnes decides whether it is safe to proceed. Behind the API, Agnes runs a suite of analyzers in parallel: The hero method is the Agnes Analyzer — a single endpoint, POST /api/v1/analyze/, that runs a combination of those analyzers under a customer-defined policy.

5-minute quickstart

Sign up, mint an API key, and run your first analysis with the Python or TypeScript SDK.

How Agnes works

The request lifecycle from your code to the analyzer pipeline and back.

Build a policy

Combine analyzers, set thresholds, and define when to block, warn, or pass through.

API reference

Full OpenAPI reference with an interactive playground for every endpoint.

​
What Agnes is for

You should reach for Agnes when you are shipping LLM-powered features and you need a security layer that does not depend on your model vendor. Typical deployments place Agnes:
  1. In front of every prompt going to your model, to block prompt injection, jailbreak attempts, and policy violations before tokens leave your tenancy.
  2. In front of every response coming back from your model, to catch safety violations, leaked sensitive data, or malicious URLs before they hit users.
  3. On retrieval pipelines (RAG ingestion, tool outputs), to scan third-party content with the same policy your prompts get.
A typical guarded LLM call looks like this: 
from agnes import Agnes, Blocked

agnes = Agnes()  # AGNES_API_KEY from environment

with agnes.guard(policy="default-inbound") as guard:
    guard.check_input(user_prompt)            # raises Blocked on fail
    reply = openai_client.chat.completions.create(...)
    guard.check_output(reply.choices[0].message.content)

​
Where to next

​
Service status

Real-time API health and incident history live at status.lasscyber.com. Subscribe via email or Slack to be notified the moment an incident opens or resolves.

​
Help

If you cannot find what you need:
  • File a ticket from the in-app Support page — your tenant, plan, and recent request IDs are attached automatically.
  • Email support@lasscyber.com and quote a recent X-Request-ID from the API response. The SDKs surface it as decision.request_id (Python) / decision.requestId (TypeScript).