For drone software teams

Review wind evidence for a location.

Senlay returns available wind measurements and forecasts for a coordinate, with source, age, distance, agreement, and missing evidence visible in a structured response.

The drone wind profile checks available speed, gust, and direction evidence. It does not assess routes, aircraft-specific limits, airspace, or whole-mission suitability.

Try the drone wind demo Download reference adapters Read API and MCP docs

Evaluation beta · Spot-level evidence only. No flight authorization, mission assessment, or robot control.

Aerial systems

Drone and UAV operations.

Bring current environmental context into mission preparation and human-supervised operational reviews. The demo uses a wind-only profile: available wind and gust evidence, source age, distance and model comparison. Visibility, precipitation, obstacles, airspace, aircraft limits, route and altitude are not assessed by that profile. Available data varies by place.

Review wind evidence

Compare available measured and model values while keeping source location, time, freshness, and disagreement visible.

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.

See SmartSurf, an existing maritime application

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.

Application sends coordinateSenlay returns available evidenceSoftware / operator reviews

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' \
  --data-urlencode 'profile=wind'

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.

Download and run a read-only example

Download robotics examples v0.1.0 (ZIP) SHA-256 · Bundle manifest

Requires Node.js 22. No npm install is needed. The bundle includes its README, scoped license, SDK, fixtures, tests and manifest. Start with the explicitly synthetic replay: it uses synthetic position and environmental evidence, without an API key, network access, hardware, or robot commands.

unzip senlay-robotics-v0.1.0.zip
cd senlay-robotics-v0.1.0
node examples/robotics/robotics-context.mjs --transport replay

Live mode is separate. The adapters support CRC-checked MAVLink 1/2 GPS_RAW_INT and GLOBAL_POSITION_INT position frames over UDP, and ROS 2 sensor_msgs/msg/NavSatFix through a separately installed rosbridge WebSocket. Set SENLAY_API_KEY in your environment before a live request. The listener passes current coordinates to Senlay; it does not issue navigation, mission or actuator commands.

# After setting SENLAY_API_KEY in your shell environment:
node examples/robotics/robotics-context.mjs \
  --transport mavlink-udp --port 14550 --field drone

node examples/robotics/robotics-context.mjs \
  --transport rosbridge --rosbridge-url ws://127.0.0.1:9090 \
  --topic /gps/fix --field agriculture

Live environmental requests default to one every 120 seconds (30/hour). The free account allowance is shared across keys and is 100 calls/day: roughly 3 hours 20 minutes at that interval if no other calls are made. This is environmental context, not a robot control loop.

ROS 2 local-coordinate messages are not converted. Remote rosbridge requires wss://. MAVLink CRC does not authenticate senders: use a trusted robot network. Receipt-time freshness cannot establish that an upstream sensor is current. Native ArduPilot, PX4 and BlueOS APIs and real-hardware validation are not claimed.

Current Open-Meteo access is not licensed for paid production use. Evaluation, source rights, coverage, reliability and domain-specific validation must be confirmed before commercial deployment. Mission evaluation and flight clearance are not provided.

Mission 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.

Available now

Spot-level context

The existing API can return available environmental and evidence context for a coordinate and selected domain.

Planned direction

Mission-aware evaluation

Combining a complete route, schedule, platform constraints, and changing conditions is future work.

Boundary

No simulated mission result

This page describes a product direction, not an available mission endpoint, route simulation, or completed flight-control integration.

For robotics software teams

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.

Contact Senlay Read API and MCP docs See the roadmap