{"uid":"cap_qchlVa4TZ9CAm0OTJc-bV","slug":"rqm-trajectory-and-sensor-timing-validation-afa7b1d3","name":"RQM Trajectory and Sensor Timing Validation","description":"Problem: Validate timestamps, ordering, rates, gaps, and synchronization in this bounded trajectory or sensor trace. Input: JSON with clock id, samples, rules. Result: pass or fail verdict, normalized timeline, exact timing defects. Limits: Software/model evidence only; 65536 request bytes; 5 s execution.","url":"https://jobs.rqmtechnologies.com/x402/buyer-jobs/robotics.validate-trajectory-timing.v1","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"request":{"type":"object","title":"TrajectoryTimingRequest","required":["clock_id","samples","rules"],"properties":{"rules":{"type":"object","title":"TimingRules","required":["expected_period_seconds","period_tolerance_seconds","maximum_gap_seconds","maximum_cross_stream_skew_seconds"],"properties":{"maximum_gap_seconds":{"type":"number","title":"Maximum Gap Seconds","exclusiveMinimum":0},"expected_period_seconds":{"type":"number","title":"Expected Period Seconds","exclusiveMinimum":0},"period_tolerance_seconds":{"type":"number","title":"Period Tolerance Seconds","minimum":0},"maximum_cross_stream_skew_seconds":{"type":"number","title":"Maximum Cross Stream Skew Seconds","minimum":0}},"additionalProperties":false},"samples":{"type":"array","items":{"type":"object","title":"TimingSample","required":["stream_id","sequence","timestamp_seconds"],"properties":{"sequence":{"type":"integer","title":"Sequence","minimum":0},"stream_id":{"type":"string","title":"Stream Id","maxLength":64,"minLength":1},"timestamp_seconds":{"type":"number","title":"Timestamp Seconds","minimum":0}},"additionalProperties":false},"title":"Samples","maxItems":20000,"minItems":2},"clock_id":{"type":"string","title":"Clock Id","maxLength":64,"minLength":1},"schema_version":{"type":"string","const":"rqm.robotics.trajectory-timing-request.v1","title":"Schema Version","default":"rqm.robotics.trajectory-timing-request.v1"}},"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_hBDwfOuqEEerapv3P5zrH","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":"Validates timestamps, ordering, sample rates, gaps, and cross-stream synchronization in a bounded trajectory or sensor trace against caller-specified timing rules.","exampleAgentPrompt":"Check whether my robot arm trajectory timing is valid — I have 500 samples from two streams (arm_joint and wrist_force) with a clock ID 'ros_clock', expected period of 0.01 seconds, tolerance of 0.002 seconds, maximum gap of 0.05 seconds, and maximum cross-stream skew of 0.005 seconds.","exampleUseCases":[{"title":"Autonomous vehicle sensor sync check","prompt":"I have LiDAR and camera samples from my autonomous vehicle test run — clock ID is 'vehicle_monotonic', 1200 samples total across two streams, expected period 0.05s, tolerance 0.005s, max gap 0.2s, max cross-stream skew 0.01s. Validate whether they are properly synchronized and flag any timing violations."},{"title":"Robot arm trajectory gap detection","prompt":"My robot arm recorded 800 trajectory samples across three joint streams with clock ID 'ethercat_clock'. The expected sample period is 0.004 seconds with a tolerance of 0.001s, and I want to catch any gaps larger than 0.02 seconds. Can you validate the timing and tell me if there are any issues?"},{"title":"Drone IMU timing validation before fusion","prompt":"Before I fuse my drone's IMU data, I need to validate the timing — clock ID 'px4_clock', 3000 samples from gyro and accelerometer streams, expected period 0.002s, tolerance 0.0005s, max gap 0.01s, cross-stream skew limit 0.001s. Are there any ordering errors or rate violations?"}],"resultDescription":"A structured validation report indicating whether the trajectory or sensor trace passes all specified timing rules, including details on any detected violations such as out-of-order sequences, period deviations outside tolerance, gaps exceeding the maximum, and cross-stream skew beyond the allowed threshold.","failureModes":["Fewer than 2 samples provided — request rejected","Samples exceed 20000 item limit — request rejected","Invalid or missing clock_id — schema validation error","Missing required timing rules fields — schema validation error","expected_period_seconds or maximum_gap_seconds not greater than zero — schema validation error","Malformed timestamp values (negative or non-numeric) — validation error"],"whenToPreferThis":"Use this endpoint when you need to programmatically verify that a bounded set of trajectory or sensor samples conforms to specific timing contracts — such as expected sample rate, gap limits, and cross-stream synchronization tolerances — before passing data to downstream fusion, planning, or control algorithms. Prefer this over manual inspection when dealing with multi-stream robotics data where ordering and synchronization correctness must be guaranteed. Not suitable for validating physical clock hardware, network-level causality, or real-time streaming data.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T06:55:13.257Z","isFirstParty":false}