# Operate lifecycle, usage, and failures

> Monitor operation status, settled usage, billing reads, webhooks, idempotency, retries, and manual-review outcomes.

Canonical: https://entirefeed.com/docs/operate

Every paid request has a status and a cost lifecycle. Estimate first, then monitor the request until it finishes; final usage shows the amount charged or released.

## Choose an operating guide

- [Billing and usage](/docs/operate/billing-and-usage) explains available balance, reservations, final usage, and ledger reads.
- [Webhooks](/docs/operate/webhooks) covers registration, signature verification, event handling, and delivery retries.
- [Idempotency and rate limits](/docs/operate/idempotency-and-rate-limits) prevents duplicate paid work and retry storms.
- [Errors and manual review](/docs/operate/errors-and-manual-review) maps failures to safe next actions.

## Read the current status

Read the generation or workflow-run resource until it reaches a terminal state. Do not infer completion from elapsed time or a local UI state. Treat `manual_review` as a deliberate outcome that requires operator attention.

## Make writes idempotent

Use a stable `Idempotency-Key` for each intended create or retry. Reusing a key for the same request returns the existing operation; changing the request while reusing a key is an integration error.

Start with [Quickstart](/docs/get-started/quickstart) to see the lifecycle and settled usage fields together. Public billing endpoints are read-only; top-ups and payment management remain signed-in Console actions.