Run your go-to-market as one system
AgentCorp is the Agentic GTM Operating System. It finds and files leads into your CRM, and into HubSpot when HubSpot is connected. Alex, Sam, Taylor and Riley are how the system gets the work done. These docs cover setup, daily use, billing, integrations, and security.
Start here
New to AgentCorp? Work through these four in order. Most people are running real tasks within their first fifteen minutes.
From sign-up to your first completed task and your first send, step by step.
Working day to day: talking to Alex, tasking specialists, and the limits that still wait.
How usage and metering work, top-ups, invoices, and what happens when you run out.
Answers to common questions about the product, billing, security, and agents.
How AgentCorp works, in a sentence
You talk to Alex in plain language. Alex plans the work and routes it to the right specialist (Sam for sales and CRM, Riley for finance, Taylor for marketing), then reports back. The agents send email, messages and posts on their own. Payments and deleting your AgentCorp data still wait for your approval. A bulk email to more than 50 recipients waits for you. Work draws on a monthly usage allowance that refreshes in full each billing period and does not roll over, and every new workspace gets $50 of free usage when you add a payment method, valid during the 7-day trial. New to the idea of an AI workforce altogether? The AI workforce guide covers what one is, what it replaces, and what it costs against hiring.
Browse everything
- User guideWorking day to day: talking to Alex, tasking specialists, and the limits that still wait.
- Admin guideInvite teammates, manage roles and seats, control integrations and spend.
- Workspace guideOrganizations vs. workspaces, seats, switching, and data isolation.
- AI best practicesWrite clear instructions, set the autonomy dial, and get reliable output.
- IntegrationsConnect Gmail, Outlook, Notion, your CRM, Slack, WhatsApp, and Mercury.
- Knowledge baseUpload documents and facts so your agents have the right context.
- API referenceThe org-scoped auth model, representative request shapes, and rate limits.
- Developer guideJWT auth, events, the integration proxy, rate limits, and environments.