What does a failed round look like?

Claude writes the challenger lines when a round starts, or the owner’s Codex subscription during early access. The test is error when no challenger is eligible to serve. A failed round has status error. That test is not served.

et status reads GET /api/runs/domain/:domainId/tests. The body is an array of runs. Each run has a tests array. Each test object has status. The failed test has "status":"error". The run object can still have "status":"running". et status copies a test into live when the test status is running, paused, or completed. et status leaves the error test out of live. A finished round is on What does a finished round look like?.

Empty allocations

The snippet loads variants from:

https://api.endlesstesting.ai/api/tests/by-url-allocations?url=

Put the page in the url query parameter. The call takes no token.

curl -fsS "https://api.endlesstesting.ai/api/tests/by-url-allocations?url=https%3A%2F%2Fexample.com%2F"

On HTTP 200 the body is a JSON array. An empty allocations array means no round is being served. [] is that array. An error test is not in the array. A failed round does not remove a winner from a finished test, so that winner can still be a row. A missing url or an invalid url is HTTP 400 with an error object. See Is a round live?.

Commands

<site> is the host (example.com) or the site id from et sites.

• et round start <site> [--url <page>] starts a round. Claude writes the challenger lines. --url sets the page. Without --url, the site host is the page.
• et status <site> shows what is live. A failed round is not in live.

et round start example.com
et status example.com

et round start can start another round when every test on the running run for that page is completed, stopped, or error. Any other status on that run, including running or paused, gets HTTP 409 and A running test run for this URL already exists for this domain.

Who writes the lines is on Who writes the lines?. The full list is on Commands.