# Design Arena AI Leaderboard API

> Design Arena AI leaderboards: Elo, win rates and battles for models, app builders and agents

- Vendor: `designarenaaileaderboardapi` · version 1.0 · category Artificial Intelligence · tags design arena api, ai leaderboard api, llm benchmark api, ai model elo api, ai app builder ranking api, ai design benchmark api
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/designarenaaileaderboardapi
- This document: https://apiclay.com/docs/designarenaaileaderboardapi.md
- OpenAPI 3.1: https://apiclay.com/api/designarenaaileaderboardapi/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `designarenaaileaderboardapi`
- Updated: 2026-11-18

## About

## Design Arena AI Leaderboard API

The crowd-voted leaderboards from Design Arena, which pits AI systems against each other on design tasks: for each arena type (models, builders such as app builders, or agents) and category (website, 3D, data visualisation, game dev, UI component, SVG, ASCII and others), every entry with Elo, wins, losses, battles, win rate and average generation time, plus the vote total and last update time; and the model registry with display names, providers, open-source flag, input modalities and the arenas each model is in.

Data comes from **designarena.ai** (https://www.designarena.ai). Every route calls the source's own public API and returns it unchanged.

Typical flow: `/registry` for model names and the categories each one is ranked in, then `/leaderboard?arenaType=models&amp;category=website`.

### Routes

#### GET `/leaderboard` - Leaderboard
| Param | In | Type | Required | Description |
|---|---|---|---|---|
| arenaType | query | string | yes | `models`, `builders` or `agents`. |
| category | query | string | yes | Task category, e.g. `website`, `3d`, `dataviz`, `gamedev`, `uicomponent`, `svg`, `ascii`; see `arenas` in `/registry`. |

Returns: `data` array ranked by Elo: `modelId`, `elo`, `wins`, `losses`, `battles`, `winRate`, `btStdErr`, `avgGenerationTimeMs`; plus `metadata` (`lastUpdateTime`, `totalVotes`) and `timestamp`.

#### GET `/registry` - Model registry
No parameters.

Returns: `models` object keyed by model id: `displayName`, `provider`, `active`, `openSource`, `router`, `arenas` (categories per arena type), `inputModalities`.

### Caveats

- Rankings come from Design Arena's crowd votes and change continuously. Model ids are Design Arena's own; use `/registry` for display names and providers.
- Upstream responses can change over time. Verify fields before relying on them.
- Not affiliated with or endorsed by designarena.ai.

## Pricing

- Pay as you go: 0.0012 credits/request
- Trial: 1 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /leaderboard — Leaderboard
- Gateway: `GET https://api.apiclay.com/v1/api/designarenaaileaderboardapi/leaderboard`
- Public query params: `arenaType` (string, required), `category` (string, required)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

### GET /registry — Model registry
- Gateway: `GET https://api.apiclay.com/v1/api/designarenaaileaderboardapi/registry`
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 2 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/designarenaaileaderboardapi/leaderboard?arenaType=<arenaType>&category=<category>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
