Clozure’s Agent API and MCP onboarding server: what AI-agent builders should check first (Oct 2026)

Affiliate disclosure. This post has one ClickBank affiliate link for Clozure (seller nickname CLOZURE; affiliate nickname pointerr). If you buy through that link, ShopperCove may earn a commission at no extra cost to you. ClickBank is the retailer of products on the vendor site. CLICKBANK® is a registered trademark of Click Sales, Inc. ClickBank acting as retailer does not mean it endorses, approves, or reviews this product or any claim used to promote it.

ShopperCove has not registered an agent tenant, topped up a wallet, connected the MCP server to an agent, or bought a subscription. Facts below come from Clozure’s public machine-readable files and one unauthenticated read-only GET /plans call, all fetched 5 Oct 2026. This is not a hands-on lab, not a rating, and not earnings advice.

No paid ads. There is no second affiliate link in this article.

Why this is not the Clozure review again

ShopperCove already published a Clozure AI Business OS review. That post covers the human product: the $99/month ClickBank subscription, the claimed 14-day trial, AI departments, and a warning that a sales tool is a poor fit for an engineering blog.

This post covers a different surface, one that fits a developer audience better. Clozure now publishes an agent-as-principal program where an AI agent can sign itself up, pay into its own prepaid wallet, pick a plan, and run Clozure “departments”. It does this through an A2A agent card, an OpenAPI 3.0.3 spec, an MCP onboarding server, and an ERC-8004 registration file. If you build agents, these are the files your agent would actually read, so this post looks at what they say.

The machine-readable files (as published)

File	What it says (vendor claim)	Status 5 Oct 2026
/.well-known/agent-card.json	A2A card, protocolVersion 1.0, card version 1.2.0, served as application/a2a+json; 8 skills (self-register, domain + mailbox setup, department enablement, wallet top-up, plans, affiliate referral, REST API, MCP onboarding)	200; legacy /.well-known/agent.json returns a 308 redirect to this card
/.well-known/openapi.json	“Clozure Agent Tenant API” v1.1.0, base https://clozure.net/api/agent-tenant, 13 operations	200
/.well-known/agent-registration.json	ERC-8004 registration file: active: true, supportedTrust: ["reputation"], registrations: [], x402Support: false	200
/llms.txt	Summary for LLMs: agent API, MCP server at /mcp/agent-onboarding, a claimed official MCP Registry name net.clozure/agent-onboarding	200

The 13 OpenAPI operations: POST /self-register, POST /auth, GET /plans, GET /identity, GET /wallet, POST /wallet/checkout, POST /subscription/charge, GET /affiliate, POST /policy/check, GET /outbound-cap, GET /departments, POST /departments/enable, POST /departments/disable.

Agent plans vs the human ClickBank price

An unauthenticated GET /plans on 5 Oct 2026 returned three agent tiers. These are paid from the agent’s wallet:

planId	Price	Departments	Monthly limits
agent_starter	$29	Sales, Marketing	200 leads · 2,000 emails · 10 social posts
agent_growth	$79	Sales, Marketing, Finance, Support	1,000 leads · 10,000 emails · 50 social posts
agent_enterprise	$199	Sales, Marketing, Finance, Support, COO, Lead Gen	5,000 leads · 50,000 emails · 200 social posts

The human offer page that ClickBank sends buyers to (clozure.net/offer) still lists $99/month, with that charge covering a 14-day trial and monthly rebills of $99 until you cancel. These are two separate billing paths. The agent tiers are wallet-funded through Stripe or x402. The human tier is a recurring ClickBank subscription. Do not mix up the prices.

How signup and the wallet work (per the spec)

• Identity: POST /self-register asks for a Moltbook agent name and Moltbook API key, plus an email and password. The spec says the Moltbook key is checked once and never stored. Repeat calls with the same moltbookAgentName return the existing identity and a new JWT. If your agent has no Moltbook identity, this path is closed.
• Wallet: top-ups start at $5 (amountCents >= 500). The spec describes three ways to pay: a Stripe Shared Payment Token, an x402 PAYMENT-SIGNATURE header settling USDC on Base, or an HTTP 402 response with a hosted Stripe checkout link. The wallet “hard-stops at zero”, with no credit and no overdraft.
• Guardrails: POST /policy/check (tenant status, balance, per-agent spend caps) and GET /outbound-cap (kill switch, daily and hourly send caps) exist as endpoints. The spec does not say who sets those caps or what the defaults are.
• MCP server: https://clozure.net/mcp/agent-onboarding (Streamable HTTP, stateless JSON) exposes get_plans, self_register, get_wallet, create_affiliate_link, top_up_wallet. The agent JWT goes in as a bearer token.

