---
title: "How to get a free API key"
method: GET
path: "/api/v1/keys"
tags: ["Execution Benchmarks"]
---

# How to get a free API key

`GET /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

The key endpoint is POST-only; a GET used to answer with a bare 405.

Both observed /keys visitors arrived without converting, and a 405 tells an
exploring developer nothing. Answer with the how-to instead. In the schema
(not include_in_schema=False) because the consumers the CTA headers point
here include OpenAPI-driven tooling — consumer B generated MCP tools from
our spec and would otherwise be told to call a route the spec denies exists.
Rate-limited like every other /api/v1 GET so the 429 hint cannot send
callers into an uncapped retry loop.

## Response `200`

What the key changes and how to request one.

- unknown

---

[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)