Era Context for AI agents
Era Context gives agents access to a user's connected financial accounts, spending insights, and billing, across banking and brokerage data. 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 Era Context.
Check an account balance
Check the balance on a connected account before answering a user's spending question.
Analyze recent spending
Analyze spending across categories to give the user a summary of where money went this month.
Confirm before disconnecting a bank
Require approval before disconnecting a bank connection, since it stops future syncing from that institution.
51 Era Context actions, graded by risk.
Every Era Context 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
49Create and change things. Allow, or ask the user first.
- era_context.help__get_helpHelp get help
- era_context.billing__upgradeBilling upgrade
- era_context.knowledge__forgetKnowledge forget
- era_context.billing__list_plansBilling list plans
- era_context.knowledge__rememberKnowledge remember
- era_context.billing__list_paymentsBilling list payments
- era_context.nurture__get_my_statusNurture get my status
- era_context.insights__get_cash_flowInsights get cash flow
- era_context.accounts__manage_accountAccounts manage account
- era_context.billing__get_current_planBilling get current plan
- era_context.knowledge__defer_questionKnowledge defer question
- era_context.knowledge__recall_historyKnowledge recall history
- era_context.nurture__set_subscriptionNurture set subscription
- era_context.insights__analyze_spendingInsights analyze spending
- era_context.billing__list_subscriptionsBilling list subscriptions
- era_context.insights__forecast_spendingInsights forecast spending
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- era_context.billing__cancel_subscriptionBilling cancel subscription
- era_context.knowledge__reset_pack_questionsKnowledge reset pack questions
Era Context in three steps.
- 01Your users connect Era ContextThey sign in to Era Context on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, writes like “help get help” can wait for the user, and “billing cancel subscription” can be denied outright.
- 03Any agent can actYour agent calls Era Context through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('era_context', { read: 'allow', write: 'ask', // help__get_help destructive: 'deny', // billing__cancel_subscription }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Era Context connects.
Era Context runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Era Context through the same endpoint, policies and audit log as every other app.
The same Era Context 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
- OAuth 2.0 (MCP)
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Era Context from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore finance and accounting apps.
Era Context and Arc0, answered.
Can I use Era Context with Claude, ChatGPT or Cursor?
Yes. Connect Era Context 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 Era Context actions you allow.
How do users connect Era Context?
Era Context runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Era Context through the same endpoint, policies and audit log as every other app.
Which Era Context actions can my agent take?
51 in total: 0 read, 49 write and 2 destructive, such as “help get help”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Era Context?
Yes. Actions like “billing cancel subscription” 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 Era Context too?
Yes. The same Era Context connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Era Context into your agent.
Your users connect Era Context once, under your brand. Your agent gets 51 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan