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

# Mock vs Proxy

> Each routing rule either returns a configured fixture or forwards the request to the collection target endpoint.

Every GoDizzy routing rule has an **action**: `mock` or `proxy`.

The important part: your caller keeps using the same GoDizzy URL either way.

## Mock

Mock rules return a configured response immediately.

You can configure:

* status code
* response headers
* response body
* latency range

Mock is best for:

* deterministic testing
* local development
* failure simulation
* CI and evals

## Proxy

Proxy rules forward the request to the collection target endpoint while preserving the request shape.

Proxy is best for:

* validating behavior against a live upstream
* shared or live traffic
* incremental rollouts where some routes stay mocked and others go live

## Optional response shaping

Proxy rules can also apply response shaping before the response goes back to the caller. That lets you override status, mutate headers, or patch JSON without changing the upstream.

## Switching modes

You can change a rule between mock and proxy in the dashboard. The change applies to the next matching request.

## Comparison

|                 | Mock                           | Proxy                              |
| --------------- | ------------------------------ | ---------------------------------- |
| Calls upstream  | No                             | Yes                                |
| Deterministic   | Yes                            | Depends on upstream                |
| Latency control | Yes                            | Real network latency               |
| Best for        | Testing and failure simulation | Live validation and production use |