Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ascendgtm.net/llms.txt

Use this file to discover all available pages before exploring further.

​
What is Hermes?

Hermes is the autonomous agent layer built on top of the V5 Gateway. Where the Gateway exposes 34 MCP tools for AI coding assistants to call on demand, Hermes provides persistent agents that can:
  • Hold multi-turn conversations with context preserved across sessions
  • Run async jobs (analysis, enrichment, reporting) without a human in the loop
  • Execute scheduled workflows on daily or weekly cadences
  • Orchestrate across specialized agent roles (classifier → specialist → synthesiser)
Hermes runs as a separate Cloudflare Worker (ascend-agent-worker) that calls back into the V5 Gateway via a private service binding for tool execution. No tool credentials are duplicated — agents inherit the same KV token store as the gateway.

​
Architecture

Your AI tool (Claude, ChatGPT, Cursor…)
        ↓ MCP / HTTP
V5 Gateway (ascend-gateway-v5.ascendgtm.workers.dev)
   auth → token resolve → tool dispatch
        ↓ internal service binding
Hermes (ascend-agent-worker.ascendgtm.workers.dev)
   agent loop → tool calls → state storage
        ↓ reads KV
Connected SaaS APIs (HubSpot, Google Ads, GA4…)
The agent loop runs inside Hermes. Each iteration calls the gateway’s /internal/tool endpoint, which executes the tool and returns the result. From the tool’s perspective, it’s the same execution path as a direct MCP call.

​
Agent types

An agent config defines a named role. Each config specifies:
FieldDescription
modelModel identifier (e.g. claude-sonnet-4-5, gpt-4o)
max_tokensMax tokens per iteration (256–32768, default 4096)
max_iterationsMax reasoning iterations before forced stop (1–20, default 6)
system_promptRole-defining system prompt
toolsList of gateway tool names this agent can call
classifier_modelOptional — separate model for intent classification
synthesis_modelOptional — separate model for final output synthesis
Agent configs are stored in KV at agent_config:{tenant}:{agent_type} and managed via the Admin API.

​
Common agent types

TypeRoleTypical tools
gtm_analystGTM performance analysisgoogle_ads, ga4, hubspot_crm, salesforce_query
outreach_writerCold email and sequence draftingperplexity_search, web_fetch, gmail
crm_enricherContact and account enrichmenthubspot_crm, salesforce_crm, discover_apis, perplexity_search
orchestratorRoutes requests to specialist agents(no direct tools — classifies intent)
report_builderWeekly/monthly performance reportsgoogle_ads, ga4, linkedin_ads, aws_ses

​
Next steps

Chat sessions

Start a conversation with an agent

Async jobs

Kick off background agent tasks

Orchestrator pattern

Route requests across specialized agents

Scheduled jobs

Automate recurring agent workflows