The scoring logic is deliberately opaque. Authmatech does not publish the exact signals, thresholds, weights, or score bands behind these products — doing so would help bad actors stay under the line. Integrate against the outputs documented below (
trustScore, decision, anomalies, reasonCodes, etc.); treat the internals as a black box that can change.Shared signals
All three accept the same building blocks in the request body, so you collect them once and reuse them:device(DeviceSignal) — platform, OS version, model, app/SDK version, and integrity flags such asisRooted,isEmulator,vpnDetected,proxyDetected, andappIntegrityStatus.network(NetworkSignal) —ipAddress,countryCode,operator, andconnectionType.mobileNumber,sessionId, and an optionalsdkSessionIdthat links back to a verified SDK session.metadataId— your own correlation id, echoed back on the response so you can join results to your records.
Authmatech Trust
Trust distils an identity’s track record with your account into a single, identity-grade number, so you can drop confidence into decisions. It reflects history and behaviour over time — not a snapshot of the current device or network.trustScore— 0–100; higher means more trustworthy.confidence—HIGH,MEDIUM, orLOW, based on how much history the score draws on.recommendation— a suggested action:ALLOW,REVIEW, orBLOCK.positiveFactors/riskFactors— human-readable labels for what helped or hurt; the exact set is illustrative and may change.breakdown— a high-level view of the factors behind the number.
LOW confidence. See POST /v1/api/trust/score.
Authmatech Shield
Shield is decision-first. It evaluates the session and returns the action to take, with reason codes you can log and act on.decision—ALLOW,CHALLENGE,REVIEW, orBLOCK.riskScore/riskLevel— 0–100 andLOW/MEDIUM/HIGH/CRITICAL(higher is riskier — the inverse of Trust).sdkVerified— whether the referencedsdkSessionIdwas found and validated.deviceConsistencyLevel/operatorConsistencyLevel— how the live session compares to the verified session.
POST /v1/api/shield/assess.
Authmatech Detect
Detect looks across time and across your base. It builds a behavior timeline and surfaces anomalies rather than scoring a single action.anomalies— typed findings, each with acode,severity(MEDIUM/HIGH), description, and affected count. Categories include retry bursts, multi-account-per-device or per-installation usage, IP concentration, and operator/country failure spikes.recommendedAction—ALLOW,CHALLENGE,REVIEW, orBLOCK.anomalyScore— scales with the number of anomalies detected (capped at 100).
POST /v1/api/detect/analyze.
Choosing between them
- Want one number to plug into existing rules? Use Trust.
- Want a ready-made decision at the point of action? Use Shield.
- Want to find patterns of abuse over time? Use Detect.
Each intelligence product must be enabled for your account. If a product isn’t on your plan, the API responds with
400 Bad Request and a message explaining it. Contact connect@authmatech.com to enable a product.
