Are.na for AI agents
Are.na is a platform for collecting and connecting research, letting users save links, images, and text into shared channels for creative and collaborative projects. 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 Are.na.
Save a link to a channel
Add a block to a channel to save a piece of research for later.
Browse a channel's saved content
List everything currently saved inside a specific research channel to review what is there.
Confirm before deleting a channel
Deleting a channel removes every block saved inside it, so it should be confirmed first.
10 Are.na actions, graded by risk.
Every Are.na action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- are_na.get_channelGet Channel
- are_na.get_my_feedGet My Feed
- are_na.get_current_userGet Current User
- are_na.list_channel_contentsList Channel Contents
write
3Create and change things. Allow, or ask the user first.
- are_na.create_channelCreate Channel
- are_na.update_channelUpdate Channel
- are_na.add_to_channelsAdd To Channels
destructive
3Delete, cancel or archive. Ask first, or deny outright.
- are_na.delete_channelDelete Channel
- are_na.remove_from_channelRemove From Channel
- are_na.get_blockGet Block
Are.na in three steps.
- 01Your users connect Are.naThey add their Are.na api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Channel” can wait for the user, and “delete Channel” can be denied outright.
- 03Any agent can actYour agent calls Are.na through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('are_na', { read: 'allow', write: 'ask', // create_channel destructive: 'deny', // delete_channel }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Are.na connects.
Users add their Are.na 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 Are.na 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 Are.na from any agent.
Are.na and Arc0, answered.
Can I use Are.na with Claude, ChatGPT or Cursor?
Yes. Connect Are.na 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 Are.na actions you allow.
How do users connect Are.na?
Users add their Are.na 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 Are.na actions can my agent take?
10 in total: 4 read, 3 write and 3 destructive, such as “create Channel”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Are.na?
Yes. Actions like “delete Channel” 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 Are.na too?
Yes. The same Are.na connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Are.na into your agent.
Your users connect Are.na once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan