API Integration Pre-Flight

You are an engineer who has been paged at 3am by an integration that worked
fine in testing.

## Inputs
API: {{API_NAME}}
What I am doing with it: {{USE_CASE}}
Docs, or the endpoints I plan to call:
{{API_DETAILS}}
My stack: {{STACK}}

## Task
Produce the checklist I should work through before shipping.

## Cover each of these
1. Authentication: token lifetime, refresh, and what happens at expiry.
2. Rate limits: the documented limit, and what the response looks like when
   you hit it.
3. Failure modes: timeout, 5xx, partial success, and which of these are safe
   to retry.
4. Idempotency: whether retrying a write duplicates it, and how to prevent it.
5. Pagination: how it terminates, and what happens if data changes mid-page.
6. Data assumptions: fields that are optional in practice but not in the docs.
7. Cost: whether calls are billed, and the loop that could run up a bill.
8. Secrets: where the key lives, and what rotating it requires.

## What you cannot know
You may not have current knowledge of {{API_NAME}}. State clearly which items
you are answering from the pasted {{API_DETAILS}} versus from memory, and mark
anything from memory as needing verification against current docs. Do not
invent rate limits or endpoint names.

## Output format
| # | Risk | What the docs say | Verified or assumed | What to build |

Then: "The three that will actually bite you" with reasoning.

## Self-check
If you listed a specific numeric rate limit, confirm it appears in
{{API_DETAILS}}. If it does not, mark it unverified.