Controlled pilot showroom · AgentTrust + scoped keys

Run controlled trust-receipt demos before production risk.

Three flagship pilots. One request. One consent. One receipt. Test how Passpod handles sensitive requests, source confirmation, receipt state, and verification before production integration.

Vérifier les normes de politique d'abord. Deuxième, Reçu. Action en dernier. The requester requests. The user consents. The source confirms. The responsible party decides. Passpod records. DIDX verifies limited receipt state only.
AgentTrust gateway ready
Scoped key ready
Copy-ready API preview
Controlled pilot access
No private-document custody
No EUDI certification claim

Pick a pilot path.

Start with the AgentTrust Suite or an applied TrustPass pilot. Run the preview, inspect receipt state, then request scoped access for controlled testing.

Scenario library + live API preview

Flagship pilots appear first. More controlled scenarios remain available for reviewer testing. No scoring language, no wallet-provider overclaim, no production secrets.

Controlled access packages

Public demos remain open. Live testing uses scoped temporary keys, selected scenarios, expiry, revocation, and reviewer permissions.

Starter Access

One scenario, clean validation.

Test one selected scenario in preview + scoped-key mode.

  • One flagship pilot
  • Receipt/API preview
  • Short feedback loop
Partner Console

Multiple flows, shared feedback.

Test 2–3 workflows with a shared feedback loop and walkthrough.

  • Multiple pilots
  • Scoped keys
  • Implementation notes
Vertical Console

Dedicated use-case console.

Focus on AI AgentTrust, Remote Worker TrustPass, Call Center Trust Receipt, or Age Trust Receipts.

  • Vertical-specific receipts
  • Source-strength rules
  • Partner pilot path

Operating principles

Short pilot boundaries for legal, security, and ecosystem reviewers.

Responsibility model

The requester requests. The user consents. The source confirms. The responsible party decides. Passpod records. DIDX verifies limited receipt state only.

Data boundary

No private identity documents or raw wallet credentials are collected by default. Receipt state is limited to the selected purpose and scope.

Privacy & storage

No advertising cookies, no tracking cookies. Scoped console keys use sessionStorage. Language and notice choices may be stored locally.

Developer and ecosystem links

Built for reviewer testing, API evaluation, controlled partner pilots, and France / EUDI ecosystem readiness without overclaiming certification.

France / EUDI Playground contextPrepared for review in the France / EUDIW Unfold playground environment. GitHub mirrorSource package for developer review and version tracking. GitLab pilot packagePrivate playground package for authorized reviewers. Reviewer link available on request. Passpod ProtocolReceipt engine, operating principles, and protocol context. DIDX Registry ContextLimited receipt-state registry context. PassPal InterfaceUser-facing trust decision interface.

Request scoped console access

The request is prepared locally and opens an email draft to pilots@passpod.io. Backend approval, scoped keys, expiry, and revocation are handled outside the public page.

Review boundary

The requester requests. The user consents. The source confirms. The responsible party decides. Passpod records. DIDX verifies limited receipt state only.

Authorization: Bearer <temporary_pilot_key> No hardcoded keys. No localStorage for pilot keys. No key in URL. No private-document custody by default. No EUDI certification claim. No France Identité approval claim. No wallet-provider status claim.
Live pilot access is intentionally controlled: scoped keys, selected scenarios, expiry, revocation, and reviewer permissions are part of the pilot boundary.