· case viii / viii — interoperability in build · mmxxvi

treefrog.tech

An interoperable WebMCP town.

year
MMXXVI
role
Design & build
surface
WebMCP · town
status
In build
population
Three providers
source

The brief

Town Hall publishes a machine-readable provider registry and builds itineraries a general-purpose consumer can follow across independent surfaces.

Say it once, the town does the rest: one request, and the agent chains the whole errand across independent providers, then verifies the journey against the itinerary.

Notes from the build

decisions that held
a registry, not a router

Town Hall publishes where capabilities live and leaves the sequencing to the consumer. The town describes itself; it does not drive the errand.

independent surfaces

Each provider is built and deployed on its own. The town is the agreement between them, not a framework they all sit inside.

the itinerary is checkable

A journey is verified against the itinerary it was built from, so completion is something you can inspect rather than assume.

watch it work
A WebMCP town, run by voice

Three independent WebMCP providers, one consumer, chained across the town — the whole errand driven by voice.

see the demo →
← back to ziola next sirocco.gallery →