mockd Samples

March 17, 2026 · View on GitHub

Real-world examples of mockd's digital twin and API mocking capabilities.

Available Samples

Sample	Description	Stateful	Endpoints	SDK Tested
Stripe API	Full Stripe payment API digital twin	9 tables, 46 bindings, 8 custom ops	587	stripe-go 49/49
Twilio API	Twilio REST API v2010 digital twin	7 tables, 32 bindings	197	twilio-go 13/13
OpenAI API	OpenAI API with stateful models + assistants	3 tables, 11 bindings	237	openai Python SDK

Sample	Description	What it shows
MCP Workflow	Build a Todo API with AI tool calls	Create mocks via MCP — zero CLI commands
GitHub Actions	Contract testing in CI	`setup-mockd` action + `mockd verify`
Docker Compose	Mock dependent microservices	User + Payment service mocks for local dev

Every sample follows the same pattern:

cd third-party-apis/stripe-api
mockd start -c mockd.yaml --no-auth

Or with Docker:

docker compose up

The mock server runs on localhost:4280 by default.

The Stripe and Twilio samples are digital twins — stateful mocks that behave like the real API:

Tables define in-memory resource collections (customers, invoices, messages, etc.)
Extend bindings wire HTTP endpoints to CRUD operations on those tables
Custom operations handle domain logic (e.g., paying an invoice, sending a message)
Imports split large configs into composable files

This means POST /v1/customers actually creates a customer that GET /v1/customers/:id can retrieve — no scripting required.