aport-spec vs intent-plane
Agent authorization specifications and runtime gates compared
aport-spec defines the draft Open Agent Passport specification, schemas, security guidance, and conformance materials for pre-action authorization. intent-plane is a Go authorization gate that evaluates declared intents against signed policy and records decisions; it also provides tools to independently recompute those decisions.
aport-spec: Define Pre-Action Authorization for AI Agents
aport-spec is the Open Agent Passport (OAP) v1.0 draft, a specification for cryptographically verifiable AI agent credentials and authorization decisions before sensitive actions. It is aimed at platform builders and developers who need a shared runtime trust model for agentic commerce.
intent-plane: Gate and Audit Irreversible Agent Actions
intent-plane is a Go-based authorization gate for AI agents taking irreversible actions. Agents declare intent, the gate fails closed against a human-signed policy, and independent Go and Python verifiers can re-derive decisions from the durable feed.
| aport-spec | intent-plane | |
|---|---|---|
| Language | TypeScript | Go |
| License | MIT | — |
| Stars | 4 | 1 |
| Forks | 0 | 0 |
| Last analyzed | Oct 22, 2026 | Nov 6, 2026 |
Key differences
- aport-spec focuses on defining interoperable schemas and requirements, while intent-plane provides a gate for checking actions at the tool-call boundary.
- aport-spec leaves runtime decision and enforcement components to adopting teams; intent-plane evaluates requests and refuses when authorization is uncertain.
- aport-spec documents passport and decision schemas, Ed25519 verification, and W3C Verifiable Credentials integration; intent-plane emphasizes signed policy artifacts, durable records, and independent Go and Python verification.
- aport-spec is written in TypeScript and is licensed under MIT; intent-plane is written in Go and specifies Go 1.26 for its Go packages.
- aport-spec is explicitly a draft specification; intent-plane cautions that key authority is test-grade and describes signing and identity capabilities as staged.
- aport-spec includes conformance tests and a runner; intent-plane provides a contract, frozen feed fixtures, and optional LangChain, MCP, and reporting adapters.
Choose aport-spec if you…
- need schemas and conformance materials for implementing an agent authorization approach.
- want to build your own runtime decision and enforcement components around a shared specification.
- need documentation covering Ed25519 verification and W3C Verifiable Credentials integration.
Choose intent-plane if you…
- need a Go gate that checks declared agent intents against signed policy before actions.
- want Go and Python tools to independently recompute decisions from an append-only feed.
- need derived idempotency keys or optional LangChain, MCP, and regulatory-reporting integration paths.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.