Page X for AI agents
PageX combines a CRM, page builder, and course builder so small businesses can manage leads, build websites, and sell courses in one platform. Founders use it to run marketing and sales together. 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 Page X.
Create a new lead
Add a lead captured from a landing page or form directly into the CRM pipeline.
Log a lead from a webinar signup
Create a lead record right after someone registers for a course or webinar.
Add a lead with approval before follow-up
Create a lead and hold it for a sales rep to review before any outreach begins.
1 Page X actions, graded by risk.
Every Page X 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
1Create and change things. Allow, or ask the user first.
- page_x.create_leadCreate Lead
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Page X in three steps.
- 01Your users connect Page XThey add their Page X api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Lead” can wait for the user to approve.
- 03Any agent can actYour agent calls Page X through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('page_x', { read: 'allow', write: 'ask', // create_lead destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Page X connects.
Users add their Page X 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 Page X 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 Page X from any agent.
Page X and Arc0, answered.
Can I use Page X with Claude, ChatGPT or Cursor?
Yes. Connect Page X 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 Page X actions you allow.
How do users connect Page X?
Users add their Page X 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 Page X actions can my agent take?
1 in total: 0 read, 1 write and 0 destructive, such as “create Lead”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Page X?
Yes. Allow read actions and deny writes in the Page X policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Page X too?
Yes. The same Page X connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Page X into your agent.
Your users connect Page X once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan