What Mimikos Doesn't Do
Mimikos is a mock server for your API contract. These are its current boundaries — they reflect where we focus today, guided by the principle that the spec defines the contract, not the behavior.
Authentication and authorization
Section titled “Authentication and authorization”Mimikos does not validate tokens, API keys, or session cookies. Every request is accepted regardless of auth headers.
Today’s focus: Mimikos mocks the API contract — schemas, status codes, response shapes — not the application layer. Auth logic lives in your real service or a dedicated auth mock.
Business logic
Section titled “Business logic”Mimikos does not simulate conditional behavior based on request content. A POST with {"role": "admin"} and a POST with {"role": "user"} produce the same response shape.
Today’s focus: The OpenAPI spec describes the contract — what fields exist and their types — not runtime decisions. Mimikos generates responses that satisfy the schema, not responses that simulate application behavior.
Rate limiting
Section titled “Rate limiting”No request throttling, rate limit headers, or 429 responses (unless you request one explicitly via X-Mimikos-Status: 429 and the spec defines it).
Today’s focus: Rate limiting is an infrastructure concern, outside the scope of API contract mocking. If you need it for testing, mock it at the proxy layer.
Webhooks and callbacks
Section titled “Webhooks and callbacks”Mimikos does not send outbound HTTP requests. It serves responses to incoming requests only.
Today’s focus: Webhook delivery requires event triggers, retry logic, and delivery state — concerns that go beyond mocking a request-response contract.
Multi-format responses
Section titled “Multi-format responses”Mimikos currently serves JSON (application/json and +json variants). It does not yet generate XML, form-data, or other content types.
Today’s focus: JSON is the dominant API format and where Mimikos delivers the most value today. The spec may define other media types, but Mimikos does not generate them yet.
Persistent state
Section titled “Persistent state”In stateful mode, all resources are stored in memory. Restarting the server clears everything.
Today’s focus: In-memory state keeps Mimikos simple and reproducible — no storage layer, no migrations, no corruption risk. Each server start is a clean slate, which aligns with repeatable testing.
The principle
Section titled “The principle”Every boundary above follows the same rule: the spec defines the contract, not the behavior. Mimikos mocks what the spec describes.
These boundaries reflect our current focus, not permanent limitations. If your use case pushes against one of them, open an issue — we’d like to hear about it.