Upload to URL for AI agents
Upload to URL hosts files on public CDN URLs and can publish simple HTML pages, used by teams that need a quick, shareable link for a file or page. 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 Upload to URL.
Upload a file to a public URL
Upload a file and get back a shareable CDN link.
Get a file's metadata
Look up a previously uploaded file's details, a read-only check.
Confirm before deleting a file
Check with the user before deleting an uploaded file, since any link to it would break.
5 Upload to URL actions, graded by risk.
Every Upload to URL action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- upload_to_url.get_file_metadataGet File Metadata
- upload_to_url.get_supported_formatsGet Supported Formats
write
2Create and change things. Allow, or ask the user first.
- upload_to_url.upload_fileUpload File
- upload_to_url.publish_htmlPublish HTML
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- upload_to_url.delete_fileDelete File
Upload to URL in three steps.
- 01Your users connect Upload to URLThey add their Upload to URL api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “upload File” can wait for the user, and “delete File” can be denied outright.
- 03Any agent can actYour agent calls Upload to URL through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('upload_to_url', { read: 'allow', write: 'ask', // upload_file destructive: 'deny', // delete_file }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Upload to URL connects.
Users add their Upload to URL 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 Upload to URL 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 Upload to URL from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Upload to URL and Arc0, answered.
Can I use Upload to URL with Claude, ChatGPT or Cursor?
Yes. Connect Upload to URL 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 Upload to URL actions you allow.
How do users connect Upload to URL?
Users add their Upload to URL 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 Upload to URL actions can my agent take?
5 in total: 2 read, 2 write and 1 destructive, such as “upload File”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Upload to URL?
Yes. Actions like “delete File” 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 Upload to URL too?
Yes. The same Upload to URL connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Upload to URL into your agent.
Your users connect Upload to URL 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