An agent usually calls these two before anything else. The examples use the made-up site example.com, and the values in them are invented to show the shape of an answer.

list_sites

Lists the sites of your organization. For each site it says whether the domain is verified for load testing, when the last load test ran, and what the site runs on. It also gives your organization’s load test limits. An agent calls it first, to see what it can work with and how many users one test may have.

  • Inputs: none.
  • Returns: sites, one entry per domain, and limits. A site has domain, verified, verification_method (dns or file), last_run (the run’s id, time and user count) and profile. The profile names the e-commerce platform, CMS, CDN and hosting, each with a confidence, and says whether the site looks like a shop. It is detected by the first browser of a load test or a dry run, so a new site has none yet. limits has max_users_per_test and max_concurrent_tests.
  • Cost and effect: free. It only reads.

Example

“Which of my sites can you load test?”

{
  "sites": [
    {
      "domain": "example.com",
      "verified": true,
      "verification_method": "dns",
      "last_run": { "run_id": "11111111-2222-4333-8444-555555555555", "at": "2026-11-02T03:00:12Z", "max_users": 100 }
    },
    { "domain": "shop.example.com", "verified": false }
  ],
  "limits": { "max_users_per_test": 500, "max_concurrent_tests": 1 }
}

verify_site

Checks that a domain belongs to your organization. A load test sends real traffic that can slow a site down, so Supervisor runs one only on a domain whose owner has proved it. If the domain is not verified yet, the answer says what to add, and the agent calls the command again once you have added it.

Accessibility checks, monitors and journey dry runs use a single browser and do not need a verified domain.

  • Inputs: url, a site address or a domain.
  • Returns: domain, verified and, when verified, the method. When not verified, add_one_of gives two choices: a DNS TXT record named supervisor-com.<your domain>, or a file at /supervisor-test.txt on the site. Both contain your organization’s id. If a file was found but is wrong, problem says what is wrong with it.
  • Cost and effect: free. When the record or the file is found, the domain is marked verified for your organization.

Example

“Verify example.com so we can load test it.”

{
  "domain": "example.com",
  "verified": false,
  "organization_id": "aaaaaaaa-bbbb-4ccc-8ddd-eeeeeeeeeeee",
  "add_one_of": {
    "dns": { "type": "TXT", "name": "supervisor-com.example.com", "value": "aaaaaaaa-bbbb-4ccc-8ddd-eeeeeeeeeeee" },
    "file": { "url": "https://example.com/supervisor-test.txt", "content": "aaaaaaaa-bbbb-4ccc-8ddd-eeeeeeeeeeee" },
    "note": "Add either one, then call verify_site again. DNS changes can take a few minutes."
  }
}

After you add the record, the same call answers "verified": true, "method": "dns".