[hiroTamada]

Warning

Blocked on the @onkernel/sdk 0.133.0 release. This code is written against the 0.133.0 types, but 0.133.0 is not published yet; package.json and bun.lock still pin 0.132.0. A git pin to the release PR head does not install cleanly with bun (the SDK's prepare build is skipped, so the package has no dist/), so the dependency is left unchanged. Until the bump, CI's Type check fails on the new SDK types (payment_request items, the add_payment_method / remove_payment_method operation params); tests pass on both versions. Before merge: bun add @onkernel/sdk@0.133.0, commit package.json + bun.lock, and re-run CI.

Summary

The Kernel API now supports multiple cards per Kernel wallet and payment_request purchase items, gated per organization. This updates the vault tools to match, keeping the original single-card Kernel wallet contract working for organizations without the flags.

Wallets (manage_vault_wallets)

• New add_payment_method and remove_payment_method (with payment_method_id) actions. Each one fetches the wallet first and submits only if it is a Kernel wallet that advertises the operation, matching how authorize works in manage_vault_cards. The result returns the projected payment method or removal status, a payment_methods observation hint, and guidance.
• add_payment_method returns the card_enrollment url, but the embedded capture_token is still never returned.
• Errors go through the Kernel error path, so 403 insufficient_scope, 409 purchase_unresolved / provider_revocation_pending and 429 Retry-After pass through.
• Updated the description: a Kernel wallet may be connected and empty; enrollment urls go only to the intended cardholder; removal needs user confirmation and is not proof a payment did not occur; add and remove need vaults:write.
• destructiveHint is now true, because removal deletes a stored card.

Cards (manage_vault_cards)

• New item_type (card by default, or payment_request) for create/update. Link and Kernel can create payment_request items; AgentCard is refused locally. Updates to a payment request send type: payment_request; card updates still omit type.
• The Kernel card spec accepts an optional payment_method_id. If omitted, the API selects the default card card and never another card. A Kernel payment_request requires it.
• authorize also accepts payment_request items.

Responses and manage_vault_items

• Payment methods now project status, status_reason, expires_at and action (name, url, expires_at, without capture_token). Item state projects payment_method_id and funding_status. Event data projects item_type, provider and payment_method_id_present.
• Operation results project payment_method and payment_method_id, so invoking add_payment_method / remove_payment_method through manage_vault_items renders and gets guidance.
• payment_request items are treated like cards in guidance, invocation hints, recovery_required handling, Link authorize error mapping and the confirm_transaction amount/currency check.
• A remove_payment_method hint lists required_inputs: ["payment_method_id"].
• Kernel wallet guidance covers empty wallets, method statuses and removal. It now says reconnect_required wallets refuse payment and deletion until upgraded, per the current API description. Kernel purchase guidance explains funding_status.
• Updated docs/vault-payments.md.

Entitlements, tool names, registration, analytics and deprecated-params handling do not enumerate vault operations or item types, so they are unchanged.

Tests

Run locally with @onkernel/sdk 0.133.0 built from the release PR head and swapped into node_modules, without committing it:

• bunx tsc --noEmit --incremental false: passes on 0.133.0. On the pinned 0.132.0 it fails only where the new SDK types are used.
• bun test: 1161 pass, 0 fail on both 0.133.0 and 0.132.0.
• bun run check:managed-auth-app: passes.
• bunx prettier --check on changed files: passes. Repo-wide bun run format:check fails only on AGENTS.md, which this PR does not touch.
• git diff --check: clean.
• bun run lint was not run; it is broken under Next.js 16 per AGENTS.md.

Not run: no live MCP calls against the Kernel API with the flags on.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
mcp	Error		Oct 28, 2026 2:27pm UTC