Say hello to the ISMS Copilot API
One compliance brain behind a single OpenAI-compatible endpoint. It already knows 100+ frameworks, tells you when each was last verified, runs with zero data retention, and lets you pick US or EU inference.

The ISMS Copilot API is live. It is a model provider built for compliance work: one OpenAI-compatible endpoint that already knows more than 100 frameworks, from ISO 27001 and SOC 2 to HIPAA, GDPR, NIS 2, and DORA.
What it is
The API speaks the OpenAI chat completions protocol, so any OpenAI SDK works with a one-line change of base_url. That compatibility is only how you call it. The product is what happens before the model answers: curated framework knowledge is injected at inference, so you do not have to assemble and maintain a standards corpus yourself.
It runs on the best open source models, plus our own compliance specialization. On compliance work, our isms-thinking alias reaches Opus-level quality at a fraction of the cost, roughly three times less.
What you get
- Fluent in 100+ frameworks out of the box. ISO 27001, SOC 2, HIPAA, GDPR, NIS 2, DORA, NIST, CMMC, CCPA, ISO 42001, the EU AI Act, and more. Detection is automatic, and every response tells you which framework modules it used.
- A knowledge catalog that is fully public, and dated. The list of frameworks the API knows is public, including when each module's knowledge was last verified. You can see what it knows and how fresh that knowledge is, rather than trusting a black box.
- Models fit to each task.
isms-miniis the high-volume lane for extraction, classification, and formatting, at $2 per 1M output tokens.isms-fastis for quick answers at low latency.isms-thinkingis for the hard reasoning a reviewer will sign off on. - Zero data retention, your choice of region. Prompts and outputs are never stored and never used to train models. Choose US or EU inference with the
-eualiases, so data residency is a per-call decision.
Your first call
curl https://api.ismscopilot.com/v1/chat/completions \
-H "Authorization: Bearer sk-isms-..." \
-H "Content-Type: application/json" \
-d '{
"model": "isms-thinking",
"messages": [
{"role": "user", "content": "List 3 ISO 27001 access control requirements."}
]
}'
Create a key and top up prepaid credits in the platform console. Every paid plan includes a one-time $10 API credit, so your first calls are on us. Credits are separate from your chat subscription, and completions debit the prepaid balance.
Honest scope
This is the developer API, not the chat web app and not the website assistants widget. It does not do tool or function calling yet, so it fits best as a compliance step inside your own pipeline: your agent keeps its general model and tools, and calls this endpoint for the compliance-aware answer. The models behind each alias can change over time; the aliases are the stable contract for your integration.
Live now
Create a key at platform.ismscopilot.com and read the API documentation.
We shared the launch on LinkedIn. Join the conversation there:
Related Posts

One plan, free teammates: chat teams move to a shared usage pool
ISMS Copilot chat teams no longer bill per seat. You buy the plan once, invite up to 50 colleagues, and the whole team draws from one shared usage pool at that plan's limits.

Company context: tell the assistant who you are, once
An assistant that does not know your sector, your data, or where you host is writing policies for a company that does not exist.

Chat keeps the document ID you already issued
A policy is one controlled record. If the next draft invents a new ID, you do not have a new version. You have a second document you then have to reconcile.
