Phase 1 · Partner / intermediary

Integration intake

For vendors and integrators representing or embedding for a customer. If you cannot yet name a customer, use TBD — no named customer yet in the end-customer field—we will limit scope to reference architecture until a sponsor appears.

Not the right path? I am a direct customer instead

1. Contact and party

Organization name *

Your full name *

Work email *

Role or title *

Integration route: Intermediary / partner (you represent or embed for a customer).

End-customer organization *

Your relationship to the end customer

2. Intent

Product surface (select all that apply) *

Trustee commit API
Admissibility verify API
Admissibility Vault
Other (specify below)

Goal in one sentence *

Target pilot window

3. Technical shape

Who will run the integration in production? *

System-of-record or ledger for the gated action *

SoR technology or access pattern

Orchestration / integration stack

Upstream authority for policy / admissibility verdict

Other vendors in the chain

Need BiDigest staging / sandbox? *

Production region or data residency

Preferred API authentication *

4. Compliance / procurement (light)

Industry or regulatory context (informational)

Written confirmation for hashing and API contracts *

Anything else we should know?

I agree to the Privacy Policy and understand this intake is for operational routing, not legal advice. *

Phase 2 (technical supplement) is shared after triage when engineering depth is warranted—not legal advice.

All intake options · Governance hub