Use Dockt with coding agents

Dockt publishes documentation in formats that coding agents can read without scraping page layouts:

• /llms.txt is a compact index and recommended entry point.
• /llms-small.txt contains the most important integration context.
• /llms-full.txt contains the complete documentation set.
• OpenAPI JSON is the source for exact paths, fields, enums, permissions, and response schemas.

Give your coding agent a prompt

Replace the workflow and language placeholders, then give this prompt to your coding agent:

Implement a backend integration with the Dockt API for WORKFLOW.

Read https://docs.dockt.com/llms.txt first. Use
https://api.dockt.com/openapi.json as the source of truth for every endpoint,
field, enum, permission, and response type. Do not invent fields or rely on
internal Dockt implementation details.

Requirements:
- Use LANGUAGE and the existing HTTP/client patterns in my application repository.
- Use only Dockt's public documentation and OpenAPI contract.
- Read the bearer token from DOCKT_API_TOKEN and call https://api.dockt.com.
- Keep credentials, uploaded files, and webhook secrets on the server.
- Send Idempotency-Key on supported create and upload requests.
- Treat document processing as asynchronous and handle every documented state.
- Parse non-2xx responses as application/problem+json.
- Log x-request-id without logging secrets or document contents.
- If receiving webhooks, verify the signature over the raw request body,
  enforce the five-minute replay window, and deduplicate by event ID.
- Add focused tests for the response parsing and retry logic you implement,
  plus webhook verification when applicable.

Before writing code, summarize the API operations and public states the
integration will use. After implementation, run the repository's checks.

Use verify a standalone document or complete a worker assessment for WORKFLOW. Use your application’s implementation language for LANGUAGE.

Keep generated code aligned

Generate client types from the OpenAPI document when your toolchain supports OpenAPI 3.1. Pin generated output to a reviewed contract revision in your repository, and review schema changes before updating it.

Do not ask an agent to infer undocumented fields from examples. Examples explain a workflow; the OpenAPI schema defines the request and response contract.