Authorize your agent
Touch the device to issue a 31-day lease. Your agent can then send requests without another touch or USB access until renewal.
Join the device waitlist →Agent Passport / Revision ASkip the sequence
Hardware identity for autonomous agents
Authorize once.
Let your agent work.
Touch the device to authorize 31 days.Your agent works without another touch.
01 / CONNECT
Plug in
Agent Passport.
Connect the device to your computer over USB. Its permanent identity key stays inside the security chip.02 / AUTHORIZE
Touch once.
Renew in 31 days.
Touch the gold pad. The LED confirms your touch. The device issues a signed, 31-day credential called a lease.03 / DELEGATE
Give your agent access.
Keep the key protected.
Your agent receives the lease and uses its own temporary key. The device’s permanent key stays in hardware.04 / RUN
Your agent sends requests.
Services check them.
Each service checks the signed request and lease, then applies its own rules and limits. No additional touch is needed during the lease.
SCROLL TO EXPLORE
01 / A SHARED DEVICE IDENTITY
One device identity.
One shared limit.
Each device has a permanent identity, called its root. It can issue temporary credentials to several agents. A service can group those credentials under one shared limit. Creating another agent does not reset that device’s allowance.
02 / ONE DEVICE, TWO PARTICIPANTS
AGENT PASSPORTSIGNED 31-DAY LEASEVERIFIER
Verify incoming requests
The dev kit includes the device, verification software, and a working example endpoint. Use it to test identity checks and limits in your service.
Apply for a dev kit →03 / AUTHORIZATION MODEL
Touch once. Renew in 31 days.
01 Human presence02 Hardware signs lease03 Agent signs requests04 Service enforces policy
Touch is required when the device authorizes or renews a lease. During the 31-day window, your agent signs its own requests and services verify them. Touch the device again at renewal.
Inspect the complete trust path →04 / PUBLIC INFRASTRUCTURE
Check whether a device is registered.
Look up a device’s exact public identity key to check whether Pilot issued it. The registry returns a signed record, without exposing a device directory or total count.