Developer MVP
Policy engine, API, request approvals, mock execution, SDK, dashboard, seeded scenarios and audit evidence.
AI agents are becoming capable of buying services, invoking paid APIs and moving value. The question is no longer whether they can act. It is whether an organisation can define, enforce and prove what they were allowed to do.
The agent authority problem
Treating these as one vague “payment” problem hides the boundaries that make delegation safe.
Authentication
Who is the agent?
Authorization
What may the agent do?
Intent
What exact action was requested?
Policy
Under which constraints?
Execution
What actually happened?
Audit
Can the organisation prove it?
A precise category
CAPYN starts immediately before execution and ends with evidence of what happened. That boundary keeps the product useful across networks and providers.
CAPYN is not
Money forces precise answers about identity, limits, approval, concurrency, replay and audit. Solving those constraints creates a strong base for a more general capability layer.
Integer minor units and explicit currency.
Named capabilities with time-bounded authority.
Vendor and window limits before execution.
Decision, approval and execution evidence.
CAPYN will not move into blockchain, token or network complexity until the core authority system is solid and useful to real builders.
Current status
CAPYN v0.1 is a working developer MVP.