Api getting started

[sherry-factory]

PR for creating a landing page that actually explains how to set up an API Key before being launched straight into the APIs. Details in commits as to changes, testing, etc.

docs(api-reference): add Getting Started landing page for Public API
Summary:
Adds a Getting Started landing page at /api-reference/getting-started
that introduces authentication, API key generation, permissions, and the
available endpoint groups before users land on the auto-generated OpenAPI
endpoint reference. Uses the auto-discovery openapi wrapper so new
endpoints flow into the sidebar without docs.json edits.

Changes:

• docs/api-reference/getting-started.mdx (new)
  Frontmatter + lead paragraph, Authentication section with bearer header
  example, Generate an API key 3-step list, screenshot of the API keys
  settings page, Permissions subsection, Available Endpoints table, and a
  Next Steps CardGroup matching the format used on
  /guides/power-user/setup-checklist.
• docs/docs.json
  Restructured the API Reference tab to mix the manual landing page with
  the auto-discovered OpenAPI endpoints under a single Endpoints wrapper
  group: { tab, pages: [getting-started, { group: Endpoints, openapi }] }.
• docs/style.css
  Added .url-plain class override (dark + light mode) to allow inline
  prose URLs to inherit surrounding text color instead of the brand
  orange link styling.
• docs/images/web/api-keys-page.png (new)
  Screenshot of the Factory App API Keys settings page used in the
  Generate an API key subsection.

Notes:

• Auto-discovery wrapper preserved so the existing openapi-validate CI
  workflow in factory-mono and any downstream automation continue to work
  unchanged when new endpoints are added to the spec.
• Tag subgroups (Computers, Sessions, Organization) collapse by default;
  this is a Mintlify limitation when using the auto-discovery openapi
  directive (expanded: true does not cascade to virtual tag subgroups).
• The two URLs in the Generate an API key numbered list use raw
  tags with className="url-plain" so they remain clickable but render
  in the standard prose text color.
• JP API Reference tab not mirrored in this commit; can follow up if
  needed.

Testing:

• Verified locally with mintlify dev (CLI 4.2.573) on http://localhost:3001:
  • /api-reference/getting-started returns HTTP 200 and renders the new
    page with all sections in order: Authentication > Available
    Endpoints > Next Steps.
  • /api-reference/computers/list-computers, sessions/create-a-session,
    and organization/list-organization-users all return HTTP 200 and
    appear in the sidebar under Endpoints with the correct tag
    subgroups.
  • The api-keys-page.png screenshot serves at HTTP 200 and is visible
    inline in the Generate an API key subsection.
  • The .url-plain rule resolves to inherited text color in dark mode,
    overriding the existing .dark .prose li a:not(.card a) orange rule.
  • The Next Steps CardGroup renders as a 2-column grid with four
    cards matching the visual style of the setup-checklist page.

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>

[factory-droid]

Droid finished @sherry-factory's task —— View job

---

Adds an API Getting Started landing page and wires it into Mintlify navigation for EN/JP. Only issue spotted is a misleading duplicate link in the “All Endpoints” card; otherwise the changes look good.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
factory	🟢 Ready	View Preview	May 21, 2026, 5:31 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.