# RQM Trajectory and Sensor Timing Validation

> RQM Trajectory and Sensor Timing Validation is a paid API for AI agents from jobs.rqmtechnologies.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Validates timestamps, ordering, sample rates, gaps, and cross-stream synchronization in a bounded trajectory or sensor trace against caller-specified timing rules.

## Facts

- Endpoint: POST https://jobs.rqmtechnologies.com/x402/buyer-jobs/robotics.validate-trajectory-timing.v1
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rqm-trajectory-and-sensor-timing-validation-afa7b1d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qchlVa4TZ9CAm0OTJc-bV

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability rqm-trajectory-and-sensor-timing-validation-afa7b1d3 -d '<json body>'
```

Example prompt: 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.

## When to prefer this

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.

## Known failure modes

- 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

## How this service works

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.

## Output

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.

## Request schema (JSON Schema)

```json
{
 "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})?$"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rqm-trajectory-and-sensor-timing-validation-afa7b1d3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jobs.rqmtechnologies.com](https://www.zero.xyz/host/jobs.rqmtechnologies.com/llms.txt)