### What happened?

On the **Agents** page of the Admin UI, every registered A2A agent shows the status badge **"Needs Setup"** even when the agent is correctly configured and has a virtual key linked to it (a key whose `agent_id` matches the agent).

Root cause: the agents page builds its "has key?" lookup by calling `keyListCall(...)` with **`size=500`**, but the `/key/list` endpoint validates `size` with `le=100`, so the request fails with **HTTP 422** and the lookup map ends up empty — so the badge falls through to "Needs Setup" for **all** agents.

**Frontend (Admin UI bundle)** — the badge logic:

```js n[e.agent_id]?.has_key ? Badge({color:"green", children:"Active"}) : Badge({color:"yellow", children:"Needs Setup"}) ```

…and the map `n` is built from a key list requested with `size=500`:

```js const { keys = [] } = await keyListCall(accessToken, null, null, null, null, null, 1, 500); const r = {}; for (const k of keys) { if (k.agent_id && !r[k.agent_id]) r[k.agent_id] = { has_key: true, ... }; } ```

**Backend** — `/key/list` rejects `size > 100`:

``` GET /key/list?size=500 → 422 {"detail":[{"type":"less_than_equal","loc":["query","size"], "msg":"Input shoul…