Timeouts on the client and on the service
2026-03-28 · Using the API
Give the client at least a few seconds. The service skips work the caller has already abandoned.
A text solve is far under a second of model time. Your HTTP client should still allow several seconds for a cold start. On Lambda a cold start of the API container is on the order of 12 seconds. The 15-minute warmer exists to avoid that on the common path.
Set the client timeout above that if you call infrequently. A one-second timeout will look like a failure when the process is waking up.
The solver itself skips work older than its deadline so it does not spend a credit of CPU on a client that already disconnected. You will see timeout or a 503 in those cases, and you are not charged.
Background tasks have a longer budget, about 90 seconds, and the sweeper refunds anything stuck processing after a restart.
Ready to call it? Start with the quickstart, the API guide, or pricing.