Abstract for AI agents
Abstract API is a suite of developer APIs for validating and enriching data, covering emails, IBANs, VAT categories and more. Developers use it to check data quality before it hits a database. 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 Abstract.
Validate an email address
Check whether an email address is real and well-formed before it is added to a contact list.
Validate an IBAN
Confirm a bank account number is a correctly structured IBAN before it is used for a payment.
Look up VAT categories
Pull the list of VAT categories that apply in a given country to price an invoice correctly.
3 Abstract actions, graded by risk.
Every Abstract 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.
- abstract.get_vat_categoriesGet VAT Categories
write
2Create and change things. Allow, or ask the user first.
- abstract.iban_validation_apiValidate IBAN
- abstract.email_reputation_apiEmail validation and quality check
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Abstract in three steps.
- 01Your users connect AbstractThey add their Abstract api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “validate IBAN” can wait for the user to approve.
- 03Any agent can actYour agent calls Abstract through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('abstract', { read: 'allow', write: 'ask', // iban_validation_api destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Abstract connects.
Users add their Abstract 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 Abstract 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 Abstract from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Abstract and Arc0, answered.
Can I use Abstract with Claude, ChatGPT or Cursor?
Yes. Connect Abstract 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 Abstract actions you allow.
How do users connect Abstract?
Users add their Abstract 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 Abstract actions can my agent take?
3 in total: 1 read, 2 write and 0 destructive, such as “validate IBAN”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Abstract?
Yes. Allow read actions and deny writes in the Abstract policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Abstract too?
Yes. The same Abstract connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Abstract into your agent.
Your users connect Abstract once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan