For SmartSurf-style safety, API access, pilot deployments, partnerships, investor conversations, and support.
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.
Senlay grew out of my earlier SmartSurf work: a waterproof GPS tracker and safety layer for riders, boards, schools, stations, and local rescue workflows. That work forced one question again and again: what is really happening at this exact coordinate, right now?
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.
Senlay is now focused on one product: a physical-world verification API for SmartSurf, outdoor AI apps, IoT systems, and safety applications. It is built for teams working on SmartSurf-style monitoring, drones, field operations, agriculture, marine routing, outdoor work, and safety software.
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.
Start at senlay.world/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.
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.
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.
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.
Yes. The /api/v1/pwm endpoint returns structured evidence with source provenance, freshness, confidence, uncertainty, and risk context. See the docs.
For a quick browser/chat trial, open /api/v1/try-sense?lat=15.8801&lng=108.3380&field=kitesurfing. For a self-updating browser view, use /agents/live with the same parameters plus optional request=.... For production, use /api/v1/agent-register to get a key without passwords, then call /api/v1/sense for plain-text output or /api/v1/risk-events for SmartSurf-style alert workflows. See agentic tooling docs and risk event docs.
Hardware sensors win over models. Senlay cross-references both and flags discrepancies in the PWM context. If you spot bad data, email me with the coordinates and timestamp — I'll investigate.
Open beta is available now. Planned paid tiers are Agent / IoT Developer at $29/month, Safety Pilot from $199/month, and custom enterprise verification pilots for production use.
Found incorrect data, a broken endpoint, or unexpected behavior? Email viktor@senlay.world with: