Give your LLM the right context.
Small, explicit documents that describe what the product actually accepts, returns, and cannot do.
Choose the right entry point
| Asset | Purpose |
|---|---|
| llms.txt | Short index for discovery and documentation navigation. |
| Overview Markdown | Capability contract, formats, outputs and limits. |
| OpenAPI | REST routes, authentication and request/response schemas. |
| MCP tool definitions | Actual two-tool input schemas. |
| Python example | Upload, start, bounded polling and authenticated download. |
A useful task to give your coding assistant
Copyable example
Read the RedactTool overview and API reference from this documentation site. Build a server-side integration to upload a DOCX file, replace detected sensitive information with placeholders, poll the job, and save its output. Use environment variables for the base URL and API key. Do not send a file until I provide an authorized input. Preserve job IDs and idempotency keys. Handle queued, running, completed, failed, expiry and rate limits. Do not assume an SDK, OAuth, webhook, or permanent API key exists.
An explicit capability boundary
| Available contract | Not promised |
|---|---|
| Per-job placeholders | Cross-file identity consistency or restoration mapping |
| PDF, DOCX, XLSX, TXT, MD | Arbitrary file types or all Office layout variants |
| Asynchronous status polling | Webhooks, SSE progress, or a cancellation endpoint |
| Bearer-authenticated MCP | Universal OAuth installation or remote URL import |
These documents describe the supported API and MCP contract. Read the limitations before integrating. Never put secret keys or sensitive files into a public prompt or issue.