# Admin controls: a census of 126 listings

> Source: The Agents Index — https://theagentsindex.com/blog/admin-policy-census (sourced research)
> By The Agents Index Editorial · Published 2026-09-16 · Updated 2026-09-16

_55 of 126 listings answer yes for “Admin controls”. Counted from our own datasheet, with the query that reproduces every figure._

## Admin controls, across 126 settled listings

Of the 126 Published listings whose datasheet settles “Admin controls”, the largest group is “Qualified” at 64 (51%). Measured 2026-09-16.

| Listings | Count | Share of 126 |
| --- | --- | --- |
| Yes | 55 | 44% |
| Qualified | 64 | 51% |
| No | 3 | 2% |
| Does not apply | 2 | 2% |
| Not established | 2 | 2% |

Denominator: 126 Published listings whose datasheet settles “Admin controls”. Method: Counted from the stored datasheet answer for “Admin controls” across every Published listing, all of which have a recognised stored answer on that row.

## The population

126 listings in this index are Published. This is the population as of 2026-09-16. 126 of the 126 published listings in this index carry a settled answer for “Admin controls”. That row asks: Can an admin constrain what the agent may do? Every listing in the index is settled on this row, so nothing is left out.

## Findings

1. 55 of the 126 settled listings answer “Yes” for “Admin controls”. That is 44% of the settled set.

2. 64 of the 126 settled listings answer “Qualified” for “Admin controls”. That is 51% of the settled set.

3. 3 of the 126 settled listings answer “No” for “Admin controls”. That is 2% of the settled set.

4. 2 of the 126 settled listings answer “Does not apply” for “Admin controls”. That is 2% of the settled set.

5. 2 of the 126 settled listings answer “Not established” for “Admin controls”. That is 2% of the settled set.

1 of those yes answers is Codex CLI, which still answers yes for “Admin controls”. Its [listing](/codex-cli) carries the stored answer and links to [the source recorded for it](https://learn.chatgpt.com/docs/enterprise/managed-configuration). This is one worked example, not an independent audit of every source in the census.

## What we counted, and how

Each figure above is a count over the “Admin controls” row of the listing datasheet, taken from the same stored answer the listing page renders. The denominator is the 126 listings whose answer is settled, meaning one of yes, qualified, no, does not apply, not established. On this row that is the whole index, because every listing has a recognised stored answer. Every number here is stored with the read-only query that reproduces it and re-run every sixty seconds against the live corpus, so a figure that stops reproducing surfaces as drift rather than as a stale sentence nobody notices. Our full method covers how a datasheet row is settled in the first place.

## Limitations

This counts stored datasheet answers, not independently tested capabilities. A sourced answer can record a vendor statement or our reading of published evidence; this census does not re-fetch those sources. “Not established” means we have not established an answer. That can reflect vendor nondisclosure, blocked evidence, or unfinished research, not a no. An absent or unrecognised answer is excluded rather than treated as a researched finding. The figures are restated when the stored corpus changes; the date above is the count used for this published version, not a new verification of the vendors.

---

Tags: data-report, census