What to check before you let an agent connect

1. Referral codes ride along on every response. GET /plans and self-register responses include a swarm_meta block that always carries a referral code (a “house” code when you are not signed in), and the spec says referral codes “propagate as a side effect of ordinary API use.” Every agent is auto-enrolled in a 30% recurring affiliate program with a 5% second tier. If your agent writes outbound content, filter these fields so it does not start pasting referral links into emails or posts you never approved.
2. Spending money without a human. The whole design is “no human required”. Set your own wallet ceiling outside Clozure: a small top-up, a separate card or Stripe account, and alerts. Do not rely only on the vendor’s policy endpoint.
3. Outbound email and domains. The agent card says Clozure can provision a domain and a Google Workspace mailbox for “autonomous email-based outreach”. Before an agent sends anything, check CAN-SPAM and local rules, unsubscribe handling, and whose name and reputation go on that domain.
4. Files that disagree. The ERC-8004 file says x402Support: false, but the OpenAPI spec and agent card describe x402 USDC top-ups. The same file lists no on-chain registrations. Treat “trustless agent” identity as not yet proven.
5. The registry claim. llms.txt names net.clozure/agent-onboarding as an official MCP Registry entry. A ShopperCove search of the public registry for “clozure” on 5 Oct returned zero results (later searches timed out). Treat the listing as unverified.
6. Track record. Clozure’s own llms.txt says it was founded in 2025. Earlier marketplace scouting showed Gravity 0 for the ClickBank offer. Use a throwaway agent identity and test data, not production mailboxes or CRM.
7. Read the terms. Read the terms, privacy policy, and affiliate terms (/terms, /privacy-policy, /affiliates) before an agent “accepts” anything on your behalf. ShopperCove did not audit them.

Who this angle fits

It fits developers building autonomous or semi-autonomous agents who want to see what an “agent pays for its own SaaS” onboarding flow looks like in practice: the A2A card, OpenAPI, MCP tools, 402 or x402 payments, and wallet caps. It is useful as a reference design even if you never subscribe.

It does not fit readers who want proven lead or close-rate numbers (we have none), teams without a Moltbook agent identity, or anyone who will not put their own spending and outbound limits around an agent.

Where the affiliate hop fits

Affiliate CTA. Open Clozure via ShopperCove’s ClickBank hop. The hop resolves to clozure.net/offer, which is the human $99/month ClickBank subscription, not the agent-tenant API. It is not a Clozure agent referral code, and ShopperCove does not inject referral headers into agent signups. Check the trial, rebill, and refund path (ClickBank Order Support or support@clozure.net) before you pay. No second hop. No TrekMail. No paid ads.

Bottom line

As of 5 Oct 2026, Clozure publishes a fairly complete machine interface for agents as customers: an A2A card, OpenAPI with 13 operations, an MCP onboarding server, Stripe and x402 wallet top-ups, and agent plans at 79 / $199. Things that need care: automatic referral propagation, a missing on-chain registration, an x402 flag that contradicts the spec, and an MCP Registry listing we could not confirm. Read the files. Fence the wallet and the outbound sending. Test with a throwaway identity. This is a different angle from the live Clozure review, and there is still no ShopperCove lab behind it.

Sources

• https://clozure.net/.well-known/agent-card.json
• https://clozure.net/.well-known/openapi.json
• https://clozure.net/.well-known/agent-registration.json
• https://clozure.net/llms.txt
• https://clozure.net/api/agent-tenant/plans
• https://clozure.net/offer
• https://www.shoppercove.com/blog/clozure-ai-business-os-review
• https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking

Related

• https://www.shoppercove.com/blog/clozure-ai-business-os-review
• https://www.shoppercove.com/blog/setting-up-ai-coworkers-openbot
• https://www.shoppercove.com/blog/deploying-deepseek-harness-routing-suite
• https://www.shoppercove.com/blog/localtry-mcp-crm-indie-site-workflow-2026
• https://www.shoppercove.com/blog/ai-seo-answer-engines-chatgpt-perplexity-2026
• https://www.shoppercove.com/blog/ai-traffic-secrets-aeo-wordpress-daily-posts-october-2026
• https://www.shoppercove.com/blog/grow-site-traffic-ai-search-era-2026
• https://www.shoppercove.com/blog/ready-client-sites-nodejs-freelancer-websites-2026