# Integrate with an AI coding tool

## Supply the right context
Give your coding tool `openapi.json`, this guide, the quickstart and CONTRACT-GAPS.md. Use `llms-full.txt` for a single plain-text documentation bundle. These are documentation resources, not a promise of search-engine ranking or an agent runtime.

Never paste a real API key, client document or production recipient list into a shared prompt. Configure credentials locally after reviewing generated code.

## Starter prompt
```text
Build a server-side UploadLetters integration from the attached curated OpenAPI contract and guides.
Use x-api-key authentication and the public /batches flow.
Create draft -> upload multipart letters[] -> verify all recipients and background processing -> explicit fulfillment -> retrieve records.
Keep fulfillment a separate deliberate operation because it queues wallet charging and mailing.
Do not invent endpoints, SDKs, service codes, sandbox behavior, webhooks, idempotency support or undocumented enum values.
Reject unknown payload fields locally. Reconcile partial acceptance and every intended recipient. Preserve batch_id for later requests.
Implement bounded read polling and a visible unresolved state after ambiguous mutation responses. Never replay a charge or create automatically.
Handle null records and expiring artifact URLs. Distinguish First-Class scan visibility from carrier-confirmed delivery.
Stop and identify a contract gap when the provided specification conflicts with a required workflow.
First show the proposed data flow and payloads. Do not execute production requests.
```

## Review generated output
Check exact field spelling, multipart construction, filename mapping, money units, expected-recipient reconciliation and the explicit fulfillment boundary. A compiling client is not proof that it sends the correct documents to the correct people.

## Modern documentation delivery
Publish crawlable HTML with sidebar navigation, search, anchored headings, copyable examples and a download of the versioned OpenAPI file. Provide Markdown views, `llms.txt` and the combined text bundle. Interactive API tools should make production submission unmistakable and never auto-run a fulfillment example. A documentation host's AI features do not add capabilities to the UploadLetters API.