Review wind evidence
Compare available measured and model values while keeping source location, time, freshness, and disagreement visible.
Environmental intelligence for autonomous systems
Senlay for robotics and autonomous systems.
Give drone, marine, and field robotics teams a structured view of environmental conditions around a place. Senlay combines available observations and forecasts and reports their provenance, freshness, disagreement, and uncertainty through an API and MCP.
The current product verifies available evidence for a spot and time. Mission routes, platform-specific limits, and conditions across an operation remain a product direction for future work.
Decision support only. Assessments do not replace onboard safety systems, operator judgment, or applicable procedures.
Aerial systems
Drone and UAV operations.
Bring current environmental context into mission preparation and human-supervised operational reviews. The existing drone domain focuses on available wind and gust evidence, with secondary flags for conditions such as visibility and precipitation. Available data varies by place.
See what is unknown
Missing or weak evidence should remain visible for the pilot or operator to assess.
Keep the operator in control
Use Senlay as one input to planning. It does not command a flight or certify a launch decision.
Marine robotics
Environmental context for unmanned surface vessels.
Applications can request available wind, wave, tide, and marine observations for a coordinate. Marine coverage depends on location and source proximity. Senlay does not currently evaluate a vessel's route, maneuver limits, or a complete voyage.
Outdoor and field robotics
Context for agricultural and inspection platforms.
Use available weather and environmental evidence to support workflows for field robots, remote infrastructure inspection, agriculture, and outdoor industrial systems. Domain-specific evaluations must be scoped and validated for each application.
Agricultural operations
Consider available wind, temperature, humidity, and precipitation context when planning outdoor work windows.
Remote inspection
Review current source coverage and freshness for the area around an inspection site.
Industrial field work
Pass structured context to operator dashboards or application logic that already applies platform and site rules.
Integration architecture
A small, reviewable path from telemetry to environmental context.
Robotics software provides the current location. An integration calls Senlay's existing spot-level endpoint, then presents the returned evidence to the robot application or operator. The application retains control of platform-specific checks.
Environmental Sources→Senlay Verification Layer→Structured API / MCP→Robot Software / Operator
Existing structured endpoint · authenticated spot-level context
curl --get 'https://senlay.cloud/api/v1/pwm' \
--header "Authorization: Bearer $SENLAY_API_KEY" \
--data-urlencode 'lat=37.775' \
--data-urlencode 'lng=-122.419' \
--data-urlencode 'field=drone'Use current coordinates from your own telemetry source. Check the returned evidence and source freshness in your application. A coordinate request is not route or mission verification.
Read only telemetry examples
Reference adapters in the Senlay project currently support CRC-checked MAVLink 1/2 GPS_RAW_INT and GLOBAL_POSITION_INT frames over UDP, and ROS 2 sensor_msgs/msg/NavSatFix over a separately installed rosbridge WebSocket. The examples pass a valid current position to Senlay's existing endpoint; they do not send navigation, mission, or actuator commands.
ROS 2 local-coordinate messages are not converted. Remote rosbridge connections require wss://. MAVLink CRC checks do not authenticate the UDP sender, so use a trusted robot network. Freshness is measured from local message receipt; inspect the sensor timestamps, source evidence, confidence, and unknowns yourself. The adapter does not produce safety clearance or mission evaluation.
Native ArduPilot, PX4, and BlueOS integrations are not claimed. Node.js 22 and a Senlay API key are required to run the examples; credentials belong in the SENLAY_API_KEY environment variable, not a URL.
SENLAY_API_KEY=... node examples/robotics/robotics-context.mjs \
--transport mavlink-udp --port 14550 --field drone
SENLAY_API_KEY=... node examples/robotics/robotics-context.mjs \
--transport rosbridge --rosbridge-url ws://127.0.0.1:9090 \
--topic /gps/fix --field agricultureMission Environmental Verification · Planned
Evaluate context across the operation.
The longer-term direction is to evaluate environmental conditions against a system's actual mission: route and location, planned operating time, altitude or marine environment, platform-specific limits, evidence freshness, uncertainty, and changing conditions.
Spot-level context
The existing API can return available environmental and evidence context for a coordinate and selected domain.
Mission-aware evaluation
Combining a complete route, schedule, platform constraints, and changing conditions is future work.
No simulated mission result
This page describes a product direction, not an available mission endpoint, route simulation, or completed flight-control integration.
Technical partners and pilot customers
Discuss an integration for your platform.
Share your robotics domain, telemetry source, operating environment, and evidence needs. Pilot scope and platform compatibility are confirmed case by case.