Skip to main content

Pulse Documentation

Pulse Protocol is purpose-bound consent and permissions: grant, use, revoke, and prove — with sensitive payloads off-chain and minimal anchors on-chain. It is a shared consent spine for integrations, not a single product UI.

Click to enlarge · Full screen in viewer

Start here — Pulse Protocol​

Integration guides

On client and internal docs, use Integration Guide in the sidebar for step-by-step material and OpenAPI references.

What Pulse enables​

  • Open-banking-style permissions with explicit grant and revoke, anchored for audit.
  • Multi-party data sharing with the data subject (or agent) in control of keys and consent metadata.
  • Regulated workflows that need tamper-evident consent history without centralising plaintext.

Product guides (VAS, Pulse+, Middle Tier) live under Platform services below; each product has its own documentation.

Why it matters​

AudiencePulse Protocol docs help you…
IntegratorsWire consent grant/revoke, trust boundaries, published APIs.
ArchitectsComponents, flows, and security model before you commit.
OperatorsDeploy and run Pulse-aligned infrastructure (where published).

Learn more​

Platform services

Smarter Contracts also documents operated platform services (products built on or alongside Pulse). Each service has its own overview and integration path; they are not substitutes for the consent protocol guides above.

Security

Never share wallet mnemonics or private keys. Pulse Protocol cannot recover lost keys and does not store unencrypted sensitive data.