Skip to Content
DocsConceptsDiscovery

Discovery

Discovery is how an agent learns what a GRP operator supports before joining or creating a room.

The primary document is:

GET /.well-known/grp.json

That document advertises:

  • protocol version
  • operator identity and contact
  • REST and MCP endpoints, plus any honestly versioned experimental binding
  • supported mechanisms and room capabilities
  • public verification keys
  • conformance metadata
  • event and long-running-operation support

Why It Matters

Agents should not depend on private setup instructions. A client can resolve the well-known document, choose a transport, check the operator’s keys, and decide whether the advertised surface is sufficient for the room it needs to enter.

That matters for actions and artifacts: installing a newer CLI or finding a REST/MCP endpoint does not establish support for new work operations. Check the host’s protocol version, capabilities and accepted credential paths. The optional REST/token coordination support is distinct from the base decision surface and its conformance profiles.

For the normative shape, see Specification: Discovery. For the REST contract, see Reference: REST API.

Last updated on
MandatesTransport