Currents API for AI agents
Currents API delivers recent news articles from sources worldwide, letting an app or agent search current events across languages and categories. 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 Currents API.
Search news by keyword
Search recent news articles for a keyword before summarizing what's being reported.
Check the latest headlines
List the latest news across categories to spot what's trending right now.
Check entity usage reports
Get an entity usage report to see how a specific topic is trending in coverage.
5 Currents API actions, graded by risk.
Every Currents API action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
5Create and change things. Allow, or ask the user first.
- currents_api.users_listList Users
- currents_api.activities_listList Latest News
- currents_api.activities_watchActivities Watch
- currents_api.user_usage_report_getSearch News Articles
- currents_api.entity_usage_reports_getGet Entity Usage Reports
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Currents API in three steps.
- 01Your users connect Currents APIThey add their Currents API api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “list Users” can wait for the user to approve.
- 03Any agent can actYour agent calls Currents API through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('currents_api', { read: 'allow', write: 'ask', // users_list destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Currents API connects.
Users add their Currents API 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 Currents API 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 Currents API from any agent.
Currents API and Arc0, answered.
Can I use Currents API with Claude, ChatGPT or Cursor?
Yes. Connect Currents API 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 Currents API actions you allow.
How do users connect Currents API?
Users add their Currents API 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 Currents API actions can my agent take?
5 in total: 0 read, 5 write and 0 destructive, such as “list Users”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Currents API?
Yes. Allow read actions and deny writes in the Currents API policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Currents API too?
Yes. The same Currents API connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Currents API into your agent.
Your users connect Currents API 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