Overview
The public API surface is intentionally narrow. It supports the automation assessment, onboarding intake, and a simple health endpoint for discovery tooling.
Getting started
All endpoints live under https://leverwork.com/api/ and speak JSON: send a Content-Type: application/json header on POST requests and expect JSON responses back. There are no SDKs or client libraries to install — any HTTP client works. A good first call is GET /api/status, which confirms the API surface is reachable before you wire up a form or agent integration.
If you are building tooling against the API, start from the machine-readable spec at /.well-known/openapi.json rather than hand-coding request shapes — it is the source of truth for request and response schemas, and the human-readable notes on this page follow it.
Authentication
The public endpoints documented on this page do not require an API key or OAuth flow — they are the same endpoints the leverwork.com forms call, and they are validated server-side rather than gated by credentials. Submissions that fail validation return standard HTTP error codes.
This surface is intended for first-party use and agent discovery, not as a general-purpose integration platform. If you need programmatic access beyond what is listed here, get in touch and we will scope it with you directly.
POST /api/assessment
Submits the AI readiness assessment form and returns the generated assessment output used on the site.
POST /api/onboarding
Receives structured onboarding data for approved client onboarding flows. Requests require the same validation used by the public onboarding form.
GET /api/status
Returns a lightweight JSON health response that discovery agents can use to confirm the public API surface is reachable.
Agent Discovery
Leverwork publishes discovery artifacts for agents at well-known locations. These include the API catalog, agent skills index, and markdown negotiation support for HTML pages requested with Accept: text/markdown.