Getting Started with Notis

In the control plane, open Gateway and click Activate. Provisioning takes a minute or two; the page updates to Ready when your dedicated gateway is live. Note its endpoint — it looks like:

https://<your-workspace>.gateway.notis.io

A freshly started gateway warms up for a few seconds while it loads your policy. If a request lands in that window it returns 503 with Retry-After — just retry.

Open Policies and browse the pack catalog. Pick a starting point — e.g. PII Baseline (redacts SSNs, emails, phone numbers, cards) or Secrets (API keys, tokens, private keys) — and activate it. Policies compose, so you can attach more than one, and scope them to specific workloads.

Each check has an action: monitor (observe only), redact, tokenize (reversible — restored on the response), or block. Start with monitor if you want to see what fires before enforcing.

Open API Keys and generate a key. It looks like nt_live_… and is shown once — copy it now. This is the credential your app or agent presents to the gateway (it never sees your real provider key; the gateway holds that).

You don’t rewrite your code — you change one base URL so calls go to your gateway instead of the provider directly. Pick your path:

curl https://<your-workspace>.gateway.notis.io/v1/messages \
  -H "x-api-key: $NOTIS_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-sonnet-4-5",
    "max_tokens": 256,
    "messages": [
      { "role": "user",
        "content": "Draft a reply to John Doe, SSN 123-45-6789." }
    ]
  }'

from openai import OpenAI

client = OpenAI(
    base_url="https://<your-workspace>.gateway.notis.io/v1",
    api_key="nt_live_...",  # your Notis key, not your OpenAI key
)

client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "..."}],
)

Send a prompt containing something sensitive (an SSN, an API key) and watch it get redacted before it reaches the model. Two easy ways to confirm it’s working:

• Policy Tester (in the control plane) — send a sample prompt with and without Notis and see the gateway’s decision side by side.
• Audit Log — every request shows the action taken, what was detected, the policy that fired, and the gateway’s own overhead (sub-millisecond; the total round-trip time is the model generating a response, not Notis).

Open Coverage. Notis flags any sensitive data it detected that your active policy doesn’t yet govern — your unreviewed exposure. For each category you decide: enforce it (add a pack), monitor it, or dismiss it as an auditable decision. Drive it to zero and you have a policy that matches your real traffic.