Qualify

Credit rate your machine from its revenue and activity history.

Qualify turns a machine’s on-chain history into a Machine Credit Rating (MCR): an AAA-to-NR letter rating that any protocol, agent, or frontend can query from any chain.

What ships

Component	Description
EventRegistry	On-chain store for revenue (type 0) and activity (type 1) events, with a cross-chain audit trail. On peaq for peaq-homed machines; a machine homed on Solana writes to the Solana EventRegistry program.
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

1. 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 keccak256 data hash, and writes the minimal on-chain record. For a machine homed on Solana, submitEvent / submit_event route to the Solana EventRegistry program and sign with the owner’s or controller’s Solana wallet (SDK JS, SDK Python).

   import "dotenv/config";
   import { 
     PeaqosClient, 
     EVENT_TYPE_REVENUE, 
     TRUST_SELF_REPORTED, 
     SUPPORTED_CHAIN_IDS 
   } from "@peaqos/peaq-os-sdk";
   
   const client = PeaqosClient.fromEnv();
   const machineId = <decimal machine id>n; // bigint
   const { txHash, dataHash } = await client.submitEvent({
     machineId,
     eventType: EVENT_TYPE_REVENUE,
     value: 500,                       // $5.00 in cents
     currency: "USD",
     timestamp: Math.floor(Date.now() / 1000) - 10, // Must be on or before block time
     rawData: new TextEncoder().encode(JSON.stringify({ session: "abc" })),
     trustLevel: TRUST_SELF_REPORTED,
     sourceChainId: SUPPORTED_CHAIN_IDS.peaq,
     sourceTxHash: null,
     metadata: new Uint8Array([]),
   });
   

   Full walkthrough: Submit events.

2. Events accumulate

   A freshly registered machine is Provisioned until it has enough history to score. Events feed the scoring pipeline, which combines bond status, the consistency, history and tenure of revenue and activity, trust level, and how recent the last event is.

3. Query the MCR

   Any consumer can fetch the current rating from the public API.

   curl https://mcr.peaq.xyz/mcr/did:peaq:<decimal machine id>
   

   The server covers machines homed on peaq and on Solana. There is no public MCR API for Tokenomics 1.0 machines.

   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 the machine’s home chain (peaq, or Solana for a machine homed there) with sourceChainId and sourceTxHash pointing to the origin transaction. Consumers can verify each event against its source chain.

See Events and Trust levels.

The MCR API stays canonical on peaq. Omni-chain satellite contracts (IdentityLite, DIDLite, StakingLite) mirror Tokenomics 1.0 identity and stake records only and carry no MCR mirror; Economics 2.0 machines are read from peaq or their home chain. See the Omni-chain concept and the roadmap.

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.