Before you start: protect service credentials
Design the credential custody first. It is the most difficult part of the integration. AEP services issue credentials to the agent. The AI agent must not read these credentials or get access to them. A CLI or an app that an AI agent runs must not keep them, unless you design a secure credential system. The InFlow CLI keeps credentials in an encrypted local vault that only the owner can unlock. See Unlock the vault.Step 1: Become an AEP platform
Implement Platform Hosted Identity in your backend. Every user in your backend then becomes identifiable with AEP. For each agent, the platform does these tasks:- It provisions an agent identity for each service.
- It publishes the agent DID document.
- It keeps the signing keys.
- It signs AEP client assertions for the agent. The service verifies these assertions.
@aep-foundation/platform.
Step 2: Connect your agent with the AEP agent SDK
The AEP agent SDK sends the AEP commands between your agent and each AEP service: enroll, status, grant, and revoke.createPlatformIdentityProvider() connects the agent to your platform.
SDKs for other languages
AEP has SDKs for Go, Java, Node.js, Python, and Rust. Each SDK implements Platform Hosted Identity. See aep.foundation/protocol.Related pages
Enrollment with AEP
Read how an agent enrolls and gets credentials.
Discover and enroll
Enroll with a service from the InFlow CLI.