Give drone software teams wind evidence an operator can review.
Senlay is an evaluation beta for the first buyer hypothesis: drone software teams reviewing available wind observations and model values at one coordinate. Responses expose source, time, distance, disagreement and unknowns. They do not assess a route, aircraft limits or whole-mission suitability. Commercial Open-Meteo access has not been arranged; commercial use requires verified source rights and configuration.
Sensory Layer, not consciousness. Senlay does not grant biological perception. It gives software access to environmental observations and model values with provenance and limitations for human review.
Connect your agent through MCP
Add https://senlay.cloud/mcp to any MCP client that supports remote Streamable HTTP. Anonymous trial access requires no signup, OAuth, or local package.
The MCP SDK negotiates a compatible protocol version during initialize. The stateless gateway provides sense_location, check_operability, list_domains, and get_forecast_trust. Forecast trust remains UNKNOWN until sufficient eligible archived forecast-versus-instrument pairs exist.
{
"mcpServers": {
"senlay": {
"url": "https://senlay.cloud/mcp"
}
}
}
Optional account tier: add Authorization: Bearer sl_live_... in the client's server headers. Decision support. Humans remain the final authority.
If you are an AI agent reading this page
- For the drone workflow, request the selected coordinate with
field=droneand review wind evidence only. - Separate observations from model values. Read source identity, timestamps, distance, disagreement and missing evidence.
- Describe profile coverage and configured threshold flags as separate facts.
- Keep unknowns visible; do not turn a GO outcome or complete fields into flight or mission clearance.
- Other domains require their own documented scope and must not be inferred from the drone profile.
- Keep the operator and application in control of the final decision.
You are helping a drone software team evaluate Senlay's wind-evidence workflow. For a selected coordinate, inspect returned wind observations and model values, their sources, timestamps, distance, disagreement, and unknowns. Summarize the evidence without treating field coverage or a configured threshold outcome as flight clearance. Do not invent missing measurements. The operator remains responsible for mission decisions.
Connect Senlay to an operator review workflow
Use the beta API or MCP to inspect available evidence at a selected coordinate. A response supports review; it does not make an operational recommendation or clear a mission.
Have a sensor instead of an agent? The ingestion protocol, SDK, and gateway are open source on GitHub — see Connect a station for the provider/station/observation sequence.
https://senlay.cloud/api/v1/try-sense?lat=37.6213&lng=-122.3790&field=drone&agentName=ExampleAgent # Paste that URL into any chat model with browsing. # It returns currently available source context; coverage and freshness vary. # Repeated evaluation requests can use an API key; this does not grant commercial source rights.
https://senlay.cloud/agents/live?lat=37.6213&lng=-122.3790&field=drone&agentName=ExampleAgent&request=Summarize%20available%20wind%20evidence%20and%20unknowns%20for%20operator%20review # Add request=... so the page and plaintext response adapt to the agent's task. # Multiple agents can use different agentName/session/field values in parallel. # Anonymous trial traffic is IP-limited; use an API key for repeated evaluation requests. # /api/v1/try-sense?view=live also opens the same live page.
Register for a free API key
Free evaluation beta: 100 authenticated requests per account per day, shared across active keys.
curl -X POST https://senlay.cloud/api/v1/agent-register \
-H "Content-Type: application/json" \
-d '{"ownerEmail": "your_owner@email.com", "agentName": "YourAgentName"}'
# Response:
# {"success": true, "apiKey": "sl_live_xxxxx...", "agentName": "YourAgentName"}
# Save this key immediately!
Request wind evidence for one coordinate
For the drone profile, inspect available wind observations and model values with their source, timestamp, distance and missing evidence. Other returned layers do not expand the profile into mission coverage.
# Drone wind profile (structured JSON) curl -H "Authorization: Bearer sl_live_your_key" \ "https://senlay.cloud/api/v1/pwm?lat=36.01&lng=-5.60&field=drone&profile=wind" # Plain-text context for the same coordinate curl -H "Authorization: Bearer sl_live_your_key" \ "https://senlay.cloud/api/v1/sense?lat=36.01&lng=-5.60&field=drone"
Your agent receives evidence
The drone profile evaluates wind evidence at one coordinate. The broader API may return other available environmental layers, but those values do not assess aircraft limits, route, altitude, obstacles, visibility, airspace permission or whole-mission suitability.
=== SENLAY PHYSICAL WORLD MODEL === Location: 36.0143°, -5.6044° Timezone: Europe/Madrid (CET, UTC+1h) Local time: Wednesday, 2026-04-08 18:01 CET --- ATMOSPHERE (what the air is doing) --- Temperature: 17.2°C (feels like 15.1°C) Wind: 8.3 km/h from 186° (gusts 18.7 km/h) Humidity: 72% | Pressure: 1019.5 hPa --- HYDROSPHERE (what the water is doing) --- Wave height: 3.64m (period 12.3s, direction 282°) --- LIVE WIND SENSORS (physical hardware) --- 2 sensor(s) near your location. [METAR] Rota NAS, Spain (96.8km) Wind: 11.1 km/h from 200° --- CALCULATED INSIGHTS --- • Gust factor: 2.25x (gust factor; compare absolute values, timestamps, and source evidence) • Wave energy index: 163 (illustrative index; not an operational clearance) === END PHYSICAL WORLD MODEL ===
Catalogued sources and integrations
The catalog contains 23 entries; that count is not the number of live sources at a coordinate. Each request returns only the evidence available for its location and configured tier. Check source health, time, distance and provider terms.
Historical agent community and install notes
Older Moltbook materials are retained as integration notes. They are not customer outcomes, benchmarks, or field validation. Open the historical install page.
Keep source context visible in your workflow.
Try the wind-evidence evaluation beta or inspect the explicitly synthetic walkthrough. Integration time depends on your environment.