← Authority Center
MONEY MUSK · DEVELOPER KIT

Build under
human authority.

Give an agent a precise permission. Check every proposed action. Keep a verifiable record of the decision.

Try Permission Preview →Run the developer quickstart ↓
REFERENCE RELEASE · AUTHORITY 0.2 / WITNESS 2
GRANT

Express the exact boundary.

Pin the human root and delegate key. Bound the recipient, total, expiry and delegation.

VERIFY

Use the same evaluator.

Preview without consumption. Reserve under a transaction using the same authorization checks.

REVOKE

Stop the next attempt.

Check current revocation state at the protected boundary. A completed action cannot be undone by revocation.

PROVE

Carry evidence with you.

Verify signed decisions and committed history against separately trusted keys. Keep outcomes distinct from approvals.

Built to try · tools and reference labs

Authority Tools

Explore all tools →

Permission has a short window

Try the five-second PULSE lease, silence, reconnect, stop and revoke with simulated payments.

Human Heartbeat

Use a compatible local heart-rate sensor as an optional policy input. This is not a phone link or proof of identity or biological presence.

WebAuthn presence

Try a passkey or security key for a fresh local approval. A PIN may satisfy verification; no biological-presence claim.

ECHO · shared authority allowance

Try the EUR 100 challenge: two executors, one allowance, private action evidence and strict permission translation. All effects are simulated.

Reference labs use test units. PULSE, heartbeat, WebAuthn and QR lab interfaces are in English. Physical sensors, authenticators and QR timing still need field validation.

01 · RUN IT LOCALLY

One small, inspectable starting point.

Download these two files into the same folder. With Node.js 20 or newer, run the quickstart. No package installation or account is required.

Authority SDK · profile 0.2Executable quickstartSource and SDK hashes
node authority-quickstart.cjs

The example creates temporary keys, previews a €25 request under a €40 grant, reserves it locally, refuses excess spending and a changed recipient, revokes the grant, and verifies its signed decision.

const { createPermissionPreview } = require("./echo-authority-sdk.cjs")

const session = await createPermissionPreview({
  merchant: "demo-merchant",
  budgetMinor: 4000,
  durationMinutes: 60,
})

await session.preview({ amountMinor: 2500, recipient: "demo-merchant" })
// Same evaluator; no budget consumption.

await session.reserve({ amountMinor: 2500, recipient: "demo-merchant" })
// Signed local reservation; dispatched: false.

await session.revoke()

The SDK packages the website’s TypeScript evaluator. The quickstart uses memory only and sends no payments. The repository also includes a PostgreSQL reservation adapter; each deployment must supply its own trusted enrollment, state and executor.

02 · VERIFY OUTSIDE THE WEBSITE

Evidence should travel.

AUTHORITY DECISIONS

Check who signed the verdict.

Export a decision from Permission Preview. Supply the expected gateway identity and a public key obtained separately.

Download decision verifier →
node verify-authority-decision.cjs authority-decision.json TRUSTED_GATEWAY PINNED_PUBLIC_KEY

node verify-witness.cjs witness-evidence.json trusted-keys.json

Demo trust exports reproduce a local session. They do not establish real identity or independent witness operation. A verifier must choose trusted keys through its own enrollment process. Signed times are the signer’s reported times.

03 · CONNECT A PROTECTED EXECUTOR

The boundary belongs at the action.

Keep provider credentials inside the service that enforces the grant. Authenticate and pin roots there. Bind each invocation to that service and exact parameters. Coordinate shared budgets transactionally and prevent duplicate dispatch.

An authorization receipt proves a decision. An executor’s receipt reports an attempt. A separate attestor’s receipt may report the outcome. When the result is uncertain, keep it unknown and reconcile before retrying.

Read the architecture →Explore protocol and adapters →
04 · DEPLOY WITH EXPLICIT ASSUMPTIONS

Make recovery part of the system.

  • Identity: authenticate enrollment; protect, rotate and revoke keys through a verified process.
  • Coordination: persist budgets, consumed nonces and witness checkpoints across restarts. Test concurrent requests and stale revocation state.
  • Independent witnesses: use separately controlled operators, compare checkpoints and publish the dishonest-node and outage assumptions behind the quorum.
  • Operations: separate recovery and deployment authority; rehearse backup restoration, credential revocation and traffic-abuse response.
  • Release evidence: check source hashes, run regression suites and obtain independent review before increasing security claims.

These are deployment requirements, not services activated by opening this page. The browser panel and quickstart are local references. No independent audit or uninterrupted availability is claimed.