{"uid":"cap_IWsdnugC26cCxRANOIBKz","slug":"rqm-compute-actuator-alignment-correction-51369077","name":"RQM Compute Actuator Alignment Correction","description":"Problem: Compute a bounded actuator alignment correction from these observations and caller acceptance limits. Input: JSON with observations, model, rules. Result: correction parameters, pre/post residuals, applicability verdict. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.","url":"https://jobs.rqmtechnologies.com/x402/buyer-jobs/robotics.compute-actuator-alignment-correction.v1","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"request":{"type":"object","title":"AlignmentRequest","required":["observations","model","rules"],"properties":{"model":{"enum":["constant_additive_offset","robust_median_offset"],"type":"string","title":"Model"},"rules":{"type":"object","title":"AlignmentRules","required":["maximum_post_correction_rmse","maximum_absolute_correction"],"properties":{"maximum_absolute_correction":{"type":"number","title":"Maximum Absolute Correction","maximum":1000000000,"minimum":0},"maximum_post_correction_rmse":{"type":"number","title":"Maximum Post Correction Rmse","maximum":1000000000,"minimum":0}},"additionalProperties":false},"observations":{"type":"array","items":{"type":"object","title":"AlignmentObservation","required":["commanded","observed"],"properties":{"observed":{"type":"array","items":{"type":"number"},"title":"Observed","maxItems":12,"minItems":1},"commanded":{"type":"array","items":{"type":"number"},"title":"Commanded","maxItems":12,"minItems":1}},"additionalProperties":false},"title":"Observations","maxItems":4096,"minItems":2},"holdout_observations":{"type":"array","items":{"type":"object","title":"AlignmentObservation","required":["commanded","observed"],"properties":{"observed":{"type":"array","items":{"type":"number"},"title":"Observed","maxItems":12,"minItems":1},"commanded":{"type":"array","items":{"type":"number"},"title":"Commanded","maxItems":12,"minItems":1}},"additionalProperties":false},"title":"Holdout Observations","maxItems":4096}},"additionalProperties":false},"schema_version":{"const":"rqm.jobs.bazaar-buyer-job-request.v1"},"idempotency_key":{"type":"string","pattern":"^[A-Za-z0-9][A-Za-z0-9._:-]*$","maxLength":128,"minLength":1},"max_total_price":{"type":"string","pattern":"^(?:0|[1-9]\\d{0,13})(?:\\.\\d{1,6})?$"}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_G613aiffhwjRcmSy4Drew","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Computes a bounded constant additive-offset actuator alignment correction from commanded-vs-observed pairs, subject to caller-specified RMSE and absolute correction limits","exampleAgentPrompt":"Compute an actuator alignment correction using a constant additive offset model for these 50 commanded-vs-observed joint angle pairs, with a maximum absolute correction of 0.5 and a maximum post-correction RMSE of 0.05 — I need this before running the simulation.","exampleUseCases":[{"title":"Pre-simulation joint offset calibration","prompt":"Before I run the dynamics sim, compute the additive alignment correction for my robot arm joints — I have 200 commanded and observed angle pairs, and I need the correction capped at 0.25 radians absolute and post-correction RMSE under 0.02."},{"title":"Operator review of actuator bias","prompt":"I want to check whether our actuator has a systematic offset before the operator signs off — run the constant additive offset alignment computation on these 80 commanded-vs-observed samples, with a max absolute correction of 1.0 and max RMSE of 0.1."},{"title":"Factory calibration alignment check","prompt":"After assembly, compute the actuator alignment correction for our new unit using these 300 commanded and observed position pairs — use the constant additive offset model, cap the correction at 0.75 and keep post-correction RMSE below 0.03."}],"resultDescription":"Returns a bounded actuator alignment correction value computed under the constant additive offset model, along with validation against the caller's specified maximum absolute correction and maximum post-correction RMSE limits. The result is suitable for use as a pre-simulation or pre-review correction offset, not for direct hardware actuation.","failureModes":["Insufficient observations (fewer than 2 commanded/observed pairs) returns a validation error","Commanded and observed arrays of mismatched lengths cause a schema rejection","Computed correction exceeds maximum_absolute_correction limit — correction rejected with bounds violation","Post-correction RMSE exceeds maximum_post_correction_rmse — result flagged as out of tolerance","Observations arrays exceed 12 elements per item — schema validation failure","Payment not attached or insufficient — x402 payment required error","Idempotency key malformed — request rejected"],"whenToPreferThis":"Use this endpoint when you need a pre-simulation or pre-operator-review actuator alignment correction computed under an explicit constant additive offset model, with hard bounds on both the correction magnitude and residual RMSE. Prefer this over generic regression or calibration tools when you need guaranteed bounded outputs and a well-defined additive model. Do not use this to directly command hardware or to infer a physical model that was not declared in the request.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T12:51:09.940Z","isFirstParty":false}