> For the complete documentation index, see [llms.txt](https://docs.playscript.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playscript.xyz/start/play-and-locking.md).

# PLAY and locking

PLAY is the stake. Locking it mints a script NFT and freezes an Amazon share count.

PLAY is the token you stake. Amazon shares are what a winning script pays.

A lock does four things:

1. You approve the match contract to spend your PLAY.
2. The stake moves into the shared vault.
3. The vault reserves the Amazon shares for a perfect script.
4. A script NFT is minted to your wallet.

You can lock only on a market that already exists, and only before kickoff. Each lock is its own script. One match can have many scripts. After kickoff, new locks close.

The share count is set in that same transaction. You pass the five picks and the stake. You do not pass a share amount. If the signed prices are missing, expired, or too far from the AMZN/USD feed, the lock does not use them.

If a fixture has no market yet, use Request market. The desk gets that match once. My scripts lists the scripts your wallet holds.


---

# 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.playscript.xyz/start/play-and-locking.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.