BUILD & OPERATE
Docs / Getting started
Getting started with Scryer
Start with your organization’s domains, review relevant exposure, and build a repeatable process for turning findings into action.
↗
docs-getting-started
Docs / Search & discovery
Searching for exposed data
Find records connected to your organization and refine your investigation using domains, account identifiers, and source context.
↗
docs-search-discovery
Docs / Intelligence & context
Understanding your findings
Capture enough metadata to troubleshoot model requests while keeping prompt and response content out of routine telemetry.
↗
understanding-findings
Docs / Investigation & response
Responding to exposed credentials
Assess an exposed account, coordinate containment, and verify the response across identity, endpoint, and application systems.
↗
responding-to-exposed-credentials
Docs / Data & access
Handling sensitive intelligence
Keep investigations focused, limit sensitive data sharing, and maintain a clear record of how intelligence is used and handled.
↗
data-handling
SCRYER DOCUMENTATION
From first search to informed action.
Everything you need to start investigating with Scryer. Learn how to find exposed data, understand the evidence, and turn relevant findings into a clear response
Start with one workload.
Choose a model-powered feature, define its constraints and follow one request from input to result. Keep credentials on your server and separate development from production.
Understand the request boundary.
A familiar request surface keeps application code independent of routing decisions. This provider-neutral example shows the structure to adapt to your own endpoint and credentials.
import os
from openai import OpenAI
client = OpenAI(
base_url="https://api.your-domain.com/v1",
api_key=os.environ["API_KEY"]
)
response = client.chat.completions.create(
model="balanced",
messages=[{
"role": "user",
"content": "What should we build next?"
}]
)Make the system observable.
Use the guides to choose a routing policy, inspect a request trace and define your deployment boundary. Collect only the operational metadata your team needs.