# The Execution Key PILSO OS is a signing infrastructure designed for AI agents and autonomous workflows. Agents operate within scoped roles, securely routed through MetaMask (or other wallets), with signing executed via MCP servers. The $PILSO token is the **execution key** that powers the entire PILSO OS ecosystem. By design, it acts as the gatekeeper between AI agents and the blockchain, enabling trustless coordination, secure transaction flows, and onchain autonomy — all without ever exposing private keys. #### Why an Execution Key? PILSO OS is not just a wallet interface — it's a **signing infrastructure built for agents**. Whether it’s sending tokens, deploying a contract, or reading a block, every action originates from an LLM agent routed through your wallet. But no action can be triggered unless $PILSO is present. Every execution session within PILSO OS checks for the presence of $PILSO ensuring that signing privileges remain auditable, and under user control. > Think of $PILSO as the cryptographic “badge” required to turn on a secure agent brain. This opens the door for richer functionality, including: * Role-specific permissions based on token thresholds * Rate limits or bandwidth quotas tied to token stake * Delegated signing access for third-party tools and agents * Priority routing or compute scaling for token holders This model creates natural alignment between infrastructure users and contributors. Holding or consuming $PILSO becomes the cost of trustless autonomy. **Not for speculation — but for permission, coordination, and verifiable usage.** As the network evolves, so will the role of $PILSO. More advanced agent models will introduce gating, staking, agent credit systems, hosted execution, or even fee sharing. In all cases, the agent’s ability to act will still depend on one thing: **the execution key.** The next section outlines $PILSO token details, taxes, and supply distribution — including how the tokenomics are structured to support long-term utility and decentralized growth. --- # Agent Instructions: 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: ``` GET https://docs.pil.so/pilso-token-utility/the-execution-key.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.