Back to browse
Mimikos – Zero-config mock server that infers API behavior from OpenAPI

Mimikos – Zero-config mock server that infers API behavior from OpenAPI

by codeguruking·Apr 17, 2026·2 points·0 comments

AI Analysis

●●SolidSolve My ProblemSlick

Zero-config OpenAPI mocking with behavioral inference, unlike Prism's manual setup.

Strengths
  • Heuristic classifier infers endpoint behavior from path and method.
  • Deterministic responses enable reliable snapshot testing in CI.
  • Uses existing spec examples instead of requiring separate mock definitions.
Weaknesses
  • Cannot simulate complex business logic like auth or conditional workflows.
  • Mock server category is crowded with established tools like WireMock.
Target Audience

Backend and frontend developers

Similar To

Prism · WireMock · MockServer

Post Description

I built a mock server that reads an OpenAPI spec and serves realistic, deterministic responses — no mock definitions, no config files.

``` mimikos start petstore.yaml ```

That's the entire setup. Mimikos parses your spec, classifies each endpoint (create, fetch, list, update, delete), and generates schema-valid responses with realistic data. Same request always returns the same response, so it's safe for snapshot tests and CI.

What's different from Prism, WireMock, etc.:

Most mock servers either (a) require you to hand-write every response, or (b) generate random data that changes on every request. When the spec changes, your mocks break — or worse, silently become wrong.

Mimikos sits in an unoccupied spot: zero config + high-quality responses. The key piece is behavioral inference — a three-layer heuristic classifier that determines what each endpoint does (not just what it returns) from the HTTP method, path structure, response schema, and operationId. It gets this right 96% of the time across a 344-endpoint corpus (Stripe, GitHub, Asana, Spotify specs).

Features:

1. Deterministic responses via request fingerprinting + per-field sub-seeding (adding a field to your schema doesn't change existing field values) 2. Stateful mode (`--mode stateful`) for full CRUD workflows — POST creates, GET retrieves, DELETE removes 3. 120+ semantic field mappings — `email` gets an email, `name` gets a name, `url` gets a URL 4. Spec-authored `example` values used directly when present 5. RFC 7807 error responses with field-level diagnostics for invalid requests 6. Single Go binary, no runtime dependencies, <50ms responses

Technical details:

The architecture separates startup from runtime: spec parsing, schema compilation, and behavior classification happen once at startup. At request time, it's routing + deterministic generation from a pre-computed seed. No AI in the request path — no LLM calls, no network dependencies.

I explored using LLMs for behavior classification twice (GPT-4.1, Claude) and they scored worse than the heuristic both times. The heuristic wins because it can exploit structural signals (path patterns, schema shapes) that LLMs tend to ignore in favor of semantic reasoning.

Written in Go, single binary. OpenAPI 3.0 and 3.1. Apache 2.0 licensed.

- Get started: https://mimikos.dev/getting-started/ - Repo: https://github.com/mimikos-io/mimikos

Similar Projects

Developer Tools●●Solid

Turn any OpenAPI spec into agent-callable skills

It extracts focused, executable operations from giant OpenAPI files (the GitHub REST YAML is shown) to shrink context and avoid sidecar adapter sprawl — a pragmatic answer to token bloat and brittle ad-hoc integrations. Useful and concrete: if it actually generates tidy, updateable skill units and runtime hooks it saves a lot of maintenance. That said, the idea competes with existing LangChain/openai-function patterns; the repo will need clear runtime, versioning, and update strategies to feel like more than a nicer converter.

Solve My ProblemNiche Gem
yz-yu
103mo ago