agentpassport
cognis-digital/agentpassport
Verifiable AI-agent identity + multi-hop delegation chains anchored to a human principal (the unsolved 2026 agent-auth gap)
Instalação
npx convez-ai cognis-digital/agentpassport1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
agentpassport
Cryptographically prove which human authorized which AI agent to do what — even 4 hops deep.
#ai-agents #identity #authorization #agentic-ai #mcp #security #oauth
The unsolved 2026 problem: ~80% of orgs running autonomous agents can't trace an agent's actions back
to a human, and 45% still authenticate agents with shared API keys. OAuth/MCP handle one hop — but the
delegation chain loses its anchor at hop 3-4. agentpassport fixes exactly that: signed, scope-narrowing
delegation chains you can verify back to a human principal.
pip install cognis-agentpassport
agentpassport issue researcher --principal chris --scopes read,search,write --key K > p.json
agentpassport delegate p.json summarizer --scopes read,search --key K2 > p2.json # subset only
agentpassport verify p2.json --keys '{"human:chris":"K","agent:researcher":"K2"}' --require write
# → valid:false, violation: required scope 'write' not held at final hop ✅ escalation blocked
Usage — step by step
- Install the tool:
pip install cognis-agentpassport - Issue a passport for an agent, anchoring it to a human principal with an explicit scope set.
--keysigns it:agentpassport issue researcher --principal chris --scopes read,search,write --key K > p.json - Delegate to a child agent — scopes can only narrow (subset), never escalate:
agentpassport delegate p.json summarizer --scopes read,search --key K2 > p2.json - Verify the chain back to the human.
--keysis a JSON map of issuer-to-key;--requireasserts a scope must be held at the final hop:agentpassport verify p2.json --keys '{"human:chris":"K","agent:researcher":"K2"}' --require write # -> valid:false, violation: required scope 'write' not held at final hop (escalation blocked) echo $? # non-zero when verification fails - Automate in CI / a gateway — verify the presented passport before honoring an agent action:
- run: pip install cognis-agentpassport - run: agentpassport verify "$AGENT_PASSPORT" --keys "$TRUSTED_KEYS" --require write
Architecture
flowchart LR
H[👤 Human principal] -->|issue scopes| A1[Agent: researcher]
A1 -->|delegate ⊆ scopes| A2[Agent: summarizer]
A2 -->|delegate ⊆ scopes| A3[Agent: tool-runner]
A3 --> V{verify chain}
V -->|walks back to| H
V --> R[valid? · principal · violations]
Why it's different
Every hop is HMAC-signed and can only narrow scopes — escalation is detected. Verification walks the whole chain back to the human anchor, so you get the one thing OAuth/MCP can't give you today: accountable, multi-hop agent authorization.
Use it from any AI stack
MCP server (agentpassport mcp), JSON in/out for any agent runtime, drop-in for
uncensored-fleet / LangChain / CrewAI delegation.
Prior art / standards
Aligned with IETF draft-klrc-aiagent-auth (AIMS), NIST agent-identity concept paper, MCP, and Mastercard Agent Pay tokenization. Production: anchor the HMAC demo in real PKI / SPIFFE.
Related
🤖 uncensored-fleet · 🛡️ guardpost · 🧰 toolguard · 🗂️ the suite
⭐ Star it — agent identity is the problem nobody's solved yet.
Interoperability
agentpassport composes with the 300+ tool Cognis suite — JSON in/out and a shared
OpenAI-compatible /v1 backbone. See INTEROP.md for the
suite map, composition patterns, and reference stacks.
Integrations
Forward agentpassport's findings to STIX/MISP/Sigma/Splunk/Elastic/Slack/webhooks via
cognis-connect. See INTEGRATIONS.md.
License
COCL v1.0 — see LICENSE.