Identify the actors
Separate people, agents, services, devices, and delegated identities.
Developers / Build with PTERI
Put a verification boundary around the action.
Start with a high-consequence operation. Define the actor, request, policy, and evidence you need before connecting PTERI to a production workflow.
Open the Auth integration guide ↗Integration path
A focused route from concept to test.
The public documentation provides the current endpoints. This page frames the design work that should happen around them.
Bound the action
Describe which operation, resource, scope, and expiry the approval will cover.
Test the evidence
Verify signed proof and record the policy outcome at the relying system.
Build and operate
The right entry point for each job.
Use the maintained developer services for implementation details and this site for product context and trust boundaries.
Auth integration guide ↗Signed-challenge verification for Pteri-AuthPlatform documentation ↗Wallet, infrastructure, and broader platform guidesSecurity architectureTrust boundaries and controls →Mixed-system modelHumans, agents, robots, and legacy systems →Technical discussionReview your use case with KAKR →