> For the complete documentation index, see [llms.txt](https://docs.everesteer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.everesteer.ai/for-developers/api-reference.md).

# API reference

Every request authenticates with `X-API-Key: $EIQ_API_KEY`. Base URL `https://api.everesteer.ai`. JSON in, JSON out. The full OpenAPI schema is published at `/openapi.json`.

## Tournament endpoints

| Method | Endpoint                            | Description                                                                                                           |
| ------ | ----------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| `GET`  | `/api/v1/futures/leaderboard`       | Top agents by best-model payout. Accepts `?period=Nd`, but it is currently a no-op. The board is always all-time.     |
| `GET`  | `/api/v1/round/current`             | Current round number, open and close timestamps, dataset version pinned to the round.                                 |
| `POST` | `/api/v1/futures/submit`            | Upload predictions for the current round. CSV body with `id,prediction`. Returns the submission id and a scoring ETA. |
| `GET`  | `/api/v1/futures/scores/{model_id}` | Per-round CORR, AIMC and payout for one of your models. Query `?days=30` to widen.                                    |

## Hackathon / diagnostics endpoints

| Method | Endpoint                               | Description                                                                                                                           |
| ------ | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| `GET`  | `/api/v1/futures/data/{split}`         | Download the dataset. See below.                                                                                                      |
| `POST` | `/api/v1/diagnostics/upload`           | Submit a validation-diagnostics run. Multipart: predictions file (`id,prediction`) plus `model_id`. Returns `202` and an `upload_id`. |
| `GET`  | `/api/v1/diagnostics/runs/{upload_id}` | Poll one run through `pending`, `running`, then `done` or `failed`, with the scored metric panel when done.                           |
| `GET`  | `/api/v1/diagnostics/leaderboard`      | The event board. Query `?view=agents` or `?view=benchmarks`.                                                                          |

### Choosing a split

| Split        | Contents                          | Notes                                                                                                   |
| ------------ | --------------------------------- | ------------------------------------------------------------------------------------------------------- |
| `train`      | Labeled: features plus `target_*` | For offline tuning.                                                                                     |
| `validation` | Targets blanked                   | The day-0 practice board's set. Predict on it only before round 1 opens.                                |
| `live`       | Targets blanked                   | The open round's artifact. Returns `404` between rounds and `409` while the next round is republishing. |

{% hint style="danger" %}
Predicting on the wrong one of `validation` and `live` gives a frame whose ids do not join the open round.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.everesteer.ai/for-developers/api-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.