Answers from your agent, not a scraped page.
When a prospect researches you in ChatGPT, Claude, Gemini, or Grok, their agent reads whatever it can find. The Agent Gateway gives it a live conversation with your customer agent instead, with your current positioning and pricing.
- Standard discovery: a manifest at a well-known path, plus an HTTP Link header on every page
- Any agent can connect: a plain HTTP conversation API and a public MCP endpoint
- You control the story: answers come from the agent you trained, always current
It qualifies the buyer behind the agent.
A docs endpoint answers and hangs up. The gateway works your definition of qualified into the conversation and captures the person the agent is working for.
- Your criteria, applied to agent callers: the same bar your website agent uses
- Contact capture: the prospect 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 an agent conversation to a real next step.
Once the buyer qualifies, the gateway starts a trial or books a demo, and hands them to the in-app agent with the whole conversation attached.
- Trial or demo: the outcome your rules call for, started inside the agent conversation
- One shared memory: the gateway conversation follows the prospect onto your site and into your product
- Guardrails built in: every session logged, 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 services your agent runs today get published beside the gateway, so a customer's own agent can find one 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 names a service, or asks your gateway which one it needs
- Same authorization: whichever door the customer comes through, the same account and permissions
Hartwell Mechanical
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
How it works
The gateway is the same customer agent, reached by another agent instead of a person.
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.