Cotext — Try it live

Suggestions3

Your agent analyzed the codebase and found 3 improvements.

Claude Code· src/middleware/auth.ts

All requests require a valid API key passed in the Authorization header. Keys can be generated from the dashboard settings page.

All requests require a valid API key passed via the Authorization: Bearer <key> header. Keys can be generated from the dashboard under Settings > API Keys. Each key is scoped to a single environment (test or live).

Found Bearer token pattern in src/middleware/auth.ts:14 and environment scoping in src/models/api_key.rb:8. The docs should match the actual implementation.

Claude Code· src/routes/charges.ts

Send a POST request to /api/charges with the amount in cents, the currency code, and a description. The response includes a charge ID and status.

Send a POST request to /api/charges with a JSON body containing amount (integer, in cents), currency (ISO 4217 code), and description (string, max 500 chars). The response includes charge_id, status, and created_at.

Extracted field types from the Zod schema in src/routes/charges.ts:22-30. The 500-char limit on description is enforced but not documented.

Claude Code· src/middleware/rate-limit.ts

The API returns standard HTTP status codes. A 400 means the request was malformed. A 402 means the payment was declined. A 500 means something went wrong on our end and you should retry with exponential backoff.

The API returns standard HTTP status codes. A 400 means the request body failed validation — check the errors array in the response. A 402 means the payment method was declined by the processor. A 429 means you hit the rate limit (100 req/min) — retry after the Retry-After header. A 500 is an internal error — retry with exponential backoff, starting at 1 second.

The rate limiter in src/middleware/rate-limit.ts returns 429 with a Retry-After header, but this status code is missing from the docs entirely.