PPX is an open standard for user-owned preference and context profiles that travel across agents and apps. Below are live applications reading a real profile through the PPX consent flow — each one only ever sees the slice you approve, and you can take it back.
The same four steps, defined normatively in the specification. No app ever receives your password or your raw profile — only a scoped, revocable grant.
An application requests a specific, purpose-bound slice of your profile — never the whole thing.
You sign in at the provider — not the app — and see exactly what is being asked. You can narrow it before approving.
The app receives a short-lived token derived from a revocable grant. It reads only what you allowed.
From your account you can see who has read what, and revoke any grant. Access stops immediately.
Four applications acting as PPX clients against the live PHP provider on this domain.
They read demonstration data for the seeded subject
did:example:user-123 (password ppx-demo at the consent screen).
A fragrance house composes a scent from your olfactory preferences — reading only your fragrance claims.
fragrance
Open the fragrance demo →
Recommender
A travel planner tailors suggestions to your core preferences — novelty appetite, social energy — without a profile of its own.
scope:core
Open the travel demo →
Assistant
A writing assistant adapts its tone and structure to how you like to communicate, shaped by your consented core profile.
scope:core
Open the writing demo →
Agent · A2A
Two people each grant one agent a read of their preferences. It returns how compatible they are — and neither profile is ever shown to the other.
scope:core · preference.compatibility
Open the compatibility demo →
An independent, second implementation of PPX v0.1 in PHP — passing the specification's conformance suite. Sign in to see everything held about the demo subject, which apps can read it, take a copy, or erase it.
The same consented profile is reachable over the protocols agents already speak. Both of these are live on this provider.
preference.compatibility skill, powering the Pair demo above. JSON-RPC at /ppx/a2a/, agent card at /ppx/.well-known/agent-card.json.
MCP · Model Context ProtocolA live MCP server at /ppx/mcp — connect Claude Desktop, Cursor, VS Code or Zed and read your consented profile as tools, grant-scoped.
These demos exist to make the standard tangible. The standard itself — schemas, consent model, bindings, conformance — is what you build against.
Demonstration data only. These apps read a seeded example profile, and the provider deployed here serves demonstration data — please do not put real personal data behind it. The provider is a second, independent implementation built to keep the specification honest; the reference stack lives in the PPX repositories.