{ "data": { "a": { "slug": "kite-agent-passport", "name": "Kite Agent Passport", "vendor": "Kite AI", "vendorUrl": "https://gokite.ai", "kind": "platform", "category": "agent-wallets", "summary": "Kite Agent Passport gives an AI agent a funded USDC wallet and an identity, with spending sessions a person approves by passkey. Agents use it through the kpass CLI and a skills bundle to pay x402 and MPP services.", "url": "https://www.anchorterminal.com/tools/kite-agent-passport", "markdownUrl": "https://www.anchorterminal.com/tools/kite-agent-passport.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kite-agent-passport.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kite-agent-passport.json", "repo": "https://github.com/gokite-ai/passport-skills", "license": "Closed service under terms from Datalego Inc. dated 29 April 2026. The Passport Skills repository is MIT. The kpass CLI is distributed as binaries and its source repository is private.", "transports": [ "http" ], "packages": [], "auth": "mixed", "authNotes": "A person signs up by email (a verification link plus an 8-character code) and creates a passkey on the Passport dashboard. The agent then registers itself with `kpass agent:register` and requests spending sessions, each approved by the person with the passkey. Wallet sends, session approvals and passkey changes need a fresh passkey step-up. Returning logins use an emailed code. A hosted MCP endpoint with OAuth exists for ChatGPT and other MCP clients (changelog, 23 June 2026); its URL was not found in the reviewed docs.", "pricing": "usage", "pricingNotes": "No published fee schedule was found (checked 10 October 2026). The changelog says session preflight returns an estimate covering merchant fees, network gas and Passport's own service margin, shown before approval, without stating the margin. Merchants set their own prices. Account creation and sandbox test mode with a testnet faucet need no card. Fiat funding goes through Banxa with an ID check.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "partial", "evidence": "Passport pays third-party x402 services as a buyer (`kpass agent:session execute`, `--payment-approach x402_http`) and also pays MPP services, per the Service Provider Guide (https://docs.gokite.ai/kite-agent-passport/service-provider-guide). Passport's own backend is not paid over x402, MPP or L402, and Kite recommends the third-party Pieverse facilitator for Kite chain.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-10" }, "docsUrl": "https://docs.gokite.ai/kite-agent-passport", "llmsTxt": "https://docs.gokite.ai/llms.txt", "capabilities": [ "wallet.onchain", "wallet.spend-limits", "payments.x402", "payments.card", "auth.agent-identity" ], "tags": [ "hosted", "cli", "skills", "llms-txt", "wallet", "x402", "mpp", "stablecoins", "virtual-cards", "closed-source" ], "lastRelease": "2026-10-07", "graded": true, "anchor": { "graded": true, "score": 51.5, "grade": "D", "agentReady": false, "rank": 755, "ranked": true, "rankOf": 961, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 71, "payments": 35, "reliability": 35, "schema": 64, "security": 72, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-10" }, "negative": -5, "negativeNotes": [ "22 July 2026: Kite fixed a settlement-timing gap in agent-session payments, marked [security], that could allow repricing between detection and settlement. It is fixed and disclosed in the changelog, with no report of exploitation found, so -2 (https://docs.gokite.ai/changelog/2026/2026-07-22-release).", "8 July 2026: settlement moved to Base, replacing the treasury relay path, and mainnet agent wallets' USDC was bridged to Base. The release note asked integrations that assumed Kite settlement to update, with no earlier notice found, so -3 (https://docs.gokite.ai/changelog/2026/2026-07-08-release)." ], "verdict": "Spending sessions with per-transaction and total caps, a lifetime and passkey approval are enforced by the service, with step-up checks and an audit log. A person must sign up by email and create a passkey before an agent can pay. No published fee rate, OpenAPI file or Passport status page was found.", "bestFor": "Coding agents such as Claude Code or Codex that need to pay x402 or MPP services within budgets a person approves by passkey.", "strengths": [ "Each spending session has a per-transaction cap, a USD budget, a lifetime and a scope, approved by the person with a passkey", "Wallet sends, session approvals and passkey changes need an action-bound passkey step-up, and a step-up log and login history are readable", "Pays third-party x402 and MPP services as a buyer, with cross-chain routing across Base, Tempo and Solana since 8 July 2026", "The kpass CLI returns JSON with numbered exit codes, an `error_code` and a `hint`, and documents an idempotency key on paid executes", "Active releases: CLI bundle 83 on 7 October 2026 and twelve Passport Skills tags since 29 August 2026" ], "weaknesses": [ "A person signs up by email, clicks a verification link and creates a passkey in a browser before any agent can spend", "No fee rate is published. Passport's service margin appears only in a per-session estimate before approval", "The API reference is a placeholder and no OpenAPI file is published, so agents work through the CLI or the hosted MCP endpoint", "No status page covers the Passport backend, and no rate limit with numbers or SLA was found", "The kite-passport skill tells agents to use paid services before WebSearch or built-in tools, which can spend budget on tasks free tools could do" ], "agentNotes": [ "Run `kpass` with `--output json --no-interactive` and branch on the exit code and `error_code`. Exit 6 is a session policy breach, so request a new session rather than logging in again", "Pass `--idempotency-key` on every `kpass session execute` so a retry after a timeout does not pay twice", "Ask the person for a session with a small per-transaction cap and a short `--ttl`, and confirm the merchant URL before executing", "Use `kpass sandbox` test mode and the faucet to try a payment flow without real funds. Scoped cards are not available in sandbox", "Check the kite-passport skill's trigger rules before installing it, since it directs the agent to paid services ahead of free tools" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 51.5 } ], "editorialScores": { "ergonomics": 68, "maintenance": 71, "payments": 35, "reliability": 35, "schema": 64, "security": 72, "transparency": 47 }, "provenanceScore": 65 }, "connect": { "install": "curl -fsSL https://agentpassport.ai/install.sh | bash" }, "letme": { "capability": "https://letme.dev/wallet.onchain", "tool": "https://letme.dev/kite-agent-passport" }, "area": "payments", "provenance": { "legalEntity": "Datalego Inc.", "domain": "agentpassport.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://agentpassport.ai/terms/", "privacy": "https://agentpassport.ai/privacy/", "statusPage": "", "changelog": "https://docs.gokite.ai/changelog/2026/2026-07-29-release", "securityTxt": "none", "checked": "2026-10-10", "notes": [ "The terms and privacy policy name Datalego Inc. as the operator of agentpassport.ai, and the privacy policy gives ops@gokite.ai for requests.", "status.gokite.ai covers the Kite website, explorer and RPC endpoints, not the Passport backend, so statusPage is empty.", "agentpassport.ai/.well-known/security.txt returns the site's HTML page and gokite.ai/.well-known/security.txt returns 404. SECURITY.md in the skills repository names security@kitepassport.com.", "The backend runs at passport.prod.gokite.ai, a Kite domain, per the skills repository." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kite-agent-passport.json" }, "answer": "Openfort scores 70.1 (BB) on agent readiness against Kite Agent Passport's 51.5 (D), and leads in 5 of 7 scored categories. Kite Agent Passport leads on security \u0026 auth.", "b": { "slug": "openfort", "name": "Openfort", "vendor": "Openfort (Alamas Labs Inc.)", "vendorUrl": "https://www.openfort.io", "kind": "http-api", "category": "agent-wallets", "summary": "Openfort is wallet infrastructure from Alamas Labs. Its REST API, Node SDK and CLI create backend wallets held in a trusted execution environment, with signing policies, session keys and gas sponsorship. It also sells embedded wallets for apps.", "url": "https://www.anchorterminal.com/tools/openfort", "markdownUrl": "https://www.anchorterminal.com/tools/openfort.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/openfort.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/openfort.json", "repo": "https://github.com/openfort-xyz/openfort-node", "license": "Proprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licence", "transports": [ "http", "stdio" ], "remoteUrl": "https://api.openfort.io", "packages": [ { "registry": "npm", "name": "@openfort/openfort-node" }, { "registry": "npm", "name": "@openfort/cli" } ], "auth": "api-key", "authNotes": "A secret key (`sk_test_` or `sk_live_`) from the self-serve dashboard goes in `Authorization: Bearer`. Secret keys carry scopes (26 named, such as `accounts:sign`, `policies:write` and `accounts:export`), and a key made without a scope list gets all but four. Backend wallet signing also needs an `x-wallet-auth` ES256 JWT signed with a separate wallet secret, with a nonce and a request hash. Test and live keys are isolated. No OAuth (https://www.openfort.io/docs/api-reference/authentication).", "pricing": "freemium", "pricingNotes": "Free plan with 2,000 operations a month and no card, then $0.01 an operation. Growth $99 a month (25,000 operations, $0.008 extra), Pro $249 (100,000, $0.006), Scale $599 (500,000, $0.004). An operation is a wallet creation, signature, broadcast, policy evaluation, webhook or key import or export. Sponsored gas carries a 10 per cent surcharge, 5 per cent on Pro and Scale. Enterprise is priced by sales (https://www.openfort.io/pricing.md, checked 2026-10-09).", "priceSummary": "$99 / mo", "where": "both", "x402": { "level": "partial", "evidence": "Openfort wallets pay as a buyer. The docs carry an x402 recipe for USDC payments from embedded and backend wallets and an MPP recipe for an agent paying HTTP services on Tempo. Openfort's own API is not paid over x402. Its 402 status means the plan's operations are used up with no payment method (https://www.openfort.io/docs/llms.txt; https://www.openfort.io/docs/api-reference/errors, checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 10, "npmWeekly": 7647, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.openfort.io/docs/products/server/workflows/agentic-wallets", "llmsTxt": "https://www.openfort.io/llms.txt", "openapi": "https://www.openfort.io/docs/openapi.json", "capabilities": [ "wallet.onchain", "wallet.spend-limits", "wallet.custody", "payments.x402" ], "tags": [ "hosted", "freemium", "free-tier", "api-key", "openapi", "llms-txt", "mcp", "cli", "typescript", "wallet", "stablecoin", "x402", "tee", "status-page", "webhooks" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 70.1, "grade": "BB", "agentReady": true, "rank": 163, "ranked": true, "rankOf": 961, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 87, "payments": 60, "reliability": 88, "schema": 89, "security": 65, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -5, "negativeNotes": [ "9 October 2026. The agent wallets page says a signing policy is evaluated server-side on every operation against value caps and allowlists and that caps are enforced at signing time. The policies docs say an EVM backend send is evaluated only as `signEvmHash`, so those rules cannot block one. The docs disclose this plainly, so 3 points (https://www.openfort.io/agent-wallets; https://www.openfort.io/docs/configuration/policies).", "28 September 2026. The changelog says tokens from a third-party login provider were still accepted after the provider was disabled. Fixed and documented in the changelog, with no advisory found, so 2 points (https://www.openfort.io/changelog)." ], "verdict": "Backend wallets sign inside a GCP Confidential Space enclave, secret keys carry 26 scopes, and rate limits, errors and prices are published. On EVM, a backend send reaches the policy engine only as a hash, so address and value rules bind only when the caller runs the pre-flight check first.", "bestFor": "A team that wants server-held wallets for agents on EVM chains and Solana with enclave signing, a free start and a CLI an agent can drive.", "strengths": [ "Backend wallet keys are generated and used inside a GCP Confidential Space enclave with AMD SEV-SNP, wrapped by an HSM-backed Cloud KMS key", "Secret keys carry 26 named scopes, and backend signing also needs an ES256 JWT from a separate wallet secret that can be rotated", "Policy engine rejects any operation no rule matches, with account and project scopes and a pre-flight `POST /v2/policies/evaluate`", "Rate limits are published per plan (100 to 1,200 requests a minute) and a 429 carries `Retry-After`", "Free plan of 2,000 operations a month with no card, and per-operation overage prices on every plan" ], "weaknesses": [ "An EVM backend send is evaluated only as `signEvmHash`, so address, value and calldata rules do not block it unless the caller pre-flights", "Signing policies cap value per transaction. No daily or rolling cap was found in the reviewed policy pages", "The CLI MCP server exposes 72 commands as tools, among them `accounts_evm_export`, which returns a private key", "A default secret key includes `accounts:export` and `accounts:sign`", "No SOC 2 report (the vendor says so), no security.txt and no bug bounty found" ], "agentNotes": [ "Call `policies.evaluate` with operation `signEvmTransaction` before every EVM backend send. The send itself is checked only as `signEvmHash`", "Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail", "Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error", "Give an agent a secret key without `accounts:export`, and limit the CLI MCP server to the tools it needs", "On a 5xx after a write, read the resource before retrying. On a 429, wait the full `Retry-After`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 70.1 } ], "editorialScores": { "ergonomics": 65, "maintenance": 87, "payments": 60, "reliability": 88, "schema": 89, "security": 65, "transparency": 64 }, "provenanceScore": 73 }, "connect": { "install": "npm install @openfort/openfort-node", "http": "curl https://api.openfort.io/v2/transactions -H \"Authorization: Bearer sk_test_...\"", "claudeCode": "claude mcp add --transport http openfort-docs https://www.openfort.io/api/mcp", "config": { "mcpServers": { "openfort": { "args": [ "@openfort/cli", "--mcp" ], "command": "npx", "env": { "OPENFORT_API_KEY": "${OPENFORT_API_KEY}" } } } } }, "letme": { "capability": "https://letme.dev/wallet.onchain", "tool": "https://letme.dev/openfort" }, "area": "payments", "unitPrices": [ { "item": "Growth plan", "unit": "month", "usd": 99, "note": "25,000 operations included" }, { "item": "Pro plan", "unit": "month", "usd": 249, "note": "100,000 operations included" }, { "item": "Scale plan", "unit": "month", "usd": 599, "note": "500,000 operations included" }, { "item": "Extra operation, Free plan", "unit": "call", "usd": 0.01, "note": "per operation above 2,000 a month" }, { "item": "Extra operation, Growth plan", "unit": "call", "usd": 0.008, "note": "per operation above 25,000 a month" }, { "item": "Extra operation, Scale plan", "unit": "call", "usd": 0.004, "note": "per operation above 500,000 a month" } ], "provenance": { "legalEntity": "Alamas Labs Inc.", "domain": "openfort.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.openfort.io/developer-terms", "privacy": "https://www.openfort.io/privacy", "statusPage": "https://status.openfort.io", "changelog": "https://www.openfort.io/changelog", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The Developer Terms of Service (last updated 16 January 2026) and the privacy policy (last updated 4 September 2026) both name Alamas Labs Inc. doing business as Openfort. The terms are governed by Delaware law.", "The API answers at https://api.openfort.io and the docs, OpenAPI file and docs MCP server at www.openfort.io.", "https://www.openfort.io/.well-known/security.txt answered 404. The security page gives security@openfort.io for reports.", "rdap.org answered that no RDAP service is available for openfort.io, so the registration date is not recorded.", "robots.txt on www.openfort.io allows every path and carries `Content-Signal: search=yes, ai-input=yes, ai-train=no`." ], "score": 73 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/openfort.json", "live": { "slug": "openfort", "probe": { "target": "https://api.openfort.io", "method": "get", "lastAt": "2026-10-11T02:46:35.675250683Z", "lastOk": true, "lastStatus": 404, "lastMs": 109, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 115, "p95ms24h": 191, "samples24h": 248, "samples30d": 361, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 29, "ok": 29 } ] }, "vendorStatus": { "page": "https://status.openfort.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-11T01:37:06.686210757Z" }, "versions": [ { "registry": "github", "name": "openfort-xyz/openfort-node", "version": "v0.13.1", "released": "2026-09-26", "seenAt": "2026-10-10T18:04:48.935598228Z" }, { "registry": "npm", "name": "@openfort/cli", "version": "0.2.2", "seenAt": "2026-10-10T18:04:47.715634983Z" }, { "registry": "npm", "name": "@openfort/openfort-node", "version": "0.13.1", "seenAt": "2026-10-10T18:04:46.705432258Z" } ], "githubStars": 10, "npmWeekly": 8635, "securityTxt": { "url": "https://openfort.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-10T15:41:26.50431576Z" }, "llmsTxt": { "url": "https://www.openfort.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-10T14:04:52.125276672Z" }, "pages": [ { "url": "https://www.openfort.io/changelog", "kind": "changelog", "status": 304, "checkedAt": "2026-10-10T19:16:58.764754404Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f46241d68d76" }, { "url": "https://www.openfort.io/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-10T19:17:02.792723587Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "85d4cce5d750" }, { "url": "https://www.openfort.io/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-10-10T19:17:04.847768044Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "92d5a24cf4eb" }, { "url": "https://www.openfort.io/developer-terms", "kind": "terms", "status": 304, "checkedAt": "2026-10-10T19:17:01.102072718Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c5c4280eac9f" } ], "updatedAt": "2026-10-11T02:46:35.675250683Z" } }, "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "Kite AI", "b": "Openfort (Alamas Labs Inc.)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.openfort.io", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "payer tooling only", "b": "payer tooling only", "name": "x402" }, { "a": "Closed service under terms from Datalego Inc. dated 29 April 2026. The Passport Skills repository is MIT. The kpass CLI is distributed as binaries and its source repository is private.", "b": "Proprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licence", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-07", "b": "2026-09-28", "name": "Last release" }, { "a": "", "b": "2026-01-16", "name": "Terms last updated" }, { "a": "", "b": "2026-09-04", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "10 stars, 7.6k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "Openfort scores 70.1 (BB) on agent readiness against Kite Agent Passport's 51.5 (D), and leads in 5 of 7 scored categories. Kite Agent Passport leads on security \u0026 auth.", "question": "Which is better for AI agents, Kite Agent Passport or Openfort?" }, { "answer": "No hosted endpoint is listed for Kite Agent Passport. Openfort has a hosted endpoint at https://api.openfort.io.", "question": "Can an agent call Kite Agent Passport and Openfort without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Security \u0026 auth, 72 against 65" ], "also": null, "goodFor": "Coding agents such as Claude Code or Codex that need to pay x402 or MPP services within budgets a person approves by passkey.", "slug": "kite-agent-passport", "watchFor": "A person signs up by email, clicks a verification link and creates a passkey in a browser before any agent can spend" }, { "aheadOn": [ "Reliability, 88 against 35", "Schema \u0026 documentation, 89 against 64", "Payments \u0026 pricing, 60 against 35", "Maintenance \u0026 community, 87 against 71", "Transparency \u0026 trust, 69 against 56" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Runs on your own machine" ], "goodFor": "A team that wants server-held wallets for agents on EVM chains and Solana with enclave signing, a free start and a CLI an agent can drive.", "slug": "openfort", "watchFor": "An EVM backend send is evaluated only as `signEvmHash`, so address, value and calldata rules do not block it unless the caller pre-flights" } ], "job": { "capability": "wallet.onchain", "name": "Onchain wallets" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcard-vs-kite-agent-passport.json", "title": "Agentcard vs Kite Agent Passport", "url": "https://www.anchorterminal.com/compare/agentcard-vs-kite-agent-passport" }, { "json": "https://www.anchorterminal.com/compare/circle-wallets-vs-kite-agent-passport.json", "title": "Circle Wallets (Agent Wallets, Programmable Wallets) vs Kite Agent Passport", "url": "https://www.anchorterminal.com/compare/circle-wallets-vs-kite-agent-passport" }, { "json": "https://www.anchorterminal.com/compare/circle-wallets-vs-openfort.json", "title": "Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort", "url": "https://www.anchorterminal.com/compare/circle-wallets-vs-openfort" }, { "json": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-kite-agent-passport.json", "title": "Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Kite Agent Passport", "url": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-kite-agent-passport" }, { "json": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-openfort.json", "title": "Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Openfort", "url": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-openfort" }, { "json": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-privy.json", "title": "Kite Agent Passport vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-privy" }, { "json": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-sponge-wallet.json", "title": "Kite Agent Passport vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-sponge-wallet" }, { "json": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-turnkey-agentic-wallets.json", "title": "Kite Agent Passport vs Turnkey Agentic Wallets", "url": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-turnkey-agentic-wallets" }, { "json": "https://www.anchorterminal.com/compare/openfort-vs-privy.json", "title": "Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/openfort-vs-privy" }, { "json": "https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.json", "title": "Openfort vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet" }, { "json": "https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.json", "title": "Openfort vs Turnkey Agentic Wallets", "url": "https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets" }, { "json": "https://www.anchorterminal.com/compare/agentcard-vs-openfort.json", "title": "Agentcard vs Openfort", "url": "https://www.anchorterminal.com/compare/agentcard-vs-openfort" } ], "scores": [ { "by": 53, "edge": "openfort", "key": "reliability", "kite-agent-passport": 35, "name": "Reliability", "openfort": 88, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 25, "edge": "openfort", "key": "schema", "kite-agent-passport": 64, "name": "Schema \u0026 documentation", "openfort": 89, "weight": 13 }, { "by": 3, "edge": "kite-agent-passport", "key": "ergonomics", "kite-agent-passport": 68, "name": "Agent ergonomics", "openfort": 65, "weight": 13 }, { "by": 7, "edge": "kite-agent-passport", "key": "security", "kite-agent-passport": 72, "name": "Security \u0026 auth", "openfort": 65, "weight": 14 }, { "by": 25, "edge": "openfort", "key": "payments", "kite-agent-passport": 35, "name": "Payments \u0026 pricing", "openfort": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 16, "edge": "openfort", "key": "maintenance", "kite-agent-passport": 71, "name": "Maintenance \u0026 community", "openfort": 87, "weight": 7 }, { "by": 13, "edge": "openfort", "key": "transparency", "kite-agent-passport": 56, "name": "Transparency \u0026 trust", "openfort": 69, "weight": 7 } ], "summary": "Openfort scores 70.1 (BB) on agent readiness against Kite Agent Passport's 51.5 (D), and leads in 5 of 7 scored categories. Kite Agent Passport leads on security \u0026 auth. Both do onchain wallets.", "verdicts": { "kite-agent-passport": "Spending sessions with per-transaction and total caps, a lifetime and passkey approval are enforced by the service, with step-up checks and an audit log. A person must sign up by email and create a passkey before an agent can pay. No published fee rate, OpenAPI file or Passport status page was found.", "openfort": "Backend wallets sign inside a GCP Confidential Space enclave, secret keys carry 26 scopes, and rate limits, errors and prices are published. On EVM, a backend send reaches the policy engine only as a hash, so address and value rules bind only when the caller runs the pre-flight check first." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort", "json": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort.md", "slim": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort.min.md" }, "markdown": "Openfort scores 70.1 (BB) on agent readiness against Kite Agent Passport's 51.5 (D), and leads in 5 of 7 scored categories. Kite Agent Passport leads on security \u0026 auth. Both do onchain wallets.\n\n- Kite Agent Passport: grade D, 51.5/100, rank #755 of 961. Markdown https://www.anchorterminal.com/tools/kite-agent-passport.md · JSON https://www.anchorterminal.com/api/v1/tools/kite-agent-passport.json\n- Openfort: grade BB, 70.1/100, rank #163 of 961. Markdown https://www.anchorterminal.com/tools/openfort.md · JSON https://www.anchorterminal.com/api/v1/tools/openfort.json\n- Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md\n- All 30 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md\n\n## Which one, for what\n\n### Kite Agent Passport (D)\n\nGood for: Coding agents such as Claude Code or Codex that need to pay x402 or MPP services within budgets a person approves by passkey.\n\nAhead on:\n- Security \u0026 auth, 72 against 65\n\nWatch for: A person signs up by email, clicks a verification link and creates a passkey in a browser before any agent can spend\n\n### Openfort (BB)\n\nGood for: A team that wants server-held wallets for agents on EVM chains and Solana with enclave signing, a free start and a CLI an agent can drive.\n\nAhead on:\n- Reliability, 88 against 35\n- Schema \u0026 documentation, 89 against 64\n- Payments \u0026 pricing, 60 against 35\n- Maintenance \u0026 community, 87 against 71\n- Transparency \u0026 trust, 69 against 56\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Runs on your own machine\n\nWatch for: An EVM backend send is evaluated only as `signEvmHash`, so address, value and calldata rules do not block it unless the caller pre-flights\n\n\n## Score by category\n\n| Category | Weight | Kite Agent Passport | Openfort | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 35 | 88 | Openfort +53 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 89 | Openfort +25 |\n| Agent ergonomics | 13% (16.2 this run) | 68 | 65 | Kite Agent Passport +3 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 65 | Kite Agent Passport +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 60 | Openfort +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 87 | Openfort +16 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 69 | Openfort +13 |\n| Negative events | ≤15 | -5 | -5 | |\n| **Total** | | **51.5 · D** | **70.1 · BB** | |\n\n## Facts side by side\n\n| Fact | Kite Agent Passport | Openfort |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | Kite AI | Openfort (Alamas Labs Inc.) |\n| Hosted endpoint | no (local only) | `https://api.openfort.io` |\n| Transports | HTTP | HTTP, stdio |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Freemium |\n| x402 | payer tooling only | payer tooling only |\n| Licence | Closed service under terms from Datalego Inc. dated 29 April 2026. The Passport Skills repository is MIT. The kpass CLI is distributed as binaries and its source repository is private. | Proprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licence |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-10-07 | 2026-09-28 |\n| Terms last updated | | 2026-01-16 |\n| Privacy policy last updated | | 2026-09-04 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | yes |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | yes |\n| Popularity | none | 10 stars, 7.6k npm/wk |\n\n## Verdicts\n\n**Kite Agent Passport.** Spending sessions with per-transaction and total caps, a lifetime and passkey approval are enforced by the service, with step-up checks and an audit log. A person must sign up by email and create a passkey before an agent can pay. No published fee rate, OpenAPI file or Passport status page was found.\n\n**Openfort.** Backend wallets sign inside a GCP Confidential Space enclave, secret keys carry 26 scopes, and rate limits, errors and prices are published. On EVM, a backend send reaches the policy engine only as a hash, so address and value rules bind only when the caller runs the pre-flight check first.\n\n## Before you call either\n\n### Kite Agent Passport\n\n1. Run `kpass` with `--output json --no-interactive` and branch on the exit code and `error_code`. Exit 6 is a session policy breach, so request a new session rather than logging in again\n2. Pass `--idempotency-key` on every `kpass session execute` so a retry after a timeout does not pay twice\n3. Ask the person for a session with a small per-transaction cap and a short `--ttl`, and confirm the merchant URL before executing\n4. Use `kpass sandbox` test mode and the faucet to try a payment flow without real funds. Scoped cards are not available in sandbox\n5. Check the kite-passport skill's trigger rules before installing it, since it directs the agent to paid services ahead of free tools\n\n### Openfort\n\n1. Call `policies.evaluate` with operation `signEvmTransaction` before every EVM backend send. The send itself is checked only as `signEvmHash`\n2. Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail\n3. Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error\n4. Give an agent a secret key without `accounts:export`, and limit the CLI MCP server to the tools it needs\n5. On a 5xx after a write, read the resource before retrying. On a 429, wait the full `Retry-After`\n\n## Questions\n\n### Which is better for AI agents, Kite Agent Passport or Openfort?\n\nOpenfort scores 70.1 (BB) on agent readiness against Kite Agent Passport's 51.5 (D), and leads in 5 of 7 scored categories. Kite Agent Passport leads on security \u0026 auth.\n\n### Can an agent call Kite Agent Passport and Openfort without installing anything?\n\nNo hosted endpoint is listed for Kite Agent Passport. Openfort has a hosted endpoint at https://api.openfort.io.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort.json, and with the fewest tokens: https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"kite-agent-passport\", \"b\": \"openfort\"}`. From a terminal: `anchor compare kite-agent-passport openfort`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/kite-agent-passport.json and https://www.anchorterminal.com/api/v1/tools/openfort.json\n\n## Other comparisons with Kite Agent Passport or Openfort\n\n- [Agentcard vs Kite Agent Passport](https://www.anchorterminal.com/compare/agentcard-vs-kite-agent-passport.md)\n- [Circle Wallets (Agent Wallets, Programmable Wallets) vs Kite Agent Passport](https://www.anchorterminal.com/compare/circle-wallets-vs-kite-agent-passport.md)\n- [Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort](https://www.anchorterminal.com/compare/circle-wallets-vs-openfort.md)\n- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Kite Agent Passport](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-kite-agent-passport.md)\n- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Openfort](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-openfort.md)\n- [Kite Agent Passport vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/kite-agent-passport-vs-privy.md)\n- [Kite Agent Passport vs Sponge Wallet](https://www.anchorterminal.com/compare/kite-agent-passport-vs-sponge-wallet.md)\n- [Kite Agent Passport vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/kite-agent-passport-vs-turnkey-agentic-wallets.md)\n- [Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/openfort-vs-privy.md)\n- [Openfort vs Sponge Wallet](https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.md)\n- [Openfort vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.md)\n- [Agentcard vs Openfort](https://www.anchorterminal.com/compare/agentcard-vs-openfort.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-11", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Kite Agent Passport vs Openfort", "url": "" } ], "description": "Openfort scores 70.1 (BB) to Kite Agent Passport's 51.5 (D) for onchain wallets. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Kite Agent Passport D 51.5", "Openfort BB 70.1", "scores" ], "h1": "Kite Agent Passport vs Openfort", "image": "https://www.anchorterminal.com/assets/og/compare-kite-agent-passport-vs-openfort.png", "path": "/compare/kite-agent-passport-vs-openfort", "published": "2026-10-01", "section": "tools", "title": "Kite Agent Passport vs Openfort for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-10", "url": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-openfort" }, "tokens": { "markdown": 2350, "slim": 780 }, "version": 1 }