# GoDizzy

## Docs

- [Manage Subscription](https://docs.godizzy.dev/billing/manage-subscription.md): Use the billing page for plan status, self-serve Pro checkout, and the customer portal for subscription management.
- [Plans](https://docs.godizzy.dev/billing/plans.md): Current GoDizzy billing centers on Free, self-serve Pro monthly, and Enterprise.
- [Environments](https://docs.godizzy.dev/concepts/environments.md): GoDizzy's self-serve workflow uses shared production and private development environments to isolate routing configs.
- [Mock vs Proxy](https://docs.godizzy.dev/concepts/mock-vs-proxy.md): Each routing rule either returns a configured fixture or forwards the request to the collection target endpoint.
- [Route Collections](https://docs.godizzy.dev/concepts/route-collections.md): A route collection is a gateway with a generated subdomain, a target endpoint, and the routing rules that control request behavior.
- [Routing Rules](https://docs.godizzy.dev/concepts/routing-rules.md): Routing rules determine how GoDizzy handles each incoming request — by matching on HTTP method and path, then either mocking or proxying.
- [Environments Workflow](https://docs.godizzy.dev/guides/environments-workflow.md): The recommended GoDizzy workflow is to build in development, then copy into shared production when ready.
- [Latency Injection](https://docs.godizzy.dev/guides/latency-injection.md): Add a randomized delay to any mock rule to test retry logic, timeout handling, and how your agent degrades under slow tool calls.
- [MCP](https://docs.godizzy.dev/guides/mcp.md): Connect an MCP client to GoDizzy to manage environments, collections, and routing rules.
- [Mock Responses](https://docs.godizzy.dev/guides/mock-responses.md): Configure deterministic mock responses for your routing rules, use templates to echo request data, and roll back to any prior version.
- [Mock Webhooks](https://docs.godizzy.dev/guides/mock-webhooks.md): Configure outbound HTTP callbacks that GoDizzy fires after serving a mock response, so your agent or downstream system receives realistic webhook events.
- [Proxy Response Shaping](https://docs.godizzy.dev/guides/proxy-shaping.md): Mutate the upstream response — status code, headers, or body — before GoDizzy returns it to your agent, without changing agent code.
- [Team Collaboration](https://docs.godizzy.dev/guides/team-collaboration.md): Invite teammates to your organization and collaborate around shared production configs while keeping development environments private.
- [How It Works](https://docs.godizzy.dev/how-it-works.md): Understand GoDizzy's routing model: environments, route collections, routing rules, and request flow.
- [Introduction](https://docs.godizzy.dev/introduction.md): GoDizzy is a programmable API gateway for mocking, proxying, and stress-testing agent tool calls without changing client code.
- [Quick Start](https://docs.godizzy.dev/quickstart.md): Create a development environment, add a collection and routing rule, and send your first request through GoDizzy.
- [Latency & Timeouts](https://docs.godizzy.dev/scenarios/latency-timeouts.md): Inject high latency or return timeout errors to verify your agent degrades gracefully when a tool is slow or unresponsive.
- [Rate Limits](https://docs.godizzy.dev/scenarios/rate-limits.md): Simulate 429 Too Many Requests responses to validate your agent's backoff strategy and error handling before hitting real API limits.
- [Schema Drift](https://docs.godizzy.dev/scenarios/schema-drift.md): Mock a changed or missing field in an API response to catch integration breakage before schema changes reach production.
- [Tool Failures](https://docs.godizzy.dev/scenarios/tool-failures.md): Simulate partial results and upstream errors to test how your agent handles incomplete or failed tool responses.