Give your agents their own credentials.
Connect an AI agent or a scheduled job to your application with its own identity and credentials. Manage it from your account, and pause or revoke it individually.
Agent · actor_7a2…Ed25519Automation · actor_9f1…Ed25519Try pausing the agent. Its credentials and lifecycle are independent of the scheduled task.
Pause or revoke it
Suspend an Agent or Automation temporarily, or revoke it permanently. After a suspension, resuming requires new sessions; previous sessions stay invalid.
Try the interactive demoIdentify the agent behind a request
Applications can distinguish the account owner from the Agent or Automation acting for them. Each has an actor ID scoped to the application’s sector.
Agents and Automations belong to your account. Your account supplies membership and sharing consent; the application decides what each actor may do.
•••• •••• •••• ••••Keep the private key in your environment.
Use an access key or register an Ed25519 public key. With public-key authentication, the private key stays in your environment.
Set up an agent or a scheduled task.
Create an Agent or Automation, add its credentials, and enable the corresponding authentication method in your application.