Goodbits for AI agents
Goodbits helps teams turn the best links their team and customers are reading into curated newsletters. Marketers fold it into their existing outreach and campaign workflow instead of running it separately. 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 Goodbits.
Add a link to the newsletter queue
Save an article link with a note so it is queued for the next curated newsletter issue.
Check newsletter subscriber info
Look up the current newsletter's subscriber count and settings before drafting a new issue.
Remove a subscriber with confirmation
Delete a subscriber record only after confirming the unsubscribe request is genuine.
5 Goodbits actions, graded by risk.
Every Goodbits 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.
- goodbits.get_newsletterGet Newsletter Info
write
3Create and change things. Allow, or ask the user first.
- goodbits.create_linkCreate Link
- goodbits.create_subscriberCreate Subscriber
- goodbits.update_subscriber_statusUpdate Subscriber Status
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- goodbits.delete_subscriberDelete Subscriber
Goodbits in three steps.
- 01Your users connect GoodbitsThey add their Goodbits api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Link” can wait for the user, and “delete Subscriber” can be denied outright.
- 03Any agent can actYour agent calls Goodbits through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('goodbits', { read: 'allow', write: 'ask', // create_link destructive: 'deny', // delete_subscriber }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Goodbits connects.
Users add their Goodbits 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 Goodbits 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 Goodbits from any agent.
Goodbits and Arc0, answered.
Can I use Goodbits with Claude, ChatGPT or Cursor?
Yes. Connect Goodbits 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 Goodbits actions you allow.
How do users connect Goodbits?
Users add their Goodbits 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 Goodbits actions can my agent take?
5 in total: 1 read, 3 write and 1 destructive, such as “create Link”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Goodbits?
Yes. Actions like “delete Subscriber” 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 Goodbits too?
Yes. The same Goodbits connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Goodbits into your agent.
Your users connect Goodbits once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan