Set up from your editor
Your agent sets up Apex. You stay in charge.
Install Apex in Cursor, VS Code, or Claude Code, then tell your agent to set up Apex in this repo. It names your shop, wires your events, and checks every one against Apex. It asks before it skips anything.
No credit card to start. No key to paste.
Install
Add Apex to your editor once.
One install works in every repo. Each repo names its own shop in .apex/workspace.json, so a second company never lands in the first one's data.
Using Claude Code? Run this in your terminal
claude mcp add --scope user --env APEX_URL=https://app.apex.inc apex -- npx -y -p @apex-inc/mcp-server mcp-serverThen tell your agent
Set up Apex in this repo.The first time your agent calls Apex, it gives you a link to approve in the browser. There is no key to paste. In Cursor you can also run /setup-apex.
What happens next
Four steps, in order.
Your agent reads the Set up Apex checklist after every change, so it always works the next real step.
- Your agent gives you a link to approve it in the browser. Sign in or create your account there.
- It reads your repo and names the shop. A separate company gets its own organization.
- It wires your events and waits until Apex sees each one arrive.
- It asks what counts as a conversion, then works the rest of the checklist with you.
What still needs you
A few steps need a person in a browser.
When your agent reaches one, it gives you the link and the reason, then waits. It never marks a step done for you. Steps finish when the real thing happens.
- Connecting Stripe, Shopify, GitHub, or your ad accounts. You sign in on their site.
- Verifying your sending domain. You add the DNS records where your domain lives.
- Accepting the terms that come with payouts and messaging.
Your move
Rather click through it?
Set up Apex in the browser works the same checklist. You can hand it to your editor at any step.