Drivings API documentation
Drivings publishes UK and US driving-test data as a REST API, an MCP server and a typed SDK. Every operation is read-only or compute-only, which is why none of them need a key.
REST API
Four operations under /api/agent/v1: published guides, study options, the verified test-centre directory and a study-plan preview. GET /api indexes them with absolute URLs.
OpenAPI specification
OpenAPI 3.1.1, with typed responses on every operation and a shared error schema. It is the contract the SDK and the CLI are checked against.
MCP server
Streamable HTTP at mcp.drivings.com/mcp, exposing six tools and eight resources. Public tools answer anonymously; only a learner's own progress needs OAuth consent.
SDK and CLI
A typed TypeScript client and a drivings command-line tool covering the same four operations, with the market required on every call rather than guessed.
Authentication
The public API takes no credential. The one OAuth-gated capability advertises its authorization server through RFC 9728 protected-resource metadata.
Discovery documents
An ARD catalogue, an MCP server card and manifest, an RFC 9727 api-catalog and a plugin manifest, so an agent can decide whether to connect before it does.
When to use these tools
agents.md says what these tools are for and, as plainly, what they will not do: no tool books a test, takes a payment, gives legal advice or reports a named person's licence status.
/agents.mdThe boundary is the point
Results carry the date they were verified and the limits of their coverage. Both are meant to be repeated to the user rather than summarised away.