Pricing

Fees must be as bounded as the policies.

OpenZaps should never hide execution economics. Users see gas, relayer fee caps, protocol-fee status, revocation paths, and token disclosures before they sign.

Commercial model

The clean v1 is not a hidden spread business. The user signs the max relayer fee, the app shows expected gas, and any future protocol fee must be visible in the same typed policy payload.

Simulation
Free

Local and API simulation should stay free so users can inspect policies before wallet review.

Policy creation
Gas only during gated beta

Users pay chain gas. No protocol fee until external audit and governance activation.

Hermes execution
Relayer fee cap

Every policy binds a max relayer fee before signing; Hermes cannot charge outside the cap.

Protocol fee
Governance-disabled v1

A future fee may apply to successful executions, but only after disclosure and wallet-level review.

Enterprise operators
Custom

Dedicated relayer lanes, compliance logs, policy review, and monitored revoke drills.

Access tiers

Builder

Free

Design templates, simulate policies, inspect hashes, export JSON, and test the review flow.

Operator

Relayer fee cap

Run monitored policies through Hermes with bounded submitters, private submission, alerts, and audit logs.

Protocol

Governance-set

Adapter governance, custom postconditions, dedicated monitoring, risk review, and launch-pool integrations.

Token disclosure0xZAPS is not a fee claim, yield promise, equity claim, or guarantee of access.

Token utility should grow through governance, operator alignment, and ecosystem coordination, but the product must remain usable and reviewable without implying financial returns.