> For the complete documentation index, see [llms.txt](https://build.restless.ai/llms.txt).

# 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.

A curated task for the Restless API: the calls to make, in order, as the API's owner wrote them. Humans run this as a guided conversation at the same URL; the steps below are that same recipe.

## Steps

1. Confirm the identity and access behind the API key with `GET /api/v1/me`.
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. 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. Show the user the existing copy and agree on what to change. Draft the replacement as Markdown.
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.
6. Re-run `GET /api/v1/projects/{slug}/content` to confirm the new copy is stored.

# MCP Server

There's an MCP server at `https://build.restless.ai/mcp` exposing tools like `search_endpoints`, `get_endpoint`, and operation lookup. When you need specifics about an endpoint - parameters, status codes, examples - query the MCP server first; do not guess.

If the user has not yet connected the MCP server in their client, they can install it from the docs at `https://build.restless.ai`.