OpenAPI reference
This page renders the AdminKit Check API's OpenAPI contract directly from the source spec, grouped by tag with every path, method, parameter and response shape. Every endpoint authenticates with an API key — talk to our team about access, or use the free web pages that run the same checks in your browser.
Updated
AdminKit's OpenAPI contract is published and normally renders in full above, grouped by tag. This build could not load the spec file — reload the page, or contact us if the reference does not return.
References
This contract follows the OpenAPI Specification format, describes its request and response bodies using JSON Schema, and, once deployed, every response will follow standard HTTP semantics as RFC 9110 (canonical record in the IETF Datatracker) defines it:
Frequently asked questions
Where does this OpenAPI contract come from?
This page renders AdminKit's current OpenAPI contract in full from the source spec, not a hand-written summary that could drift out of sync. Every path below authenticates with an API key; talk to our team at /contact/ about Check API access for your organization.
How do I get the same results without an API key?
Use the free, no-account web pages linked in the table above — each runs the same underlying check in your browser. For AI agents, the AdminKit MCP server (see /developers/mcp/) is a free connector you self-host; talk to our team at /contact/ for a checkout and for API access.
What format is the contract in?
OpenAPI 3.1 in YAML (this particular file happens to be valid JSON too), the same contract the Check API implements.
Why does every endpoint need an API key?
The committed contract's only security scheme is an API key header (X-API-Key) — there is no unauthenticated route in the current spec, including the per-kind checks. The free tool pages and the MCP server's built-in fallback tools give an equivalent result without a key.
Want Check API access for your team?
Tell us what you want to automate and our team will scope Check API access — or a custom integration built by Netbase.