Onepage for AI agents
OnePage is a data-enrichment API that looks up user and company details through a simple search endpoint. Sales and product teams use it to fill in missing profile information. 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 Onepage.
Enrich a company or person record
Run a search request to fill in missing details for a lead before it enters a CRM.
Validate an access token
Check token details read-only to confirm API access is valid before running a batch lookup.
Batch enrich a lead list
Run enrichment searches across a list of prospects ahead of an outbound campaign.
2 Onepage actions, graded by risk.
Every Onepage 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.
- onepage.search_input_post_requestSearch input post request
write
1Create and change things. Allow, or ask the user first.
- onepage.token_details_requestToken details request
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Onepage in three steps.
- 01Your users connect OnepageThey add their Onepage bearer token on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “token details request” can wait for the user to approve.
- 03Any agent can actYour agent calls Onepage through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('onepage', { read: 'allow', write: 'ask', // token_details_request destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Onepage connects.
Users add their Onepage bearer token 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 Onepage 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
- Bearer token
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Onepage from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Onepage and Arc0, answered.
Can I use Onepage with Claude, ChatGPT or Cursor?
Yes. Connect Onepage 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 Onepage actions you allow.
How do users connect Onepage?
Users add their Onepage bearer token 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 Onepage actions can my agent take?
2 in total: 1 read, 1 write and 0 destructive, such as “token details request”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Onepage?
Yes. Allow read actions and deny writes in the Onepage policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Onepage too?
Yes. The same Onepage connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Onepage into your agent.
Your users connect Onepage once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan