> For the complete documentation index, see [llms.txt](https://digital-landia.gitbook.io/agentic-pet-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digital-landia.gitbook.io/agentic-pet-whitepaper/economic-model-and-token-utility.md).

# Economic Model and Token Utility

The commercial viability of AgenticPet is built upon a decentralized economic structure incentivized by the AgenticPet Utility Token (PetAi). This model is designed to align the commercial interests of platform users, clinical data contributors, and infrastructure hosters across the distributed network.

### The AgenticPet Utility Token Model (PetAi) <a href="#the-agenticpet-utility-token-model-petai" id="the-agenticpet-utility-token-model-petai"></a>

The rationale for utilizing a tokenized model is to drive engagement across the distributed network. PetAi serves as the medium of exchange for platform services and as an economic incentive to maintain system integrity and performance.

### Token Utility Definition <a href="#token-utility-definition" id="token-utility-definition"></a>

The PetAi token is designed with multi-faceted utility to stabilize network activity:

* **Resource Access:** PetAi tokens are required as payment to access premium diagnostic services, especially those utilizing the high-throughput inference endpoints necessary to achieve 100k+ RPM capacity.
* **Data Rewards:** Tokens are used to financially compensate partner clinics and academic institutions for contributing de-identified VPHI or model updates via the Federated Learning network (Section VI).
* **Agent Staking/Reliability:** A critical utility is the requirement for agents or their operators to stake PetAi tokens. This stake serves as a financial performance bond, signaling commitment and reliability.

### Economic Sustainability and Growth Drivers <a href="#economic-sustainability-and-growth-drivers" id="economic-sustainability-and-growth-drivers"></a>

The staking mechanism is directly interwoven with the platform's safety and compliance architecture. Because agent performance variability is a systemic risk in distributed systems, and clinical errors pose direct patient safety concerns, the staking model translates economic capital into a verifiable performance commitment. The Compliance/Audit Agent's Explainable and Audit-Ready Logging (EARL) data serves as the immutable oracle for performance verification. If an agent consistently posts low confidence scores, fails to comply with security protocols, or contributes diagnostics that are flagged for factual inconsistencies, the associated PetAi stake can be penalized (slashed). This creates a self-correcting financial loop that ensures sustained, high clinical safety and operational integrity.


---

# 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://digital-landia.gitbook.io/agentic-pet-whitepaper/economic-model-and-token-utility.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.
