Ask questions about product documentation
A chat agent that answers questions from Dome Platform documentation.
Caller- chat
Agent- docs-answerer
Daily limit- docs-answerer
- $5.00
Gateway- docs
Pooldocs-pool
- documentation-model
Toolsdomedocs
Guard- keep-ssn-out-of-promptsrequest
What this template gives you
Interface
A chat window, in your browser
Use the included interface to send a request to this template.
Budget
$5.00 per day
docs-answerer is capped at $5.00 per day.
Gateway
docs gateway
This template sends its requests through docs gateway, where its access rules and limits apply.
Model
documentation-model
This template uses documentation-model through the docs-pool pool.
Content
keep-ssn-out-of-prompts inspects the documentation-model request
Redact US SSNs before a prompt reaches the model provider.
Usage
Hand this template to an AI agent to set up this template
Node.js and npm to run npx.
Dome CLI, installed with brew install dome-systems/tap/dome, then signed in with dome auth login.
Docker Compose to run the companion app locally.
- 1
Create a sandbox workspace
dome sandbox provision --scope workspaceUse a sandbox while trying a template. Provisioning does not switch your active context.
- 2
Switch to the sandbox workspace
dome context sync dome context list dome context use sandbox-<sandbox-name>Replace <sandbox-name> with the sandbox name returned when provisioning it.
- 3
Pull the template
npx @domesystems/templates pull dome-systems/ai-agent-for-documentation@0.1.4 --dir ai-agent-for-documentationDownloads this immutable release and verifies its digest.
- 4
Run the template
npx @domesystems/templates up --dir ai-agent-for-documentationImports it into Dome and starts the companion app.
Dome import variables
npx @domesystems/templates up imports the template into Dome and prompts for required values. For unattended runs, set them as DOME_IMPORT_VAR_… environment variables.
Required values
DOME_IMPORT_VAR_anthropic_api_key
Runtime environment
These variables are required to run the agent. During pull, .env.example is copied to .env when available. If they’re missing, npx @domesystems/templates up retrieves them from Dome and saves them in .env. Pass --provision to refresh them.
# The container holds exactly one secret.
#
# Tool credentials went into Dome when dome import ran and live behind the gateway.
# The provider key lives with the Broker. Neither is here, and neither should be.
# Revealed once after import: dome import outputs <job-id>
DOME_TOKEN=
# The gateway ROOT — not a bare host, and not the /mcp path.
# Copy the "Gateway URL" from the command above. The container derives
# /mcp for tools and /v1/messages for models from it.
DOME_GATEWAY_URL=Agent instructions
You answer questions about the Dome Platform from its documentation.
Work like this:
1. If the question is broad — "what is Dome", "how does authorization work" —
start from the documentation index to see what exists.
2. Search the documentation for the terms in the question. Search results carry
the path of every page they match.
3. Read pages rather than searching repeatedly. Two or three searches is
plenty; after that, open the most promising pages in full **using the paths
the search results gave you**. Do not invent a path and try it.
4. Answer from what you read, and name the pages you used.
If the documentation does not contain the answer, say so plainly. Do not fill
the gap from general knowledge — a confident answer that is not in the
documentation is worse than no answer, because the reader cannot tell the
difference.
Use whatever tools you have been given, and do not decline a request on the
assumption that you lack permission. If a call comes back refused, say what came
back and carry on with the tools that do work.