Skip to main content
GoDizzy is a programmable gateway between your agent and the APIs it calls. Each inbound request is mapped to a collection, evaluated against routing rules, and then either mocked or proxied.

​
Data model

Organization
  └── Environments (production | development)
        └── Route Collections
              └── Routing Rules

​
Environments

  • Production — shared across the organization for real or shared traffic
  • Development — private to the creator for experimentation and iteration

​
Route collections

A route collection contains:
  • a generated GoDizzy subdomain
  • a target endpoint used by proxy rules
  • an ordered set of routing rules
Your agent calls the collection URL, not the upstream directly. 
https://<generated-subdomain>.godizzy.dev

​
Routing rules

Each rule defines:
  • Method match — such as GET, POST, or *
  • Path match — exact path, parameterized path, or wildcard
  • Priority — higher numbers run first
  • Action — mock or proxy
Every collection also has a default rule. Unmatched requests fall through to that rule.

​
Request flow

1

Resolve the collection

GoDizzy identifies the collection from the request subdomain.
2

Sort rules by priority

Rules are evaluated from highest priority to lowest.
3

Find the first match

The first rule whose method and path match wins.
4

Execute the action

  • Mock returns the configured status, headers, body, and optional latency.
  • Proxy forwards the request to the collection target endpoint.
5

Return the response

The response goes back to the caller through the same GoDizzy URL.

​
Path matching

StyleExampleNotes
Exact/api/usersOnly matches that exact path
Parameter segment/api/users/:idMatches one path segment
Wildcard*Matches any path
Query parameters do not change path matching. Path matching is case-sensitive.

​
Mock vs proxy

Mock rules return a configured fixture. No upstream request is made.

​
What changes without client rewrites

  • switching a rule between mock and proxy
  • editing a mock response
  • changing rule priority
  • adding latency to a mock rule
  • updating proxy response shaping

​
Learn more

Environments

Production and development visibility, usage, and constraints.

Route Collections

Generated subdomains, target endpoints, and copying.

Routing Rules

Method/path matching, priority, and the default rule.

MCP

Programmatic access to environments, collections, and rules.