The product knowledge layer
For the teams accountable for product knowledge
DevDocs.ai is for the teams blamed when product knowledge is wrong: support and success, product and docs, engineering, and AI platform owners. DevDocs.work did this the hard way first: reading code, tracing tickets, interviewing experts, and reconciling docs against real product behavior. DevDocs.ai turns that field-tested operating model into a maintained system.
New ticket
Describe your issueHello Joyce!
The cancellation policy for a booked class may vary depending on the studio you are booking with. Generally, we allow you to cancel a class reservation without any penalty up to a certain time before the class starts. However, if you cancel within 24 hours of the class start time, you may be subject to a late cancellation fee. This fee is typically deducted from your credits or charged to your payment method on file.
Did this not solve your issue?
Support and success leaders
Give reps answers grounded in current policy, product behavior, account context, and ticket history without asking them to search five systems first.
Product and docs leaders
Turn specs, release notes, code, support learnings, and expert review into docs sites and portals that stay aligned after launch.
Processed message: We are experiencing 404 errors on the cron endpoint since this morning. Upon reviewing the logs, it appears that this error is not properly detected.
Original message: Help! Cron is alwys retunning 404s now its happening all the time since this morning!!! Ntohing to see in the logs!
Engineering and AI platform teams
Give internal agents and AI features current product context, approved tools, and permission-scoped source material instead of stale snapshots.
May 14, 3:42 PM
Hi Tyler!
Yes, the cancellation policy for a booked class may vary depending on the studio you are booking with. Generally, we allow you to cancel a class reservation without any penalty up to 12 hours before the class starts. However, if you cancel later than that, you will be subject to a late cancellation fee. This fee is deducted from your credits.
Best,
Joshua
Support automation owners
Generate drafts, summaries, routing, and escalations from the same maintained knowledge layer your docs sites and portals use.
Connect the systems where knowledge is born
Product knowledge is not in one wiki. It is split across code, tickets, docs, Slack decisions, CRM fields, meetings, websites, and APIs. DevDocs.ai continuously ingests those sources and normalizes them into a permission-scoped knowledge graph.
GitHub Repo
GitLab
Notion
Fireflies
Salesforce Knowledge
Jira
Website
GitHub Discussions
Zendesk
Salesforce Case
HubSpot
GitBook
Front
GitHub Issues
Confluence
DevDocs.ai supports encryption at rest, and is actively pursuing SOC 2 Type II compliance.
Publish the knowledge where people work
One maintained graph can power a customer docs site, an employee portal, a support workflow, and an AI agent. Each audience gets the right surface without creating another stale copy.
Customer and developer docs sites
Turn connected source material into searchable docs sites with scoped content, consistent design, and freshness checks built in.
Customer and employee portals
Give people a signed-in place to search docs, see account-aware context, request help, and take approved actions.
Gaps and conflicts surfaced
Use search, portal, and workflow analytics to find missing, stale, or conflicting knowledge before people and agents act on it.
For engineering teams shipping AI features
Expose the same knowledge graph through REST APIs, SDKs, and an MCP gateway so agents can read current product context and call approved tools. Your team controls auth, permissions, source systems, and where answers appear.
curl https://api.devdocs.ai/v1/train -X POST \-H "Authorization: Bearer <TOKEN>" \-F 'file=@./post.md'
curl https://api.devdocs.ai/v1/chat -X POST \-H "Authorization: Bearer <TOKEN>" \-d '{"messages": [{ "role": "user", "content": "How do I claim my credits?" }],"model": "gpt-4-32k"}'
curl -X GET "https://api.devdocs.ai/v1/insights/queries" \-H "Authorization: Bearer <TOKEN>" \-d '{ "from": "2023-09-01T22:00:00" }'
1import { DevDocsAI } from '@devdocsai/react';2import { syncSource } from '@devdocsai/core';34export default function CustomerPortal(): ReactElement {5 return <DevDocsAI6 projectKey={process.env.NEXT_PUBLIC_PROJECT_KEY}7 portal={{8 surface: 'customer-docs',9 sources: ['docs', 'policies', 'account-data'],10 requireAuth: true,11 }}12 />13}
See where your product knowledge breaks
We will trace one product area across code, tickets, docs, Slack, and support workflows; show where facts conflict or go stale; and map the docs, portals, answers, and agent context DevDocs.ai should maintain.