For AI agents: a machine-readable documentation index for this API is available at /llms.txt. Every page is also available as Markdown — append ".md" to the URL or send an "Accept: text/markdown" request header.

Update the getting started page

Review and update the project's getting started documentation page.

The Getting Started page is the first thing a developer reads, and it goes stale faster than the rest of the docs because it describes the setup path rather than the API surface.

This reads the page as it stands today, agrees the changes with you, and writes the revision back. Edits are field by field, so revising the setup copy leaves the authentication section untouched.

Steps

Restless runs these six in order with your stored key, and stops for your approval before the one that changes data.
  1. 1

    Confirm the identity and access behind the API key with GET /api/v1/me.

  2. 2

    Pick the target project. If you only have an example slug, verify it with GET /api/v1/projects/{slug}, or browse options via GET /api/v1/projects.

  3. 3

    Read the current docs content with GET /api/v1/projects/{slug}/content. The Getting Started page is the installation field; authentication holds the auth section shown alongside it.

  4. 4

    Show the user the existing copy and agree on what to change. Draft the replacement as Markdown.

  5. 5

    Apply the change with PATCH /api/v1/projects/{slug}/content, sending only the fields you are changing (for example {"installation": "..."}). Anything you omit is left alone.

    changes data
  6. 6

    Re-run GET /api/v1/projects/{slug}/content to confirm the new copy is stored.