> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/blockchain/ecosystem/powered-by-iotex-devices/pebble-tracker.md).

# Pebble Tracker

## Take Control of Your Data with Pebble!

For the IoT to reach its full potential, the ability for anyone to verify that the underlying data and code are trustworthy **is paramount**. As our world becomes more digitized by the day, **Pebble Tracker** establishes a new standard for trust based on transparency, reliability, and verifiability.

<figure><img src="https://content.gitbook.com/content/EyawgxYexImpo6OGzEiR/blobs/uj7fmfaS99ZOCjrhj7ze/image.png" alt=""><figcaption><p>Pebble Tracker</p></figcaption></figure>

IoTeX's Pebble meets the demand of applications that require strong data security, integrity protection, and multiparty trust across the entire supply chain. **Existing asset tracking solutions lack critical security features**, rendering them easily hackable and exposed to data corruption.

Pebble is a breakthrough blockchain-powered device that captures physical world data to give you   trusted information about real-world events in real-time.

## Who is Pebble for? <a href="#who-is-pebble-for" id="who-is-pebble-for"></a>

**Blockchain users** who own Pebble Trackers can register their devices to the IoTeX[ MachineFi Portal](http://portal.machinefi.com), fund their accounts, and start joining the new world of MachineFi Dapps and games to regain ownership of their data and start earning from providing it to third-party.

**Blockchain Developers** can use trusted data from Pebble devices in their smart contracts to build innovative *MachineFi* decentralized applications (DApps), or to enforce business logic in a trusted way, extending verifiability from data to code (smart contracts).

**Supply Chain developers** can use Pebble to establish a higher standard of **trust** for supply chain and transportation & logistics use cases with verifiable GPS, climate, motion, and light data. Pebble can serve as an **unbiased third party** in consortium scenarios where absolute trust is needed.

**IoT developers** who want to prototype Blockchain-based solutions, can develop their custom firmware for Pebble Tracker and take advantage of a decentralized network to receive, verify, and archive device data, ready to be used in Blockchain applications.&#x20;

## Interested building Pebble dApps? <a href="#interested-in-tech-specs" id="interested-in-tech-specs"></a>

[-> Check out how to use Pebble Tracker Data](/blockchain/ecosystem/powered-by-iotex-devices/pebble-tracker/query-pebble-data.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.iotex.io/blockchain/ecosystem/powered-by-iotex-devices/pebble-tracker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.