Skip to main content
Use a unique client_key for a logical create request whenever the route accepts one. Reuse the same key only to retry the identical work. A successful replay returns the resource already created; a key reused for different input returns a conflict instead of creating ambiguous work. Creating an evaluation, submission, or race entry starts work that may finish later. Store the returned IDs, then poll that resource’s status endpoint with backoff until it reaches a terminal state. A response with progress is an observation, not a final score or a completion guarantee.