Skip to main content
By the end of this guide you’ll have a live gateway URL that returns a mock JSON response. You’ll send a real HTTP request to it and see GoDizzy in action.

​
Prerequisites

You need a GoDizzy account. Sign in at godizzy.dev using your work email — authentication is handled through the dashboard.

​
Steps

1

Sign in to the dashboard

Go to godizzy.dev and click Sign in. Complete the authentication flow. You’ll land in the GoDizzy dashboard.
2

Create an environment

From the dashboard, navigate to Environments and click Create environment.Choose Development as the environment type. Development environments are personal — only you can see them, which makes them ideal for initial setup and experimentation.
Your organization can have one production environment, one staging environment, and one development environment per user. You can create all three independently.
3

Create a route collection

Inside your new development environment, click Create route collection.Fill in:
  • Name — something descriptive, like My Agent Tools
  • Target endpoint — the base URL of your real backend (for example, https://api.example.com). This is where proxy rules will forward requests.
Click Create. GoDizzy assigns your collection a stable subdomain URL in the format:
https://<subdomain>.godizzy.dev
Copy this URL — you’ll use it in the final step.
This URL never changes. Whether a rule is set to mock or proxy, your agent always calls the same address. You change behavior in the dashboard, not in your agent.
4

Add a routing rule

Inside your collection, click Add routing rule.Configure the rule to match a specific endpoint your agent calls. For this example, match GET /api/search:
  • Method — GET
  • Path — /api/search
  • Action — Mock
  • Priority — 10 (higher numbers run first)
Click Save.
5

Configure the mock response

After saving the rule, click into it to configure the mock response.Set:
  • Status code — 200
  • Body — paste in a JSON fixture that matches what your real API returns, for example:
{
  "results": [
    { "id": "r1", "title": "Acme Corp", "score": 0.97 },
    { "id": "r2", "title": "Globex", "score": 0.84 }
  ],
  "total": 2
}
Optionally, add a latency range — for example, min 50ms and max 200ms — to simulate a realistic response time.Click Save. The rule is now set to mock mode and active.
6

Send a test request

Use the gateway URL you copied in step 3. Send a request to the path your rule matches:
curl https://<subdomain>.godizzy.dev/api/search
GoDizzy matches the GET /api/search rule and returns your mock fixture:
{
  "results": [
    { "id": "r1", "title": "Acme Corp", "score": 0.97 },
    { "id": "r2", "title": "Globex", "score": 0.84 }
  ],
  "total": 2
}
If you set a latency range, the response is delayed by a random amount within that range.

​
What’s next

You now have a working gateway. Here are a few things to try:
  • Switch to proxy — Edit the rule and change its action from Mock to Proxy. The same request will now be forwarded to your real backend at the target endpoint you configured. Your agent code doesn’t change.
  • Add a fallback rule — Every collection has a default rule that catches any request that doesn’t match a specific rule. You can configure it to proxy to your backend so unmatched paths always reach the real API.
  • Copy to staging — Once your rules are working, copy the collection to your staging or production environment to share the configuration with your team.

How It Works

Understand rule evaluation, priority, and the routing model.

Mock Responses

Versioning, templates, rollback, and latency configuration.

Environments

Isolate configurations across production, staging, and dev.

Agent Scenarios

Ready-made patterns for testing tool failures and rate limits.