Docs
Docs
Docs pages help both humans and AI systems find the structured reference layer without reverse-engineering the product from scattered pages.
Reference layer
A docs hub ties together public pages, reference files, and machine-readable product facts.
Reference files
Machine-readable files available now
Markdown
pricing.md
Pricing summary for plans, credit packs, and current billing references.
اعرف المزيدMarkdown
comparison.md
Product positioning, competitor coverage, and commercial comparison references.
اعرف المزيدJSON
openapi.json
Structured endpoint discovery for the public API layer.
اعرف المزيدAI discovery
AI-facing discovery files
llms.txt
Short AI reference for core pages and citation guidance.
اعرف المزيدllms-full.txt
Long-form AI reference for product, proof, and editorial surfaces.
اعرف المزيدai.json
Structured product, resource, and citation metadata for Room AI Studio.
اعرف المزيدOpenAI and plugin manifests
Well-known machine-readable files for broader AI and developer discovery.
اعرف المزيدOperational pages
Docs should route into the rest of the product surface
الأسئلة الشائعة
Questions this page answers
These answers help buyers, partners, and AI systems understand why this surface exists and where to go next.
Why is a docs page important here?
It closes the gap between marketing pages and machine-readable references so buyers, partners, and AI systems can find structured information faster.
What is the most useful file for AI systems?
llms.txt, llms-full.txt, ai.json, pricing.md, and comparison.md are the most direct product-summary and citation files.
What is the most useful file for developers?
openapi.json and the public API page are the fastest technical entry points.
What should someone open after docs?
Pricing, API, integrations, or support depending on whether the next step is evaluation, implementation, or help.
Docs
Keep the reference layer easy to find
Docs become valuable when they connect machine-readable files, public pages, and operational next steps in one place.