Maritime Navigation API

Everything to connect is in one public repository: the OpenAPI specification, the data models, Python and JavaScript clients, an MCP server for Claude, Cursor, VS Code, Windsurf and Zed, and a GitHub Action that checks a route against the warnings in force. The endpoints stay the ones below; the kit is the way in.

• Editors and agents: add the MCP server and ask in plain words; the tools are search_warnings, warnings_near, route_check, navareas and feeds.
• Code: python/sealagom.py and js/sealagom.mjs, no dependencies beyond requests or fetch; generate any other language from openapi.yaml.
• No-code and agents: import sealagom.com/openapi.json into n8n, Make, Zapier, Pipedream, Postman, ChatGPT actions or LangChain. Send the key as X-API-Token or Authorization: Bearer.
• Routes: POST /api/v2/route/ with a route file or waypoints, or the drop link /api/v2/drop/<key>/route/ for tools that can only POST a file.
• Sky view: GET /api/v2/sky/link/?vessel= (or mmsi, warning and region, port, locode, lat and lon) gives a ready link that stands there in the sky view; POST /api/v2/sky/route/ takes a route and gives its sky link, drawn on the sea, with the RTZ and GPX. Section 20 of the README has the calls. Not for navigation.
• CI: the Action fails a build when a critical warning lies on a route kept in the repository.
• Scripts and agents paying for themselves: POST /api/agent/checkout/, crypto, the key once paid (in the profile when the e-mail already has an account).

Gumagamit ang API v2 ng parehong token, plano at request accounting gaya ng v1. Lahat ng nasa ilalim ng /api/v1/ ay magpapatuloy na gumana nang eksakto gaya ng dati, kaya ang umiiral na mga integration ay hindi kailangang baguhin. Nagdadagdag ang v2 ng:

• Isang listahan ng lahat ng warning: GET /api/v2/messages/, NAVAREA at coastal na magkasama, pinakabago muna, bawat mensahe kasama ang rehiyon, bansa at archive status.
• Message filters sa mga region endpoints: /api/v2/navarea/ and /api/v2/coastal/ sumasagot tulad ng v1 at nag-aapply din date_from, date_to, keyword and has_coordinates sa mga mensaheng ibinabalik nila.
• Mga setting na nasasave sa bawat token: pumili ng token sa Profile > API > API v2 builder, buuin ang response gamit ang mga menu at live preview, at i-save. Bawat /api/v2/ call gamit ang token na iyon ay magbabalik ng ganoong shape; ang mga /api/v1/ call ay hindi pinapansin ang saved settings at sasagot nang eksakto gaya ng dati.
• prompt filter (Full API):ilarawan sa sariling salita ang mga warnings na dapat ibalik ng isang token, halimbawa "only space debris warnings around the USA".
• Integrate: the kit on GitHub (OpenAPI spec, clients, MCP server, Action) is the way in; a README.md per token, with its settings, plan and every parameter and field, is there for any program that wants one file.
• Settings file:instead of ticking options, ask LagoPal (with the README) for a settings file: a small JSON file with the token's endpoint, parameters and prompt. Load it on Profile > API (Load settings file); it fills the builder so you can check the live preview before saving. Download settings file gives the current settings in the same form. JSON Schema: /api/public/api-settings-schema/.

GET /api/v2/messages/

Mga field o filter na hindi kasama ng iyong plan ay iniwan at nakalista sa meta.warnings, hindi kailanman isang error.

content ay ang tekstong na-broadcast; content_en is the English text (the official English version or a machine translation) for sources that broadcast in another language, such as China or Turkey, and source_language nagtutukoy ng orihinal na wika.

Ang US Coast Guard Local Notices to Mariners (10 distrito, ina-update lingguhan) ay mga baybaying rehiyon na pinamagatang US Coast Guard LNM, country US. They are not analysed, so their automatic fields are empty; each district also has one message, number LNMxx-DISCREPANCIES, na naglilista ng mga aids to navigation nito na may pagkakaiba.

curl "https://www.sealagom.com/api/v2/messages/?country=France&include_coordinates=true&include_ai_analysis=true" \
  -H "X-API-Token: YOUR_API_TOKEN"

{
  "count": 42,
  "page": 1,
  "page_size": 50,
  "next": null,
  "previous": null,
  "results": [
    {
      "scope": "coastal",
      "region_id": 57,
      "region_title": "FRANCE Atlantic",
      "country": "France",
      "is_archived": false,
      "archived_on": null,
      "id": 90211,
      "number": "AVURNAV 1234/26",
      "content": "BAY OF BISCAY. DRIFTING BUOY ...",
      "content_en": "BAY OF BISCAY. DRIFTING BUOY ...",
      "source_language": "en",
      "added_on": "2026-09-27T08:10:00Z",
      "coordinates": ["45-10.0N 002-05.0W"],
      "ai_analysis": { "headline": "...", "severity": "moderate", "valid_until": null }
    }
  ]
}

Mga setting na naka-save sa isang token

