Vitality Connect

Connected Applications

Review approved application connectivity, permissions and verified interaction provenance. Applications submit evidence; Vitality protocol policy determines eligibility and reward intent.

Reward calculation capability does not mean rewards are live. No approved active reward policy is currently represented by this surface, and reward intent never authorizes a token transfer, Treasury action or wallet signature.

Applications

—

Proof history

—

Reward policy

Not active

Execution authority

Disabled

Application access

Status and permissions are observational. Revocation and credential controls remain governed operational actions.

Application status unavailable

No live application collection is available to this read surface. Vitality does not fabricate application registrations or permissions for presentation.

Verified interaction history

Proof processing and provenance remain distinct from reward execution.

Interaction history unavailable

No governed proof-history collection is currently available to this product surface. Missing records remain unavailable rather than inferred.

Developer integration

Build with Vitality Connect

Integrations authenticate as approved applications, submit schema-versioned proofs, use unique source-event and replay controls, and receive protocol-governed processing outcomes.

POST /api/vitality-connect/v1/proofs

Sandbox credentials and live application credentials are never inferred or embedded in this interface. Integration authority must be explicitly provisioned.

Operations

Fail-closed by design

Unknown or revoked applications are rejected.
Invalid authentication and unsupported schemas fail closed.
Replay and duplicate evidence is rejected.
Reward values remain protocol controlled.
Reward intent remains separate from token execution.

Operational revocation controls are intentionally not exposed as unauthenticated client-side mutation buttons.