How do I mock the gRPC echo demo API locally?

Install stunt, add a one-service block to stunt.yaml (adapter: embedded:echo-style), and run stunt up. You get a local, stateful stand-in for gRPC echo demo 1.0 — 0 routes over grpc/websocket — with no remote account, no network, and no bills.

Is the gRPC echo demo mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of gRPC echo demo (routes, status codes, pagination, webhooks), never real records.

← all adapters

echo-style

simulates gRPC echo demo 1.0

grpcwebsocketadapter v0.1.00 routes

verification

bootboot tier — no SDK suite yet· surface 1

use it

# add to stunt.yaml
services:
  echo:
    adapter: embedded:echo-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the gRPC echo demo API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of gRPC echo demo. It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real gRPC echo demo 1.0 surface — the data is fake, the behavior is real.

backing stores

echoes

api surface (1)

generated from the adapter manifest — exactly what boots, nothing more

0 routes · +1 ws · grpc stunt.example.Echo

WS/ws/echo

full scorecard →

want more of the gRPC echo demo surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.