Qualify turns a machine’s on-chain history into a Machine Credit Rating (MCR): a Moody’s-style letter rating that any protocol, agent, or frontend can query from any chain.Documentation Index
Fetch the complete documentation index at: https://docs.peaq.xyz/llms.txt
Use this file to discover all available pages before exploring further.
What ships
| Component | Description |
|---|---|
| EventRegistry | On-chain store for revenue (type 0) and activity (type 1) events, with a cross-chain audit trail. |
| MCR scoring pipeline | Computes AAA-to-NR ratings from a bonded machine’s event history. |
| MCR API | Public read API. Any chain, any caller, no auth. |
| SDK helpers | submitEvent, validateSubmitEventParams, computeDataHash, queryMcr on both JS and Python. |
How it works
Submit events
Each time a machine earns revenue or performs a trackable activity, the operator submits an event to the EventRegistry. The SDK validates the payload, computes a Full walkthrough: Submit events.
keccak256 data hash, and writes the minimal on-chain record.Events accumulate
A freshly registered machine is Provisioned until it has enough history to score. Events feed the scoring pipeline, which blends revenue trend, activity cadence, bond status, and trust level.
Query the MCR
Any consumer (an agent, protocol, frontend, or another chain) can fetch the current rating from the public API.Response includes the rating (AAA / AA / A / BBB / BB / B / NR / Provisioned), score, event counts, revenue trend, and bond status. Full walkthrough: Query MCR.
Cross-chain revenue
Revenue earned on another chain (e.g., Base) is recorded on peaq withsourceChainId and sourceTxHash pointing to the origin transaction. Consumers can verify each event against its source chain.
See Events and Trust levels.
Concepts
Machine Credit Rating
AAA-to-NR scale, lifecycle from Provisioned to rated.
Events
Revenue and activity records that feed MCR.
Trust levels
Self-reported, on-chain verifiable, hardware-signed.
SDK reference
submitEvent: Write a single event to EventRegistry.validateSubmitEventParams: Validate event params client-side.computeDataHash: keccak256 of raw event data.queryMcr: Fetch a machine’s rating from the MCR API.
API reference
GET /mcr/{did}
Rating, score, trend, bond status for a single machine.
GET /operator/{did}/machines
Paginated operator fleet with per-machine MCR.
Guides
Submit events
Event types, validation, data hashing, cross-chain pattern.
Query MCR
Fetch ratings from curl, JS, or Python.

