Turn an API contract into a small client design that handles retryable failures, deadlines and idempotency deliberately.
No public result for version 1 yet
Version 1 · 3 variables · 3 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
Runtime, installed HTTP library and execution style. Default: Python 3.12; httpx is already installed; synchronous client.
Endpoint behavior, authentication and retry/idempotency guarantees. Default: GET /v1/status returns 200 JSON with status:string. 429 may include Retry-After in seconds; 401 is permanent. Base URL and bearer token are caller supplied.
Explicit timeout, retry and escalation requirements. Default: Total operation budget 10 seconds; at most 3 attempts. Retry transient connection failures and 503 responses. Do not retry other 4xx responses except 429.
Implement a small API client for Python 3.12; httpx is already installed; synchronous client. using this contract:
GET /v1/status returns 200 JSON with status:string. 429 may include Retry-After in seconds; 401 is permanent. Base URL and bearer token are caller supplied.
Operational policy:
Total operation budget 10 seconds; at most 3 attempts. Retry transient connection failures and 503 responses. Do not retry other 4xx responses except 429.
First separate retryable failures from permanent errors according to the contract. Explain how the total deadline, per-attempt timeout, maximum attempts, backoff and jitter interact. Retry writes only when their documented idempotency behavior makes that safe; mark unknown behavior.
Provide focused code with explicit error types, cleanup and cancellation where supported. Keep credentials supplied by the caller and out of logs. Respect documented rate-limit or retry guidance without inventing header semantics.
Finish with expected test scenarios for timeout, rate limit, malformed response and retry exhaustion, plus assumptions requiring verification. Do not claim execution or guaranteed exactly-once delivery.No public examples yet for version 1
Curated prompt only. No example output or model test is attached; model compatibility has not been verified. Default inputs are illustrative practice material; replace them with your own facts and context.
Reports go to moderators and are never shown publicly.
No public results yet
Break a dependency replacement into reviewable stages with compatibility checks, exit criteria and realistic rollback limits.
No public results yet
Define realistic traffic, workload data, measurements and stopping rules for an authorized performance test.
No public results yet
Find source-visible labeling, semantics and keyboard risks, while separating code findings from checks that require a browser.
No public results yet
Map feature assets, trust boundaries and data flows to concrete threats, existing controls and targeted verification tasks.
No public results yet
Interpret supplied plan evidence and prioritize query or index experiments without inventing costs or speedups.
No public results yet
Check whether keys, constraints and relationships actually enforce the application's stated data rules.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.