Signup
Create an account and workspace. The first launch only needs email.
One Spectorn key for model discovery, prepaid credits, fail-closed prompt checks, and conversation memory. Keep your OpenAI-compatible SDK.
Choose a model from the Spectorn catalog and call it through one OpenAI-compatible endpoint.
Browse allRoutes and fallback live in the gateway while your client SDK and request shape stay the same.
Learn morePrepaid balance, limits, keys, and usage history are collected in the user workspace.
View pricingPrompt injection, jailbreak, leakage, and policy risk are checked before the request reaches a model.
View docsA familiar catalog: model, use case, availability, and one Spectorn key.
The reasons teams buy more than a plain router: protected agents, MCP, memory, and security enablement.
MCP, tools, repo context and command guardrails for engineering teams.
Memory, retrieval context and leakage checks for customer-facing assistants.
Threat libraries and policies for regulated AI deployments.
Create an account and workspace. The first launch only needs email.
Add prepaid balance and keep team spend inside clear limits.
Point base_url at Spectorn and call models with the same SDK.
On the surface: models, keys, usage, and credits. Under each call: a protection gateway and optional persistent memory.
Requests are checked for prompt injection, jailbreak, exfiltration, and policy violations before the model call.
Add persistent context with a session header, without a separate memory service.
Allow, deny, and reroute models by workspace, key, and task.
Keep verdict, usage, and route history for incident review and cost control.
Only the endpoint changes. Your message format, SDK, and workflow stay familiar.
from openai import OpenAI
client = OpenAI(
base_url="https://spectorn.xyz/v1",
api_key="sk_spct_...",
)
resp = client.chat.completions.create(
model="spectorn/auto",
messages=[{"role": "user", "content": "Summarize this ticket."}],
extra_headers={"X-Spectorn-Session": "customer-42"},
)
# Spectorn checks the request before the model call.
# Output verdicts and usage are stored in your workspace.A specialist knowledge base, from beginner onboarding to industry-specific LLM protection scenarios.
One key, familiar model catalog, credits, protection, and memory in one gateway.