For assessment platforms
The Security Layer Your Enterprise Assessment Buyers Demand
One REST API. Zero candidate friction. Zero UI changes. Aiseptor becomes the security substrate of your platform. Your brand stays on the glass; Aiseptor handles the device and network layer beneath.
// Create an Aiseptor-secured session for a candidate.
// Your platform keeps exam authoring, scoring, and UX;
// Aiseptor handles the device + network layer.
POST /api/v1/sessions
Authorization: Bearer $AISEPTOR_API_KEY
{
"candidate_id": "cand_7f3a...",
"exam_ref": "exam_a1b...",
"duration_minutes": 90,
"policy": {
"allowed_domains": ["leetcode.com", "docs.python.org"],
"aegis_mode": "active"
}
}
// → 201 Created
{
"session_id": "sess_xyz...",
"join_code": "482917",
"agent_download_url": "https://cdn.aiseptor.com/..."
}Webhook signatures use HMAC-SHA256. See the real request and response on the developer quickstart →
Why platforms embed
Your enterprise buyers are losing trust in your scores. Aiseptor gives it back.
You already know the data. Half of technical candidates are using AI in live interviews. Your enterprise buyers know it too. They are renegotiating their contracts, piloting alternative vendors, or building in-house. The churn isn't coming from a better assessment engine; it's coming from a cheating tool that your stack can't see.
Detection loses every generation. Aiseptor shifts the contract from detecting misbehavior to preventing the network path that makes it possible, mathematically, on any candidate device, without touching your UX.
The integration
Three endpoints. One webhook. Ship in 3–5 days.
You don't rebuild your platform. You embed a security substrate. Your candidate still lands on your UI, takes your assessment, and submits to your scoring engine, with an Aiseptor-secured device underneath.
Create a secured session
When a candidate begins an assessment, your backend calls POST /api/v1/sessions with an exam reference, duration, and allowed-domain policy. Aiseptor returns a short-lived session_id and 6-digit join code.
Candidate joins the enclave
Your UI shows the join code and agent download link. The candidate runs the Aiseptor agent, enters the code, and is inside a 30-second-deploy ephemeral security enclave. No persistent install. No kernel drivers.
Receive the verdict webhook
On session end, Aiseptor posts a signed webhook with the Aegis integrity score, flagged signals, and a link to the full audit report. Your platform ingests it and stores it against your candidate record.
POST https://your-platform.com/aiseptor/webhook
X-Aiseptor-Signature: sha256=...
{
"event": "session.ended",
"session_id": "sess_xyz...",
"aegis": {
"status": "FLAGGED",
"signals": ["AI_LOCAL_LLM", "OVERLAY_CHEAT"]
},
"audit_url": "https://gateway.aiseptor.com/report/..."
}Three endpoints for you. A full console for your proctors.
You integrate an API. Your proctors get live posture, a per-candidate roster, and a signed report per session, without you building any of it.
No secret wholesale rate. One price list, for everyone.
Aiseptor keeps one price list. Your enterprise buyers see exactly what you see; no secret wholesale rate, no channel-markup game to defend. A partnership isn't about reselling our product; it's about tighter integration and the commercial defense that comes with it: named on your security page, co-marketed on buyer RFPs, and a unified integrity narrative when cheating complaints hit procurement.
Quoted per contract
Usage-based, scoped to volume
Aiseptor bills per exam session, with no seat fees and no licence floor. The tier follows what you run rather than how much of it, and a single session covers up to three hours. Rates are quoted on a partnership call against your actual volume and payment terms, which is how they end up below what a published rate card would give you.
Partnership-tier features (enterprise SLA, white-label audit PDFs, extended data retention, SOC 2 shared responsibility mapping, dedicated integration engineer) are bundled at the custom commercial tier and negotiated during partnership kickoff.
Who owns what
You keep your brand. We handle the hard part.
- Exam authoring and question banks
- Candidate scheduling, invitations, and branding
- Scoring engine and result reporting
- The enterprise buyer relationship
- All UI: candidates never leave your platform
- Storage of results, submissions, and audit records
- The ephemeral security enclave on the candidate device
- Real-time device + network threat prevention
- Aegis integrity scoring + structured signal output
- Candidate agent binaries for Windows and macOS
- Cryptographic audit trail (webhook-delivered)
- Threat intelligence updates against new cheating tools
Will this survive your security review? Here's the paper trail.
SOC 2 Type II (Q3 2026)
SOC 2 audit in progress with a targeted report date of Q3 2026. GDPR- and CCPA-compliant by design; standard DPA available for enterprise contracts.
Patent pending
Method of deploying an ephemeral deterministic network enclave in user-space without kernel privileges or persistent drivers. Filing details available under NDA.
Session metadata only
Network access requests and device integrity signals. No webcam, microphone, keystrokes, or file contents. No footage is captured, so none is retained; post-exam records default to 90 days and are configurable from 7 to 365 days by the institution; longer windows available under DPA.
Public bug bounty
Open invitation to the research community to break the enclave. Program scope and disclosure terms shared on request during partnership kickoff.
Questions platform teams ask before they integrate.
How long does an Aiseptor platform integration take?
Typical integration for an assessment platform takes 3–5 engineering days. Three REST endpoints, one webhook, no candidate-facing UI changes. Sandbox credentials and an integration engineer pair are provided at partnership kickoff.
How is Aiseptor priced for platform partners?
Aiseptor has a single price list that applies to every customer, including platform partners; there is no separate wholesale rate. Pricing is usage-based and billed per exam session, with custom volume terms for large cohorts or high monthly session counts, negotiated at kickoff alongside SLA, white-label audit reports, and enterprise data retention. Current rates are shared directly on a partnership call.
Does Aiseptor replace our existing proctoring partner?
No. Aiseptor is a device- and network-layer security substrate. Behavioral and physical proctoring (webcam, gaze, human proctors) complements Aiseptor above. Lockdown browsers, application-layer tools like Respondus LockDown Browser or Safe Exam Browser, are what Aiseptor replaces.
Further reading
- Exam security API for developersThe session endpoint, the webhook contract, and what the integration actually looks like.
- Proctoring software for assessment platformsWhy platforms are being asked for network-layer enforcement by name, and what embedding it involves.
- Secure remote assessment architectureA lockdown browser secures one window. How to architect remote assessment when the threats do not run in one.
60-minute deep dive. Your engineer asks anything. We show the API, the audit trail, and the math.
Book a partnership call and we'll tailor the session to your platform, walking through integration timelines, pricing for your expected session volume, and your security review checklist. Technical founder in the room. NDA standard.