Sandbox inputs
With a test key, any input.text that starts with sandbox: answers from a fixed example. It spends no credits and returns the same body every time, except id and created_at. An unknown entry answers 422 validation_failed.
| Input | Answer |
|---|---|
sandbox:priced | 200, a priced fence of 100 linear feet. |
sandbox:needs_detail | 200, the same fence with no size and the question to ask. |
sandbox:unsupported | 200, a job Hometown does not price. |
sandbox:unclear | 200, a description too vague to price. |
sandbox:rate_limited | 429 rate_limited, with Retry-After. |
sandbox:insufficient_credits | 402 insufficient_credits. |
sandbox:content_rejected | 422 content_rejected. |
sandbox:timeout | 503 model_unavailable, with Retry-After. |
sandbox:async | 202 processing, then priced within seconds, with estimate.completed. |
sandbox:failed | 202 processing, then failed, with estimate.failed. |
The four 200 answers are copies of what the estimator returned for real descriptions of these jobs. The two 202 entries rehearse async estimates whatever mode says, and send their event to the test webhook endpoints that listen to estimate.completed or estimate.failed.
Daily cap on test keys
The test keys of an account make up to 200 estimates a day together, sandbox inputs included. Past that, they answer 429 with the code sandbox_daily_cap_reached until midnight.
A test key also prices real descriptions, within the same cap. A sandbox: input with a live key answers 422 with the code sandbox_input_on_live.