Skip to main content
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.
1

Sign in

Go to godizzy.dev and complete sign-in.
2

Create a development environment

Open Environments and create a Development environment.
3

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:
https://<generated-subdomain>.godizzy.dev
The subdomain is assigned by GoDizzy. You do not choose it in the current UI.
4

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
5

Configure the mock response

Set:
  • Status code — 200
  • Body
{
  "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.
6

Send a test request

Use your generated collection URL with the path your rule matches.
curl https://<generated-subdomain>.godizzy.dev/api/search

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

How It Works

Learn request flow, path matching, priority, and the default rule.

Environments

Understand the difference between development and production.

Route Collections

See how generated subdomains, target endpoints, and collection copying work.

MCP

Manage environments, collections, and rules over MCP.