Respondus
Respondus builds assessment-integrity tools for online exams - most notably LockDown Browser, a custom browser that locks down the testing environment, and Respondus Monitor, an automated webcam-based online proctoring service that adds AI-assisted review on top of LockDown Browser. Over 2,000 institutions across 50+ countries use Respondus to deliver hundreds of millions of online exams a year. Respondus does not publish a self-service public developer API. Its products reach learning platforms through LMS integration rather than an open REST surface - native plugins/building blocks plus the IMS Global LTI (Learning Tools Interoperability) standard for Blackboard, Brightspace, Canvas, Moodle, Sakai, and Schoology, and a privately-licensed LockDown Browser SDK for third-party assessment platforms that must be arranged through Respondus sales. No public OpenAPI, developer keys, or documented endpoints are offered.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Respondus the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Respondus scores 8.9/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Respondus
Each block below is one kind of artifact we hold for Respondus. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Respondus — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/respondus · machine-readable index on apis.io