# Quickstart

**Start with the working offline demo.** The production SDK, live financial checks, and hosted P21 MCP/API service are still in development.

## For an agent

Read [/agents/start.md](https://proof21.xyz/agents/start.md) on the website. The guide states the current capabilities and permissions. Ask your agent to summarize what exists and whether it fits your workflow before installing or running anything.

Reading a guide is not permission to execute code, disclose secrets, connect a wallet, or spend money. Those decisions remain with the operator.

## For a developer

Open [/demo/](https://proof21.xyz/demo/), download and inspect `proof21-demo.mjs`, and run it with Node.js 22 or newer:

```bash
node proof21-demo.mjs
```

Four synthetic examples demonstrate a matching instruction, a wrong recipient, missing evidence, and a tampered signed report. No package installation, network, wallet, API key, or file write is needed.

From a checkout that includes the example, the repository root also supports:

```bash
npm run demo
npm run test:demo
```

These run local scripts; there is no published P21 npm package. The [offline demo specification](https://proof21.xyz/docs/start/offline-demo/) explains the restricted format and limitations.

## What comes next

The production work is still to implement supported source adapters, request binding, freshness/finality policies, complete negative fixtures, and reviewable producer/consumer interfaces. Bitcoin selection remains experimental. The website's [API contract](https://proof21.xyz/docs/build/api/) is design-only, not an endpoint to invoke.

For a partner pilot, bring a sanitized instruction, expected outcome, evidence, and a known failure case. Begin with the [pilot playbook](https://proof21.xyz/docs/partners/pilot/).

<!-- p21-source-payment-v08 -->

## Commercial activation and implementation status

NAT and USDC are both required for the initial commercial-launch acceptance test. Public documentation, source code and policy fixtures are not live payment endpoints. The static payment-policy resource lists required launch methods with `enabled: false`, no recipient and no live endpoint until each rail passes end-to-end settlement, accounting, failure/reorganization, security and owner-approval gates. Do not advertise a USDC-only release as the completed initial payment scope.

No token has been issued, no source element is announced, and no mainnet inscription, customer charge, treasury swap or wallet authorization is performed by this release. Production service availability remains separate from website publication. No Trac partnership, hosted SLA or independent cryptographic audit is implied.


[1] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/digital-elements/.element-registry

[2] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/src/index/updater/inscription_updater/tap/ops/dmt_element.rs

[3] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/nat-use-cases/usdnat-method-1-live

[4] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/non-arbitrary-tokens-nats/nat-token-transfer

[5] https://docs.x402.org/core-concepts/network-and-token-support

[6] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/README.md

[7] https://arxiv.org/abs/1605.04559