> 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/submissions.md).

# Submissions

The submission contracts for the tournament, events, and model uploads.

**Recommended for tournament keys: auto-submit.** Upload your model as a `.pkl` once (`create_model`, `upload_model`, `set_auto_submit`) and the platform runs it and submits every round. Check `get_models`: `lane_active` is `true` when it will run, and `lane_note` explains when it will not. See [Model upload (.pkl)](/submissions/model-upload-pkl.md). Also submit your validation predictions to the historical leaderboard with `submit_validation_diagnostics`. The manual per-round submit below is the fallback.

How you submit predictions depends on which key type you hold. The table below maps each contract to the right lane.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tournament submissions</strong></td><td>The live Himalayas Futures round: submit predictions for one exped via JSON v2, pre-flight validation, batch submit, and status tracking.</td><td><a href="/submissions/tournament-submissions.md">Tournament submissions</a></td></tr><tr><td><strong>Event submissions</strong></td><td>Closed events: two upload lanes (practice board and event round), multipart form with model .pkl, caps, final selection, and the batch presign flow.</td><td><a href="/submissions/event-submissions.md">Event submissions</a></td></tr><tr><td><strong>Model upload (.pkl)</strong></td><td>Pickle a predict function and let the platform run it for you on every open round.</td><td><a href="/submissions/model-upload-pkl.md">Model upload (.pkl)</a></td></tr></tbody></table>

## Which contract applies

| Key scope                        | Submit lane                                         | Model .pkl required |
| -------------------------------- | --------------------------------------------------- | ------------------- |
| Full tournament (Himalayas tier) | `POST /api/v1/futures/submit/v2` (JSON)             | No                  |
| Event (hackathon)                | `POST /api/v1/event/predictions/upload` (multipart) | Yes, on both lanes  |
| Practice board (event keys)      | `POST /api/v1/diagnostics/upload` (multipart)       | Yes                 |

Call `get_started` (MCP) or `GET /api/v1/status` (REST) to learn which scope your key is in and which lane is open right now. It is mode-aware: it reads your key type and the event cadence, and returns the right next actions.


---

# 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/submissions.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.