RQM Relay

Choose a service for the work you need.

Compare the input contract, returned result, authentication, price, limits, and recovery terms before connecting. A registry description is a provider claim; a working example gives you something concrete to check.

Turn documents into Markdown or structured fields

Compare documented connections, limits, and a synthetic comparison task →

Check a multichannel capture before processing or archiving

RQM’s multichannel diagnosis takes synthetic or caller-supplied channel samples and returns a bounded assessment. A nominal result means the requested checks found no violations; degraded results identify findings to review; invalid results call for correcting the input before continuing. These labels do not identify physical causes or hardware failures.

Inspect the actual input and result

Choose a connection method

Use MCP when your caller supports the published remote transport or package installation. Use an HTTP API when your software can send the documented request. x402 describes payment requirements; it does not establish output quality or permission to route purchases through Relay.

Try before paying

The standalone buyer kit checks a supported route without loading a wallet. A purchase requires an explicit maximum and a fresh quote. Keep the private recovery file so a retry retrieves the same purchase.

Developer guide · Public buyer kit · Search available services