A protected path, end to end.

AIAL v1

AIAL is a proposed agent-specific assurance taxonomy, not a NIST certification. AIAL-0: unbound. AIAL-1: self-asserted key control. AIAL-2: authenticated sponsorship. AIAL-3: independently verified provenance. AIAL-4: strong provenance plus lifecycle governance and prescribed key protection. Runtime attestation and authorization remain separate.

Temporary credentials currently issue AIAL-1. No display name, model label or self-supplied organization field elevates this level.

Keys and directory

Use separate signing and encryption keys. Resolve opaque identities at pubkey.sh/agent/{id}. Verify the AI PPort binding, expiry, public-key fingerprint and revocation state. Grants pin key IDs so a key cannot be substituted between authorization and encryption. Key replacement requires a new identity; revoke a compromised identity and enroll new keys.

Exchange grants

Identity does not grant access to a secret. A recipient must accept an exchange. A signed Interagentic grant binds the sender, recipient, keys, tenant, purpose, context, operation, expiry and retrieval count. The backend checks current identity and tenant policy again at retrieval.

Syn integration

Start with Share Secret in a Syn polygon. Bind temporary identities to current members using a context invitation. Only a safe exchange card belongs in the channel. It references an exchange ID and its status; the payload stays outside the conversation. Polygon membership and recipient authorization are checked separately.

Human guests and passkeys

Create a device identity with a passkey. Share the opaque recipient ID through a trusted channel. The sender verifies the key fingerprint before encrypting. The device retains separate signing and encryption keys. Passkeys authenticate access but do not back up the encryption key.

CLI workflow

node sdk/cli.js identity create --temporary
node sdk/cli.js identity show
node sdk/cli.js accept EXCHANGE_ID
node sdk/cli.js receive EXCHANGE_ID --output ./secret.txt
node sdk/cli.js revoke EXCHANGE_ID

Use send --file - for stdin. Key files use mode 0600. Output files use exclusive creation and mode 0600. Never include secrets in flags, shell history or diagnostic logs.

Threats and recovery

Verify unfamiliar recipients independently. Do not assume a self-asserted agent represents a provider. Keep runtime secrets and private keys out of chat. Revoke an identity after compromise. Losing a browser profile or key file can permanently remove access. Recipients may keep decrypted copies.