Authoryze is spend control you can switch on today: connect one MCP server and your agent gets per-agent and cross-agent limits, merchant rules, human approval over a threshold, duplicate detection, and a single-use card per approved purchase, with an audit trail per member and agent and shared envelopes for teams. Nekuda started on an adjacent problem and has since moved away from it. Through 2025 it was a developer SDK that gave agents a wallet to store and inject the user's payment credentials at checkout, plus mandates that recorded signed proof of user authorization. As of September 2026, Nekuda's site and docs are about WebMCP, a W3C-track standard originated by Google and Microsoft that lets websites expose actions to agents, and the payments SDK is no longer documented.
Feature Comparison
| Feature | Authoryze | Nekuda |
|---|---|---|
| Form factor | MCP-native managed service | WebMCP tooling for websites |
| Integration | Add one MCP server (Claude, ChatGPT, Meta's Muse, custom agents) | Plugin that generates WebMCP tools for a site |
| Payment model | Single-use card issued per approved purchase, through the card networks' agentic programs (Visa Intelligent Commerce and Mastercard Agent Pay) | None documented today; legacy SDK injected stored card credentials and network tokens at checkout |
| Authorization | Server-side spending rules plus human approval | Legacy mandates recorded signed user authorization; not in current docs |
| Spend controls | Per-transaction caps, daily/weekly/monthly limits, merchant allow/blocklists, aggregate caps across agents | None in current docs |
| Human approval | Built-in approval flow by email and dashboard, with duplicate detection | None in current docs; legacy mandate captured authorization up front |
| Teams | Shared team envelope, approvers, per-member and per-agent records, one monthly plan | None in current docs |
| Audit | Full logged history of agent purchases | Dashboard monitors WebMCP tool calls |
Managed Service vs Website Tooling
The core difference is which side of the transaction each product sits on. Authoryze is buyer-side. The spending rules, approval flow, and audit are already built and enforced server-side, so there is nothing to assemble. When a purchase is approved, the agent gets the single-use card directly from retrieve_card and checks out at any merchant that takes Visa or Mastercard.
Nekuda's WebMCP tooling is merchant-side work, making a site legible to agents by generating the tool definitions an agent needs to act on it. Its legacy payments SDK is still published on npm and PyPI, but the old wallet and mandates docs return 404 and we found no sunset notice, so whether it is still sold is unconfirmed.
When Authoryze Is the Right Choice
Choose Authoryze if you want agent card spending that is governed and auditable without building the flow yourself. A single MCP connection, per-agent and cross-agent limits, human approval over thresholds, duplicate-purchase protection, shared team envelopes, and a complete record, working with Claude, ChatGPT, Meta's Muse, or custom agents.
Sources
Nekuda claims on this page were checked on September 16, 2026 against nekuda.ai, its WebMCP post (nekuda.ai/blog/webmcp-every-website-is-getting-an), its ChatGPT WebMCP post (nekuda.ai/blog/breaking-chatgpt-now-supports-webmcp), docs.nekuda.ai, the nekuda-ai/webmcp-kit repository on GitHub, and the webmcp.com directory. If something has changed since, let us know.
More comparisons: Authoryze vs Crossmint · Authoryze vs Locus · Authoryze vs Payman · Authoryze vs Skyfire · Authoryze vs Stripe Link for agents · Authoryze vs Allowance