---
title: "Get a free API key (higher rate limits)"
method: POST
path: "/api/v1/keys"
tags: ["Execution Benchmarks"]
---

# Get a free API key (higher rate limits)

`POST /api/v1/keys`

## Request

- Base URL: `https://cleartracedata.com` (the document declares no server; this is the origin it was published from)
- URL: `https://cleartracedata.com/api/v1/keys`
- Auth: none declared

**Free, opt-in API key. Raises your rate limits; changes nothing else.**

Every `/api/v1` endpoint stays open without a key and returns the same data
either way. There is no paid tier and no gated data behind this. The only thing a
key changes is your ceiling, which is multiplied by
`rate_limit_multiplier` on every endpoint.

We ask for an email because usage is logged against a one-way hash of your IP and
we have no way to reach you otherwise. `use_case` is optional and is the field we
actually read.

The key is self-contained, so it keeps working across our deploys and restarts.
Keep it: we cannot show it to you again.

## Request body

- ApiKeyRequest
  - `email` string, required: Where to reach you. Required.
  - `name` string: Optional. Who you are.
  - `company` string: Optional. Where you work.
  - `use_case` string: Optional, and the most useful field: what you are building.

## Response `200`

A key to send as X-API-Key, and what it grants.

- ApiKeyResponse
  - `api_key` string, required: Send as the X-API-Key header.
  - `tier` string, required: Which tier this key grants.
  - `rate_limit_multiplier` integer, required: How much your per-endpoint ceiling is multiplied by.
  - `note` string, required: What the key does and does not change.

---

[API](https://skmtc.dev/cleartracedata/apis/cleartrace-api.md) · [All operations](https://skmtc.dev/cleartracedata/apis/cleartrace-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cleartracedata/apis/cleartrace-api/revisions/2073a5a38ab5?raw)