Discuss a Senlay evaluation or ask for support.
We are exploring source-aware wind evidence workflows with drone software teams. The robotics use case is under evaluation; a conversation does not imply a running customer pilot.
Why Senlay Exists
Founder
I'm Viktor Kryvotsiuk, a Ukrainian founder based in Hoi An, Vietnam. For more than twenty years I have worked close to wind, water, weather, and risk as a kitesurfing instructor, water-sports operator, hardware builder, and self-taught engineer.
Origin
Senlay grew out of my earlier SmartSurf product work. It is the origin story and reference experience that led me to ask how software can inspect environmental evidence at a selected coordinate. SmartSurf is not evidence of paid Senlay traction or validated drone use.
To answer it, I had to combine weather stations, ocean buoys, tide gauges, swell models, air-quality networks, terrain, and satellite data into one usable picture.
Focus
Senlay is an evaluation beta for location-level environmental evidence. The first buyer hypothesis is a drone software team reviewing available wind observations and model values, their source, age, distance, agreement and gaps. The product does not evaluate a whole flight or authorize a launch.
If wind, waves, weather, tides, air quality, terrain, device telemetry, or environmental risk can change a decision in your product, Senlay can provide the evidence layer behind that decision.
— Viktor Kryvotsiuk. Hoi An, Vietnam.
Contact Viktor
Common Questions
How do I get an API key?
Start at senlay.cloud/pricing, choose Free Developer, then create your API key. No credit card required; you get 100 requests/day immediately. AI agents can also use /api/v1/agent-register with no password.
What counts as one request?
Each authenticated call presented to /api/v1/pwm or /api/v1/sense counts as one request, including cache hits. The daily allowance is shared across all active API keys on the account. Caching reduces upstream work and latency; it does not make the customer call free. Invalid requests or upstream failures may also consume quota after authentication.
Which locations are supported?
Any valid coordinate on Earth can be queried, but source coverage and quality vary. Coastal and urban areas often have more hardware sensors; inland and remote areas may rely more on model data with less cross-referencing. Always inspect timestamps, source health, distance, and uncertainty rather than assuming accuracy.
How fresh is the data?
Freshness varies by model run and station cadence. Hardware sources such as METAR, NDBC buoys, and NOAA tide gauges commonly report on different schedules, and some can be delayed or unavailable. Inspect the response timestamps, freshness labels, distance, and source health instead of assuming a fixed update interval.
Can I use Senlay with my own AI model?
Yes. The /api/v1/pwm endpoint returns structured evidence with source provenance, freshness, confidence, uncertainty, and risk context. See the docs.
I'm building an AI agent or safety app — how do I integrate?
Start with the drone wind-evidence demo or follow the authenticated API quickstart. The public demo is an evaluation surface; commercial source terms and any pilot scope must be agreed before commercial deployment. Senlay does not provide flight clearance.
What if a sensor is wrong?
Neither a sensor observation nor a model value is automatically ground truth. A sensor can be stale, mislocated, uncalibrated, or unrepresentative; a model can miss local conditions. Senlay exposes source, time, distance, and disagreement where available so an operator can review the uncertainty. If you spot a problem, email the coordinate and request time.
Is there a paid tier?
The evaluation beta is available now. Paid subscriptions have not launched. The pricing page shows proposed options; commercial source rights and any pilot scope require separate confirmation.
API Support
Found incorrect data, a broken endpoint, or unexpected behavior? Email viktor@senlay.cloud with:
- The coordinates you queried
- The timestamp (UTC if possible)
- What you expected vs. what you got
- Your API key prefix (first 12 chars only — never paste the full key)