Your buyers send their agents ahead. Answer them.
The Agent Gateway is a public conversational endpoint for visiting AI agents. When a prospect researches you in ChatGPT, Claude, Gemini, or Grok, their agent talks to your customer agent instead of scraping stale pages.
How it works
The gateway is the same customer agent, reached by another agent instead of a person, with the same memory and the same connection to your product.
1Connect your product's MCP.
Aimdoc works through the tools your product already exposes. No integration code.
2Aimdoc authenticates as each customer.
Every call runs as that user, with their permissions, in their account.
3The agent and every service do real work.
In your app, over email, on your site, or for another agent. Where a tool is missing, a task definition teaches the browser path.
Discoverable, current, and under your control.
Your site advertises the gateway through a standard manifest, so what an AI says about your product comes from a live agent you control.
- Standard discovery: a manifest at a well-known path plus an HTTP Link header on every page
- Two surfaces: a plain HTTP conversation API and a public MCP endpoint, so any agent can connect
- You control the story: answers come from your trained agent with your positioning and pricing, always current
An endpoint that qualifies, not just answers.
Documentation endpoints answer questions and hang up; the gateway works your criteria into the conversation and captures the contact behind the agent.
- Your definition of qualified: the same criteria your website agent applies, applied to agent callers
- Contact capture: the prospect behind the agent lands in your CRM with the full conversation
- Human escalation: sessions hand off to your team the moment judgment is required
Matthew Smith
matthew@hartwell.io
From the conversation
Company size
"we're a 60-person team"
Use case
"leads need to reach the right rep"
Stack
"everything lives in HubSpot"
Timeline
"hoping to switch before Q4"
From agent conversation to a real next step.
Once a prospect qualifies, the gateway starts a trial or books a demo, and hands the prospect to the in-app agent with the whole conversation attached.
- Trial or demo: the outcome your rules call for, started from inside the agent conversation
- One shared memory: the gateway conversation follows the prospect onto your website and into your product
- Guardrails built in: logging on every session, rate limits, and human confirmation where you want it
Can it route new trial signups to the right rep in HubSpot?
Yes — and I can set it up with you. Start a trial and I'll bring this conversation in with me.
Welcome back, Matthew. Let's connect HubSpot first — I'll do the setup with you.
Next: their agents find your catalog.
The same catalog of services your agent runs today is published next to the gateway, so a customer's own agent can find a service and ask for the outcome.
- Published with the gateway: your services listed in the format agents read, at the same well-known path
- Direct or assisted: an agent asks your gateway which service it needs, or names one directly
- Same authorization: whichever door the customer comes through, the same account and the same permissions
Hartwell Logistics
4 services configured to this account
- running
Weekly account audit
Mondays, 7:00 · Fixed 3 drifted settings
- running
Usage drop monitor
Continuous · Emailed 2 accounts this week
- scheduled
Monthly executive report
1st of the month · Sent to 4 recipients
- running
Failed sync investigation
On trigger · 2 resolved, 1 escalated