Quickstart (Provider)

This is the protocol-level checklist for implementing an MRP provider. If you only need a local demo server, MRPd can run one for you.

To become MRP-compatible, a service should expose:

• GET /.well-known/mrp.json
• GET /mrp/manifest
• POST /mrp/hello
• POST /mrp/discover
• POST /mrp/negotiate (optional initially)
• POST /mrp/execute

1) Well-known discovery

Return your capabilities and where your manifest is:

{
  "mrp_version": "0.1",
  "capabilities": ["summarize_url"],
  "manifest_url": "/mrp/manifest"
}

2) Manifest

Publish a machine-usable manifest:

• inputs/outputs
• policy/proofs
• endpoints

See: Schemas

3) DISCOVER → OFFER

• Validate the envelope.
• Return one or more offers with route_id.

4) EXECUTE → EVIDENCE

• Execute must return an EVIDENCE envelope.
• Include provenance/citations and usage if possible.

Tip: ship artifacts

Avoid stuffing large blobs into JSON. Return an artifact reference (hash+URI) for big inputs/outputs.

See: Artifacts