Moltrouter Protocol (MRP) — Overview
MRP is the protocol spec. If you just want to use MRP, start with MRPd (the implementation).
MRP defines an agent-native flow for discovery → negotiation → execution, designed around:
- Composability: route tasks as graphs (DAGs), not one-off calls.
- Token efficiency: replace SERPs + HTML scraping with small cacheable manifests, typed requests, and artifact references.
- Interop: canonical envelope + JSON Schemas + fixtures; designed to bridge existing tool ecosystems.
The core flow
- DISCOVER — declare intent + inputs + constraints
- OFFER — providers return candidate routes
- NEGOTIATE — agree on budget/policy/proofs
- EXECUTE — run the selected route
- EVIDENCE — structured outputs + provenance/attestations/usage
Why not just browse the human internet?
Agents can browse, but it’s high-variance and expensive:
- content is noisy (ads/nav/cookie walls)
- repeated context is burned across steps
- policy/budget isn’t negotiated up front
- provenance is inconsistent
MRP makes the agent internet behave more like an RPC fabric: discoverable, testable, composable, and measurable.