Connecting assistants to your documentation
How to let your own agents and assistants answer from DocOpsly-maintained pages, with citations.
What agent-first consumption means
DocOpsly is built for an environment where agents read documentation to answer questions and generate content. Because pages are kept current and structured consistently, they are a dependable reference — and every answer produced through DocOpsly cites the specific pages it relied on.
Two ways to connect
- Published pages — your documentation site is crawlable and structured, so any assistant that reads the web can use it. Each page carries stable URLs and clear headings.
- Workspace access — assistants operated by your organisation can query the workspace directly and receive answers with page-level citations, including material not yet public.
Citations
Every answer includes references to the pages it drew on. Surface them to end users: a support assistant that says "see Billing → Refund windows" is more trusted, and easier to correct, than one that speaks without sources.
Closing the loop
Questions that assistants cannot answer well are themselves triggers. They are routed into the review queue as proposed additions, so gaps found by readers become documentation improvements within the same day.
Access control
Workspace access respects the same permissions as human readers. An assistant serving customers sees public pages only; an internal helpdesk assistant can see internal processes as well.
Good practice
- Keep one canonical page per topic; agents cite better when there is a single authoritative source.
- Use the workspace conventions for dates and currency so answers are unambiguous.
- Review the unanswered-questions report weekly during the first month.
Want help with this?
Our team sets up workspaces with every new customer. Ask us anything about this guide.
Contact us