HyperMap is a JSON format for REST APIs built around a single reserved key, #,
that carries hypermedia controls and executable scripts. Resources link to each
other, forming a minimalist, data-oriented DOM — a tree where values
change, events bubble up, and JavaScript or WebAssembly ships from the server and
runs on the client in OS-level process isolation.
Mech is the client that speaks it — available for browser environments or as a POSIX daemon. There's no separate spec to write and no client to generate — each resource describes itself, and Mech understands them all.
Built on REST
HyperMap is REST. Every resource has a URL, responds to standard HTTP methods,
and works with the infrastructure you already have — caching, CDNs,
proxies, auth. If you already serve a REST API, adopting HyperMap means adding
# keys to the JSON you already return. No wrapper service, no new protocol, no
second deployment.
Explore, then automate
Resources carry their own controls, links, and executable scripts. An agent can start at a URL and explore — following links, running scripts, progressively discovering what's available. Then it can write a lightweight integration for ongoing work. The same format that supports dynamic exploration also supports low-overhead automation.
Network APIs don't need bespoke clients. They need to describe themselves. That's what HyperMap does.