OpenAPI document

Returns an OpenAPI 3.1 document describing every public endpoint: its method, path, request body schema, response schema, the scope it needs (x-dhanu-scope) and the error codes it can return (x-dhanu-error-codes).

It needs no key and spends no credits.

curl https://api.dhanu.ai/api/pub/v1/openapi.json

The docs site serves the same document at docs.dhanu.ai/developer/openapi.json, and a Postman collection built from it, one folder per tag, bearer auth over an apiKey variable, a required-fields body example per request, at docs.dhanu.ai/developer/postman.json. Bruno and Insomnia import that collection too.

For an AI assistant, /llms.txt indexes every page and /llms-full.txt is the whole Developer section in one file; any page is Markdown with .md appended to its URL, and every reference page carries the same call as curl, Node and Python with a copy button.

What it is for

• Generating a client in a language we do not ship an SDK for (openapi-generator, openapi-typescript, kiota, …).
• Importing into Postman, Bruno or Insomnia to try calls by hand.
• Giving an agent the API: point a coding assistant at the URL and it can write a correct call.

How it stays true

The document is built from the same schemas the server validates requests with. A request body that the spec says is valid is one the server accepts, and a route that exists but is missing from the spec fails the server’s own test suite. It is never edited by hand.

Authentication is declared as the apiKey security scheme, an HTTP bearer token, and every operation except this one requires it.