Diff ROS topic schemas API

Compare caller-supplied left/right ROS topic message types and fields. Missing schemas are not invented.

The Diff ROS topic schemas operation is part of the Industrial Robotics & Automation Intelligence API on BRAINIAC.software. Compare caller-supplied left/right ROS topic message types and fields. Missing schemas are not invented. It is exposed as POST /api/v1/robotics-intelligence/ros-topic-schema-diff and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied ROS bag topic exports, schemas, robot telemetry, cycles, downtime, OPC UA tags, PLC alarms, maintenance records, and protocol declarations Limitations: No live industrial equipment connection is opened and no machine commands are issued. Binary .bag/.mcap files are not fully decoded. Supply topic CSV/JSON exports or labeled sample rows. Anomaly, cycle-time, downtime, and maintenance estimates use only supplied measurements and intervals. Missing values are not invented. Protocol compatibility compares caller-supplied required versus available protocol names, versions, and features only. Workcell reports aggregate only sections for which records were supplied. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Parse ROS bag telemetry exports, Detect robot telemetry anomalies, Analyze robot cycle time, Cluster robot downtime root causes. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/robotics-intelligence/ros-topic-schema-diff

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/robotics-intelligence/ros-topic-schema-diff" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "asOf": "2026-11-04T21:00:00.000Z",
  "schemas": [
    {
      "id": "A1",
      "topic": "/joint_states",
      "side": "left",
      "messageType": "sensor_msgs/JointState",
      "fields": [
        {
          "name": "position",
          "type": "float64[]"
        },
        {
          "name": "velocity",
          "type": "float64[]"
        }
      ],
      "source": "Caller-supplied"
    },
    {
      "id": "B1",
      "topic": "/joint_states",
      "side": "right",
      "messageType": "sensor_msgs/JointState",
      "fields": [
        {
          "name": "position",
          "type": "float64[]"
        },
        {
          "name": "effort",
          "type": "float64[]"
        }
      ],
      "source": "Caller-supplied"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Industrial Robotics & Automation Intelligence APIFull docsHow it works