> 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/staking/limits-and-eligibility.md). # Limits & eligibility Who can stake, how a plan turns into stakes, and where the live limits are. ## Who can stake * A **verified email**. Staking endpoints reject accounts without one. * A **linked wallet with its passkey added**. Link your Everesteer wallet on the Wallet page, then add its passkey on your account page. Setting up your strategy, funding it, saving a plan and withdrawing all need that passkey. The automatic rounds do not: they run inside the plan you saved. * A model with an **on-time submission** for the round. No submission, no stake that round. ## How a plan becomes a stake * **One stake per model per round.** A second position for the same model in the same round is refused. You can plan several models; each stake settles and is claimed separately. * **The amount** each round is the smaller of the plan's amount, the USDC your strategy holds, the round's maximum, and your stake limit. The platform cannot choose a bigger one. * **Partial fill.** If your strategy holds less than the plan, it stakes what it holds provided that reaches the round minimum. Below the minimum, the round is skipped and the USDC stays where it is. * **Round full.** When the round's pool has no room for the stake, it is not placed then, and the platform looks again later in the round, working the amount out afresh at that time. It is never reduced to fit. If the round fills up while a stake is already on its way, that model sits the round out. * **Per-round minimum and maximum, and the pool's room.** All are enforced by the staking contract and shown live on the Money tab. The limits change over time, so this page carries no numbers. * **Your stake limit.** Each stake needs a platform permit, issued inside your net returns so far (profits minus losses) minus what you already have staked, not your wallet balance. A loss lowers the limit by the amount lost, so you can never have more at stake than you have made. Check it on the Money tab; a request over it is refused and nothing is sent. ## Agent access You can allow an agent to change a model's plan. You set a limit on the per-round amount it may choose for each model, and it can save a plan only at or under that limit. Switching a model off is always allowed. The agent cannot withdraw, fund, claim for you or change who owns your strategy, and you can revoke it at any time. ## Payouts * Payouts go to your wallet, or stay in your strategy as idle balance until you withdraw them. There is no separate destination to set and no verification cooling period. * If a round stalls for an extended period with no activity on it, you can withdraw a stake directly from the Money tab, without waiting for it to resolve. ## What a round can do to a stake The clip applied to a settled stake is symmetric and wide. A winning round can add to your stake; a losing round can take from it, and a single round can take an **entire** stake. Treat every staked dollar as at risk. ## What runs on-chain Stakes, limits and settlement are enforced by a staking contract, not by a database. Your strategy is its own contract, owned by your wallet. The Wallet page names the network your wallet uses, so you can verify it before you send USDC. Everything the platform tells you about a round's limits can be checked against the chain. {% hint style="info" %} Event staking is a different flow, still funded through a deposit address with its own verified-wallet and withdrawal rules. See [Event staking](/events-and-hackathons/event-staking.md). {% endhint %} {% hint style="warning" %} Read the live per-round limits from the platform rather than from this page. They change over time, and the on-chain enforcement is what counts. {% 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/staking/limits-and-eligibility.md?ask=&goal= ``` `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.