Zylvie for AI agents
Zylvie is checkout software for solopreneurs selling digital products and subscriptions, used by creators who want a simple cart without a full e-commerce platform. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Zylvie.
Create a new product
Set up a new digital product or subscription for sale.
Get the authenticated user
Confirm which account is connected as a read-only identity check.
Confirm before unsubscribing a webhook
Check with the user before removing a webhook subscription, since downstream automations depending on it would stop.
4 Zylvie actions, graded by risk.
Every Zylvie action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- zylvie.get_authenticating_userGet Authenticating User
write
2Create and change things. Allow, or ask the user first.
- zylvie.create_productCreate Product
- zylvie.subscribe_webhookSubscribe Webhook
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- zylvie.unsubscribe_webhookUnsubscribe Webhook
Zylvie in three steps.
- 01Your users connect ZylvieThey add their Zylvie api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Product” can wait for the user, and “unsubscribe Webhook” can be denied outright.
- 03Any agent can actYour agent calls Zylvie through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('zylvie', { read: 'allow', write: 'ask', // create_product destructive: 'deny', // unsubscribe_webhook }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Zylvie connects.
Users add their Zylvie api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Zylvie connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Zylvie from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Zylvie and Arc0, answered.
Can I use Zylvie with Claude, ChatGPT or Cursor?
Yes. Connect Zylvie to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Zylvie actions you allow.
How do users connect Zylvie?
Users add their Zylvie api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Zylvie actions can my agent take?
4 in total: 1 read, 2 write and 1 destructive, such as “create Product”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Zylvie?
Yes. Actions like “unsubscribe Webhook” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Zylvie too?
Yes. The same Zylvie connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Zylvie into your agent.
Your users connect Zylvie once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan