Developer evaluation
Use synthetic data and the reference environment.
Startups
Prove one protected workflow before expanding your platform.
Start with the developer quickstart, then discuss a scoped pilot. Startup pricing is an enquiry: eligibility, limits, support, and fees must be agreed in writing.
Purpose-built capabilities
What Startups covers.
Pilot scope
Name one owner, protected resource, and measurable acceptance criteria.
Cost planning
Estimate agents, tools, evaluations, and evidence retention.
Commercial review
Confirm available capabilities and the transition after the pilot.
Use case / Startup engineering lead
Evaluate one protected action before agreeing pilot scope.
Illustrative integration review. These controls explain the design; they do not submit requests, grant authority, or execute an action.
Inspect the flow
Stage 1
Define scope
Evaluate one protected action before agreeing pilot scope.
Follow Startups from identity to evidence.
Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.
- 01IdentityWho or what is acting
- 02IntentSigned purpose and limits
- 03PolicyDeterministic evaluation
- 04ApprovalA named human when required
- 05ExecutionSingle-use grant, redeemed at the resource
- 06EvidenceReceipt joined to the audit chain