• Isang token, isang hugis: each token keeps its own endpoint and parameters. Need a second shape (say France coastal with coordinates, and a worldwide feed)? Create a second token.
• Ipinapakita ang bawat option, Kasama ang mga Full API, kasama ang planong kailangan ng bawat isa. Ang pag-save ay nangangailangan ng aktibong API plan.
• Panalong URL: anumang parameter na ilalagay mo sa URL ay pumapalit sa naka-save na halaga para sa tawag na iyon; ?settings=off gumagawa ng simpleng tawag.
• Mga relatibong panahon: "huling 30 araw" nagpapadala date_from bilang ngayon minus 30 araw sa bawat tawag.
• Ang mga tugon ay nagdadala ng isang X-API-Token-Settings header na nagbabanggit ng token na ang mga setting ang inilapat.

Ice feed: GET /api/v2/ice/

• Every warning about ice at sea, from NAVAREA, coastal and NAVTEX sources: icebergs and iceberg limits, sea ice, ice edge, vessel icing and freezing spray, ice reports, icebreaker operations and ice navigation rules. An model reads each warning that mentions ice and keeps only those really about it, with its kind in ice.type.
• Positions, shapes (iceberg limit lines, ice areas) and the analysis are included by default. ?output=geojson nagbabalik ng GeoJSON FeatureCollection, isang feature bawat hugis, handa para sa route checks at chart overlays.
• ice_type pinapaliit ito: iceberg, sea_ice, ice_edge, icing, ice_report, icebreaker, ice_navigation, other_ice (ulit-ulitin o paghiwalayin ng kuwit). Bawat /api/v2/messages/ parameter ay gumagana rin, at /api/v2/messages/?topic=ice ay parehong feed.
• Full API plan, o isang ice feed licence (taunan, ifi-invoice): makipag-ugnayan sa amin.

curl "https://www.sealagom.com/api/v2/ice/?output=geojson&ice_type=iceberg,ice_edge" -H "X-API-Token: YOUR_API_TOKEN"

Themed feeds: GET /api/v2/feeds/<feed>/

• Ready-made feeds built from the category the analysis gives every warning: military exercises and firing, rocket launches and space debris, cable and pipeline work, offshore works and rigs, surveys, wrecks and drifting hazards, aids to navigation, search and rescue, security and restricted areas.
• Same output as the ice feed: positions, shapes and the analysis by default, the category in feed.category, ?output=geojson para sa isang FeatureCollection at ?category=upang panatilihin lamang ang ilan sa mga kategorya ng isang feed. Bawat /api/v2/messages/ parameter ay gumagana rin, at /api/v2/messages/?topic=military ay parehong feed.
• Only warnings with an analysis are included. GET /api/v2/feeds/ (walang token na kailangan) inililista ang bawat feed kung ilan sa mga babala nito ang kasalukuyang epektibo.
• Full API plan, o isang feed licence para sa isang solong feed (taunan, ifi-invoice): makipag-ugnayan sa amin.
• Free and without a token, for feed readers and scripts: RSS at /feeds/warnings.xml, /feeds/navarea/<id>.xml and /feeds/coastal/<id>.xml; the same three as Atom (.atom) and JSON Feed 1.1 (.json); plain text at /feeds/warnings.txt. The newest 100 warnings, text only, a warning keeps its id when it is updated. Region pages carry the feed links in their head, so a reader finds the feed from the page address.

Naglo-load ng feeds…

curl "https://www.sealagom.com/api/v2/feeds/military/?output=geojson&navarea_id=3" -H "X-API-Token: YOUR_API_TOKEN"

prompt filter

• Write what you want in plain words on the token (Full API plan). When you save, a model checks every warning in force against it; each new warning is checked within about 10 minutes of arriving.
• /api/v2/messages/ ang mga tawag na may token na iyon pagkatapos ay magbabalik lamang ng mga babalang tumutugma. Ang isang babalang tumugma habang epektibo ay mananatiling tumugma pagkatapos itong ma-archive.
• Dinadagdag ng tugon ang meta.prompt_filter na may prompt, ang status nito ("matching kasunod ng pag-save, ready pagkatapos) at kung ilan ang tumugmang babala. ?prompt_filter=off binalewala ito para sa isang tawag.
• The filter can miss or over-include a warning. Use it to narrow a feed, not as the only safety check; the official broadcast stays the authority.

# Token with saved settings: nothing else needed
curl "https://www.sealagom.com/api/v2/messages/" -H "X-API-Token: YOUR_API_TOKEN"

# Same token, override the period for one call
curl "https://www.sealagom.com/api/v2/messages/?date_from=2026-09-01" -H "X-API-Token: YOUR_API_TOKEN"

# Token with the prompt "only space debris warnings around the USA"
{
  "count": 3,
  "results": [ ... ],
  "meta": {
    "prompt_filter": {
      "prompt": "only space debris warnings around the USA",
      "status": "ready",
      "matched": 3
    }
  }
}