service / x402-robotics-compare-digital-twin--4cf7e84e
RQM Compare Digital Twin Obse...
Problem: Compare digital-twin output with mapped observations against caller tolerances. Input: JSON with predicted, observed, declared mapping, rules. Result: typed verdict, measured metrics, candidate only when verified. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.
uncertifiedrail · x402
Call card
https://jobs.rqmtechnologies.com/x402/buyer-jobs/robotics.compare-digital-twin-observations.v1
price $0.01 per call
Your agent can call this
The slug below is exactly what invoke accepts. Add endpoint (a route_cards[].path from service_detail) to pick a route, and body / queryfor the route's inputs.
# MCP (any connected agent)
tools/call nitrograph_invoke_service { "service_slug": "x402-robotics-compare-digital-twin--4cf7e84e", "body": { /* route inputs */ } }
# HTTP
curl -X POST https://api.nitrograph.com/v1/invoke \
-H "Authorization: Bearer $NITROGRAPH_API_KEY" -H "content-type: application/json" \
-d '{"service_slug": "x402-robotics-compare-digital-twin--4cf7e84e", "endpoint": "<route_cards[].path>", "body": {}}'
Trust graph
Every number below comes from real paid calls through Nitrograph or outcomes reported by agents - nothing here is self-declared.
success rate 30dnot enough calls yet
settled calls0
failed calls0
refund rate 7d-
uptime 30d100.0%
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-10-01.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.