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.

​
Starting a session

Send a POST to the Hermes chat endpoint with your message and the agent type you want to use: 
curl -X POST https://ascend-agent-worker.ascendgtm.workers.dev/chat \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "What are my top 5 Google Ads campaigns by ROAS this month?",
    "agent_type": "gtm_analyst"
  }'
Response: 
{
  "session_id": "ses_01J...",
  "response": "Here are your top 5 campaigns by ROAS for May 2026...",
  "tool_calls": [
    { "tool": "google_ads_query", "status": "success" },
    { "tool": "ga4_report", "status": "success" }
  ],
  "iterations": 2,
  "status": "complete"
}

​
Continuing a session

Include session_id to resume the conversation with full context: 
curl -X POST https://ascend-agent-worker.ascendgtm.workers.dev/chat \
  -H "Authorization: Bearer <your-token>" \
  -H "Content-Type: application/json" \
  -d '{
    "session_id": "ses_01J...",
    "message": "Which of those has the highest impression share?"
  }'
The agent remembers the previous exchange — no need to repeat context.

​
Session state

Hermes persists session context in the gateway’s KV store via agent_state:
  • Sessions are scoped to {tenant}:{session_id} — fully isolated across tenants
  • Session state TTL defaults to 24 hours (configurable up to 720 hours / 30 days)
  • Tool call results within a session are included in the agent’s context window

​
Request parameters

ParameterTypeRequiredDescription
messagestringYesThe user message / instruction
agent_typestringYesAgent config to use (e.g. gtm_analyst)
session_idstringNoResume an existing session
contextobjectNoAdditional context injected into the prompt
max_iterationsintegerNoOverride the config’s max_iterations (1–20)

​
Response fields

FieldDescription
session_idSession identifier for follow-up turns
responseAgent’s final text response
tool_callsArray of {tool, status, duration_ms} for observability
iterationsHow many reasoning loops the agent ran
statuscomplete, max_iterations_reached, or error
usageToken counts {prompt, completion, total}

​
Error handling

If the agent exceeds max_iterations, it returns with status: "max_iterations_reached" and whatever partial response it assembled. This is not an error — it means the task was too complex for the configured limit. For quota or upstream API errors, the tool call that failed is listed in tool_calls with status: "error" and an error_code. The agent continues with other tools.

​
Best practices

  • Start with focused questions — narrow scope = fewer tool calls = faster responses
  • Use sessions for workflows — chain analysis → write → send in one session rather than three separate calls
  • Pin agent types — use gtm_analyst for data questions, outreach_writer for content; don’t route everything through the orchestrator
  • Set explicit max_iterations — for quick lookups, max_iterations: 3; for deep analysis, let it run to the config default