> ## Documentation Index
> Fetch the complete documentation index at: https://docs.godizzy.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Quick Start

> Create a development environment, add a collection and routing rule, and send your first request through GoDizzy.

This guide walks through the shortest real setup path: create a private development environment, create a collection, add a mock rule, and hit the generated GoDizzy URL.

## Prerequisites

You need a GoDizzy account and access to the dashboard at [godizzy.dev](https://godizzy.dev).

<Steps>
  <Step title="Sign in">
    Go to [godizzy.dev](https://godizzy.dev) and complete sign-in.
  </Step>

  <Step title="Create a development environment">
    Open **Environments** and create a **Development** environment.
  </Step>

  <Step title="Create a route collection">
    Inside the development environment, click **Create route collection** and fill in:

    * **Name** — for example `My Agent Tools`
    * **Target endpoint** — the upstream base URL for proxy rules, such as `https://api.example.com`

    After creation, GoDizzy generates a collection URL in this form:

    ```text theme={null}
    https://<generated-subdomain>.godizzy.dev
    ```

    <Note>
      The subdomain is assigned by GoDizzy. You do not choose it in the current UI.
    </Note>
  </Step>

  <Step title="Add a routing rule">
    Open the collection and create a rule that matches `GET /api/search`:

    * **Method** — `GET`
    * **Path** — `/api/search`
    * **Action** — `Mock`
    * **Priority** — `10`
  </Step>

  <Step title="Configure the mock response">
    Set:

    * **Status code** — `200`
    * **Body**

    ```json theme={null}
    {
      "results": [
        { "id": "r1", "title": "Acme Corp", "score": 0.97 },
        { "id": "r2", "title": "Globex", "score": 0.84 }
      ],
      "total": 2
    }
    ```

    Optionally configure a latency range such as `50` to `200` ms.
  </Step>

  <Step title="Send a test request">
    Use your generated collection URL with the path your rule matches.

    <CodeGroup>
      ```bash curl theme={null}
      curl https://<generated-subdomain>.godizzy.dev/api/search
      ```

      ```javascript fetch theme={null}
      const response = await fetch('https://<generated-subdomain>.godizzy.dev/api/search');
      const data = await response.json();
      console.log(data);
      ```

      ```python httpx theme={null}
      import httpx

      response = httpx.get('https://<generated-subdomain>.godizzy.dev/api/search')
      print(response.json())
      ```
    </CodeGroup>
  </Step>
</Steps>

## What to do next

* Switch the rule from **Mock** to **Proxy** to forward the same request to your upstream.
* Add more specific rules above the default rule.
* Copy the collection into **production** when you want to share or go live.
* If you want to automate setup from an agent, use [MCP](/guides/mcp).

<CardGroup cols={2}>
  <Card title="How It Works" icon="diagram-project" href="/how-it-works">
    Learn request flow, path matching, priority, and the default rule.
  </Card>

  <Card title="Environments" icon="layer-group" href="/concepts/environments">
    Understand the difference between development and production.
  </Card>

  <Card title="Route Collections" icon="network-wired" href="/concepts/route-collections">
    See how generated subdomains, target endpoints, and collection copying work.
  </Card>

  <Card title="MCP" icon="terminal" href="/guides/mcp">
    Manage environments, collections, and rules over MCP.
  </Card>
</CardGroup>