Quickstart
Create or select an Application gateway, attach a Connector, authorize access, invoke one MCP capability, and verify the decision evidence.
Govern every path from intent to action
Axec gives applications an identity, binds access to explicit grants and connections, and enforces policy before credentials reach upstream systems.
Start with the outcome
Section titled “Start with the outcome”The quickest way to understand Axec is to follow one request from an Application to an upstream capability, then inspect the authority and evidence that made it possible.
How Axec works
See how Application identity, User grants, Connections, policy, approvals, Data Protection, and evidence form one trust chain.
Build from stable boundaries
Section titled “Build from stable boundaries”Concepts
Learn the ownership and lifecycle of Applications, credentials, Service Accounts, Connectors, Connections, GrantBundles, Grants, and gateway capabilities.
Guides
Implement delegated access, autonomous Applications, Service Account automation, offline access, revocation, and evidence inspection.
Governance
Narrow live authority with policy, pause sensitive actions for approval, mask mediated results, and correlate evidence.
SDK reference
Use the supported TypeScript and Python clients for delegated, autonomous, and management authority.
Review the trust boundary
Section titled “Review the trust boundary”Axec mediates credentials and reloads live authority at use time. The security model is explicit about what Axec can enforce, what it can observe, and what changes when a credential is released to a caller.