Authoryze and Nekuda started out solving adjacent problems and have since moved apart. Authoryze is an MCP-native managed service. Connect it to your agent, and it issues a single-use virtual card per approved purchase with spending rules, human approval, and audit built in. Nekuda, through 2025, 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 (WebMCP Kit, webmcp.com directory, AgentLane) |
| Integration | Add one MCP server (Claude, ChatGPT, custom agents) | Claude Code, Codex, and Cursor plugin that generates WebMCP tools for a site |
| Payment model | Single-use virtual card issued per approved purchase | None documented today; legacy SDK injected stored card credentials and network tokens at checkout |
| Authorization | Server-side spending rules plus human email approval | Legacy mandates recorded signed user authorization; not in current docs |
| Spend controls | Per-transaction caps, daily/weekly/monthly limits, merchant allow/blocklists | None in current docs |
| Human approval | Built-in email approval flow with duplicate detection | None in current docs; legacy mandate captured authorization up front |
| Audit | Full logged history of agent purchases | AgentLane dashboard monitors WebMCP tool calls |
Managed Service vs Website Tooling
The core difference is which side of the transaction each product sits on. Nekuda's WebMCP Kit scans a website and generates the tool definitions an agent needs to act on it, with a directory of more than 600 sites and a dashboard for watching tool calls. That is merchant-side work, making a site legible to agents. Its legacy payments SDK is still on npm and PyPI, with last releases in December 2025 and March 2026, but the old wallet and mandates docs return 404 and we found no sunset notice, so whether it is still sold is unconfirmed.
Authoryze is buyer-side. The spending rules, approval flow, and audit are already built and enforced server-side, so there is little to assemble. If you are a website owner who wants agents to be able to act on your site, Nekuda's tooling is relevant. If you want agent spending governed and audited out of the box, the managed MCP service is the fit.
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, and a complete record, working with Claude, ChatGPT, or custom agents.
Sources
Nekuda claims on this page were checked on September 16, 2026 against nekuda.ai, its WebMCP post, its ChatGPT WebMCP post, docs.nekuda.ai, the webmcp-kit repo, 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