# KineticVM

> Identity, spending limits, and signed attestations for physical AI devices on Monad.

- [Overview](https://docs.kineticvm.xyz/index.md): KineticVM gives physical AI devices an onchain identity, a wallet with hard spending limits, and a signed, verifiable record of everything they do.
- [Quickstart](https://docs.kineticvm.xyz/quickstart.md): Install KineticVM, give a device an onchain identity, fund its vault, and talk to it from Telegram in about ten minutes.
- [How it works](https://docs.kineticvm.xyz/how-it-works.md): The architecture of KineticVM: what runs on the device, what lives on Monad, and how a machine moves from first boot to a verifiable history.
- [Identity](https://docs.kineticvm.xyz/concepts/identity.md): How a machine becomes an ERC-8004 agent owned by a person, and how its device key is bound to that identity without ever controlling it.
- [Device Vault](https://docs.kineticvm.xyz/concepts/vault.md): How a machine holds and spends money: per-agent balances, per-transaction and rolling daily caps, a recipient allowlist, a pause switch, and owner-signed loosening.
- [Attestations](https://docs.kineticvm.xyz/concepts/attestations.md): How a device signs what it did, how KineticAttestor verifies it, and how the result becomes a public ERC-8004 validation anyone can query.
- [State](https://docs.kineticvm.xyz/concepts/state.md): Where every fact about a KineticVM device lives, which copy wins, and how plugins keep their own durable state.
- [Operation records](https://docs.kineticvm.xyz/concepts/records.md): How a builder declares the shape of a machine's work, and how each completed operation becomes one canonical line that is signed, attested, stored, and later sellable.
- [Telegram owner commands](https://docs.kineticvm.xyz/operate/telegram.md): Run a claimed device from the paired Telegram chat: check status, pause, change caps, approve recipients, fund, withdraw, and sell data.
- [Funding and gas](https://docs.kineticvm.xyz/operate/funding.md): Put MON in a device's vault, understand how the device pays its own gas, and get funds back out.
- [Ownership](https://docs.kineticvm.xyz/operate/ownership.md): Sell or hand over a machine by transferring its agent NFT, revoke a device you no longer trust, and rotate a device key.
- [Building on KineticVM](https://docs.kineticvm.xyz/build/overview.md): The four building blocks a builder uses to turn a generic KineticVM device into a specific machine: plugins, SOPs, skills, and firmware.
- [Plugins](https://docs.kineticvm.xyz/build/plugins.md): Write tools as sandboxed WebAssembly components, declare what they may touch, build them, and install them onto a device.
- [SOPs](https://docs.kineticvm.xyz/build/sops.md): Standard operating procedures: triggered, ordered steps that call tools, with approvals, branching, retries, and deterministic execution.
- [Skills](https://docs.kineticvm.xyz/build/skills.md): Markdown guidance the model reads so it knows when and how to use your tools, without becoming code itself.
- [Hardware and firmware](https://docs.kineticvm.xyz/build/hardware.md): How a board talks to the device over serial, which commands it must answer, and how a local event starts a procedure.
- [Data marketplace](https://docs.kineticvm.xyz/marketplace/overview.md): How an owner sells a device's attested operation records, and how a buyer checks them on Monad before paying.
- [Data listing](https://docs.kineticvm.xyz/marketplace/listing.md): Publish a device's operation records from Telegram or from the sell_data tool, and what the marketplace checks before the listing goes up.
- [Buyer verification](https://docs.kineticvm.xyz/marketplace/verification.md): Check every row of a listing against the ERC-8004 Validation Registry on Monad, then pay and unlock the files.
- [Trust and safety](https://docs.kineticvm.xyz/security.md): What KineticVM guarantees, what it deliberately does not, and the controls an owner has when something goes wrong.
- [Tutorials](https://docs.kineticvm.xyz/tutorials/overview.md): Three walks through a real device: a vending procedure, a first plugin, and a dataset you can check on Monad yourself.
- [Vending machine](https://docs.kineticvm.xyz/tutorials/vending-machine.md): Turn a claimed device into a four-slot vending machine: a record schema, a procedure, a keypad event, and an attestation for every sale.
- [First plugin](https://docs.kineticvm.xyz/tutorials/first-plugin.md): Scaffold a plugin package, compile it to wasm32-wasip2, and install the tools onto a device.
- [Verify a dataset](https://docs.kineticvm.xyz/tutorials/verify-dataset.md): Take one attested operation line and check it against the ERC-8004 Validation Registry on Monad testnet.
- [Smart contracts](https://docs.kineticvm.xyz/contracts/overview.md): The three KineticVM contracts, the ERC-8004 registries they sit on, and what each one is allowed to do.
- [Deployments](https://docs.kineticvm.xyz/contracts/deployments.md): Monad testnet addresses for the KineticVM contracts and the ERC-8004 registries they use, with the transactions that created them.
- [KineticRegistry](https://docs.kineticvm.xyz/contracts/kinetic-registry.md): The contract that mints an ERC-8004 agent to its owner and binds exactly one device key to it.
- [DeviceVault](https://docs.kineticvm.xyz/contracts/device-vault.md): The per-agent MON vault: caps, allowlist, pause, owner withdrawals, and device gas top-ups.
- [KineticAttestor](https://docs.kineticvm.xyz/contracts/kinetic-attestor.md): The ERC-8004 validator that checks a device-signed action proof and writes response 100 to the Validation Registry.
- [ERC-8004](https://docs.kineticvm.xyz/contracts/erc-8004.md): Which parts of the agent identity standard KineticVM uses, and which parts this deployment leaves alone.
- [CLI](https://docs.kineticvm.xyz/reference/cli.md): The kinetic commands that set up a device, run it, and build on it.
- [Configuration](https://docs.kineticvm.xyz/reference/configuration.md): The config.toml fields that point a device at Monad, the marketplace, its records, and its boards.
- [Agent tools](https://docs.kineticvm.xyz/reference/agent-tools.md): The tools a KineticVM agent uses to read its identity, spend, attest, sell records, and run procedures.
- [Marketplace API](https://docs.kineticvm.xyz/reference/marketplace-api.md): The HTTP endpoints a device and a buyer use to list records, verify them, and unlock a purchase.
- [FAQ](https://docs.kineticvm.xyz/resources/faq.md): Short answers to the questions that come up while claiming, funding, and selling a device's records.
- [Glossary](https://docs.kineticvm.xyz/resources/glossary.md): The words KineticVM uses for identity, money, records, and the software around a device.
- [Changelog](https://docs.kineticvm.xyz/resources/changelog.md): What shipped in the 0.8 device releases.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.