PilotAgent Passport Protocol preview

How it works / Product preview

Your agent, recognized across services.

Agent Passport ties your agent’s requests to a device you control. Participating services can recognize that device, offer higher quotas, and let your agent get to work without a separate signup. Here’s how that connection is verified.

Figure 01 / A verifiable identity

Your request.
Your device’s signature.

Services recognize the device behind your agent.
The signing key stays in your hardware.

01 SIGN AND VERIFY EVERY EVENTEvery outbound event or request receives a device signature
YOUR SOFTWARE

Your agent

Prepares a request and asks your connected device to sign it.

EVENT / REQUEST CONTENT
YOUR HARDWARE

Agent Passport

Signs the request with a private key held inside its secure element.

ONE SIGNATURE PER EVENT
PARTICIPATING PROVIDER

The service

Checks the signature, recognizes your device, and applies its allowance. No separate service signup.

VERIFY / APPLY QUOTA

Verified means the request is signed by a registered device. It links your agent to hardware you control; it does not identify you as a unique person.

02 SUPPORTING PRESENCE CHECKTouch the device every 31 days
HUMAN PRESENCE

Touch once a month.

A physical touch refreshes the device’s human-presence confirmation.

HARDWARE ROOTAgent Passport
Agent Passport Revision A development board

Root key stays in hardware ECDSA P-256

HUMAN PRESENCE WINDOW

31days

  • Physical touch recorded
  • Device identity unchanged
  • Next touch at renewal

Every request still needs a hardware signature.

↓ Keep the device connected. Its private key stays in hardware and signs each outbound request.

Figure 02 / Supporting human-presence check

A monthly touch confirms presence.

Touch the device every 31 days to refresh its human-presence confirmation. This is separate from event signing: the connected device still signs every outbound event between touches.

MONTHLY HUMAN TOUCHHARDWARE SIGNS EVERY REQUEST
TouchDay 0
Every request signed by the deviceNo additional touch
RenewDay 31
FOR EVERY REQUESTdevice signature → registered public key → verified device identity

Figure 03 / Why providers can offer more

Higher quotas. A limit that holds.

Providers can offer higher tiers to verified devices and keep one allowance per device. Your agents share that allowance. Creating more email addresses or accounts cannot reset it.

01 / ACCOUNT-BASED LIMITS

New accounts.
New free quotas.

When a service grants a free quota to each account:

Account A
24 / 100
Account B
18 / 100
Account C
26 / 100

Three accounts receive three allowances. Email addresses alone do not identify a shared device.

02 / AGENT PASSPORT

More agents.
The same device quota.

The service groups valid signatures by device:

SAME DEVICEAgent A24 requests
SAME DEVICEAgent B18 requests
SAME DEVICEAgent C26 requests
REGISTERED HARDWARE ROOTDevice R-01
SIGNS EVERY EVENT
SERVICE / SHARED ALLOWANCE68 / 100
24 + 18 + 26 requests32 remaining
You get more usage. Providers keep control.

The signature identifies your device. The provider chooses its quota and counts usage across all agents using it.

Illustrative policy
100 requests per device
01Private key stays in hardwareunder normal operation
02Device signs every eventbound to the event content
03Public key identifies the devicethrough its registry record
04Agents share the device quotano service sign-ups, accounts, or logins

What this model establishes

  • A valid device signature requires its private key and ties the event to its registered public key.
  • A participating service can share one included quota across agents using the same signing device.
  • The monthly touch provides a recurring human-presence check.

What this does not establish

  • That one unique human owns or operates the device.
  • That the agent is safe, truthful, or uncompromised.
  • That an attacker cannot obtain multiple devices. Each device remains a separate identity.