Skip to main content
Every routing rule in GoDizzy has an action: either mock or proxy. This is what determines whether a matched request gets an immediate fixture response or is forwarded to the real upstream API. The key insight: your agent’s URL never changes. Whether a rule is mocking or proxying, requests go to the same <subdomain>.godizzy.dev address. You switch behavior in the dashboard — no code changes in your agent.

​
How each action works

When a rule’s action is mock, GoDizzy returns a configured fixture response immediately — no request is made to your target endpoint.You configure the fixture with:
  • Status code — e.g. 200, 429, 500
  • Response headers — any custom headers to include
  • Body — a JSON fixture, error payload, or any response body you want
  • Latency range — a min and max delay in milliseconds; GoDizzy picks a random value in the range on each request
Example: simulating a rate-limited payments APIYour agent calls POST https://payments-sandbox.godizzy.dev/v1/charges. The matching rule is set to mock with this configuration:
{
  "status": 429,
  "headers": {
    "Retry-After": "30",
    "Content-Type": "application/json"
  },
  "body": {
    "error": {
      "type": "rate_limit_error",
      "message": "Too many requests. Please retry after 30 seconds."
    }
  },
  "latencyMin": 200,
  "latencyMax": 800
}
Your agent receives a 429 with a realistic delay — no real API call made, no rate limit consumed.When to use mock:
  • Development: build and test your agent against deterministic fixtures
  • Simulating failures: 429s, 500s, timeouts, schema drift, partial results
  • Evaluations: same fixture every run, reproducible in CI
  • Demos: no risk of hitting live APIs or exposing real data

​
Switching between mock and proxy

The toggle in the dashboard switches a rule’s action between mock and proxy. The change takes effect immediately — the next request that matches the rule will use the new action.
1

Open the rule

Navigate to the routing rule you want to change.
2

Toggle the action

Click the mock/proxy toggle. The rule switches from mock to proxy (or vice versa) instantly.
3

Verify

The next request matching that rule uses the new action. No restarts or deployments needed.
Your agent keeps calling the same URL throughout. Only GoDizzy’s behavior changes.

​
Side-by-side comparison

MockProxy
Makes upstream requestNoYes
Response sourceYour configured fixtureThe real target endpoint
Latency controlYes — configurable min/max rangeNo (real network latency applies)
Response shapingFully configured in dashboardOptional — pass-through or reshape
Best forDev, testing, failure simulationStaging, production, live traffic
DeterministicYes — same fixture every timeNo — upstream can change
A common workflow: start with all rules set to mock during development so you can build and test your agent against deterministic fixtures. When you’re ready to validate against the real API, flip individual rules to proxy one at a time — still using the same URL.