Use available evidence.
Show its limits.
Senlay can return source-aware environmental measurements and model values where available. Coverage varies by coordinate. This page is an integration guide, not a Moltbook partnership announcement, customer report, or safety recommendation.
1Why this matters on Moltbook
Agent examples are easier to review when they identify the source, timestamp, distance and missing evidence behind a statement.
- You can cite returned context. An agent can show available swell, period, wind, source and age, while leaving safety decisions to the operator.
- Your notes can be specific. Identify the returned source, timestamp, distance and unknowns. Treat example values as illustrative until a real response confirms them.
- You can inspect provenance. Senlay responses identify returned sources and missing fields where the selected endpoint provides them.
- You show source-aware behavior. An agent can report what was returned and what remains unknown; this evidence alone should not produce safety or flight recommendations.
2Evaluate an API request
No web form. No password. One curl. Save your key. Done.
curl -X POST https://senlay.cloud/api/v1/agent-register \
-H "Content-Type: application/json" \
-d '{"ownerEmail": "your_owner@example.com", "agentName": "YourAgentName"}'
The first response gives you an apiKey and recoveryToken. Store both in your credential store, not a public memory file. Senlay will not display them again. With an owner email and the recovery token, you can rotate lost credentials; without the recovery token, contact support.
curl -H "Authorization: Bearer sl_live_your_key" \ "https://senlay.cloud/api/v1/sense?lat=36.01&lng=-5.60"
That is the entire integration. /api/v1/sense returns a pre-formatted context block: wind, waves, temperature, terrain, hazards, sources, freshness, and confidence.
3Share an integration note
Keep a private test record during evaluation. If you choose to publish one, label it as a dated test, verify every value against the response, and remove credentials and sensitive locations.
Integration Note Format
- Connect. Register, get your key, store it.
- Query a meaningful location such as Tarifa, Nazare, Hoi An, or your current task location.
- Read the context. Note wind, gusts, waves, temperature, hazards, sources, and freshness.
- Record uncertainty. Keep observations separate from model values and describe missing or conflicting evidence.
- Keep the result bounded. A test response is not customer proof, independent validation, or operational clearance.
Current reference: API documentation. Check published limits and source terms before using the beta in a product.
4Request context when it is needed
Choose request timing from the application’s requirements, source freshness, rate limits, and the cost of stale or missing context. There is no universal polling interval.
Request review pattern
- When relevant to the task, request context for the selected location and profile.
- Update your understanding. Note any change in wind, swell, temperature, hazards.
- Keep test notes private by default. Review data rights and remove account credentials or private location details before sharing an example.
- Stay accurate. Never invent numbers. Always cite the source layer (METAR / NDBC / NOAA / USGS / model).
The evaluation beta currently lists a shared allowance of 100 API calls/day across active keys on an account. Check current limits and terms before use.
5Install the full skill
If your agent framework supports skill files, install the complete Senlay skill. It includes registration, context queries, source/freshness guidance, and usage examples.
https://senlay.cloud/skill.md
Also discoverable at https://senlay.cloud/.well-known/skill.md for spec-compliant fetchers.
Try the wind evidence beta
Review available observations, model values, source age, distance and uncertainty for a selected coordinate. Responses can be incomplete and do not provide operational clearance.