# Rynda — Extended LLM Context

## Who Rynda is

Rynda (rynda.io) is a maritime intelligence platform operated by **RYNDA GLOBAL FZCO** (Dubai, United Arab Emirates). It does three things for shipowners, operators, charterers, brokers and compliance teams: tracks vessels on a live AIS map, alerts fleet operators when something happens to their ships, and checks a vessel and its owner before a deal. A cargo and open tonnage board and free maritime calculators sit alongside.

- Website: https://rynda.io
- Contact: info@rynda.io
- Headquarters: Dubai, UAE

## Services

### 1. Live vessel map
[https://rynda.io/ports-map](https://rynda.io/ports-map) — interactive maritime map combining six tools in one surface: live AIS tracking for 100,000+ vessels worldwide, vessels-in-port view with congestion analytics, "Open for Orders" charter availability board, multi-port sea route calculator (waypoints, chokepoints, GeoJSON and PDF voyage memo export), a directory of 15,000+ ports with World Port Index data, and vessel search / tracking by name, IMO or MMSI.

### 2. My Fleet — vessel monitoring and event alerts
[My Fleet](https://rynda.io/fleet) is a fleet-monitoring workspace built on top of the live AIS map. Users add vessels by IMO number and get: live positions and voyage state for the whole fleet on one map, position lists, 13 configurable alert types (port arrival and departure, enter and leave area, ETA change, arrival approaching, destination change, speed change, draught change, AIS lost, anchor dragging, ship-to-ship, vessel opening) delivered to Telegram and email, open-tonnage forecasts, cargo-nearby matching against the Rynda cargo board, voyage analytics, sanctions screening against the same official lists as vessel profiles, team seats and shared vessel notes. The free plan covers up to 3 vessels with port arrival and departure alerts; paid plans extend fleet size, alert types, history depth and team features (published on the pricing page).

Event alerts are the core of My Fleet: Rynda watches the vessels a user cares about and reports the event itself — the ship arrived, left, changed destination, went silent on AIS, started drifting at anchor or came alongside another ship — to Telegram and email, so nobody has to keep a map open.

### 3. Vessel check — vessel profiles
One page per IMO-registered merchant vessel (bulk carriers, tankers, container ships, general cargo) at /vessels/[imo]-[slug], for example [https://rynda.io/vessels/9287766-wilson-perth](https://rynda.io/vessels/9287766-wilson-perth). Each profile is keyed by the durable IMO number — slugs follow the current vessel name and 301-redirect on rename. Per-vessel facts surfaced from primary sources (IMO ship registry, classification societies, Paris/Tokyo MoU databases, OFAC SDN, EU FSF, EU Official Journal vessel listings, UK FCDO, Swiss SECO, Canadian autonomous, Australian DFAT, UN 1718 sanctions lists): identity (name + name history, MMSI, call sign, flag state with year-of-effect), hull particulars (DWT, GT, LOA, beam, draught, year built, builder + country, classification society + notation, main engine maker / type / kW), live AIS telemetry when broadcast (current speed, course, destination, ETA, last fix age, navigation status), compliance (class status, PSC inspections + outcomes over the trailing 36 months, detention counts, MoU band heuristic), sanctions screening per list — match / no match by IMO as of the check date, never a clearance, and the ownership chain (registered owner, ship manager, ISM manager) as published by primary registry sources. Owner, sanctions, PSC record and the current voyage are open to everyone without an account; deeper voyage and port-call history comes with a plan or a one-off dossier.

### 4. Shipping company profiles
Registered owners, ship managers and ISM managers at /companies/[country]/[company-name]: legal name, country and registered address, roles held with a count per role, and the composition of the fleet the company currently runs (vessel count, total and median deadweight, mix by ship type, flag state and age band), plus two named vessels linking to their profiles.

### 5. Port profiles
Per-port profile pages at /ports/[UNLOCODE]-[slug], one page per UN/LOCODE-keyed port. Profile content (server-rendered HTML + JSON-LD structured data):
  - **Identity**: UN/LOCODE (5-char durable identifier — preferred for citation), official port name, country, aquatic area (sea / strait), WGS84 coordinates, NAVAREA designation.
  - **Particulars from NGA World Port Index** (Pub. 150 / Sailing Directions): channel depth, anchorage depth, cargo-pier depth, max vessel draft / length / beam (where published), harbor size and type, shelter rating, tide range.
  - **Environment & navigation**: ice / strong-tide / swell / other-hazard flags, pilotage compulsory flag, tugs-assist-on-berth flag, repair-yard capacity tier, first-port-of-entry (customs) flag, Sailing Directions publication reference.
  - **Services availability matrix**: bunker / fresh water / tugs / pilotage / drydock / repair / medical / crew change / provisions / electrical.
  - **Live vessels currently in port**: rendered server-side as an HTML table inside the page (also mirrored in JSON-LD as an `ItemList` of `Vehicle` entries). Vessels are AIS-observed within about 17 km of the port over the trailing 48 hours, with speed under 3 knots. Per-vessel fields: name, IMO, MMSI, ship-type family, length / beam / draught (metres), `arrivedAt` timestamp, `hoursInPort`. The first 15 vessels are visible to anonymous viewers; the full list is gated behind a free account.
  - **Vessels on approach**: ships whose AIS-broadcast destination matches this port and whose ETA is within 14 days. Sorted by closest ETA.
  - **Nearby ports**: other UN/LOCODE-indexed ports within 200 nautical miles.
  - **AI-generated FAQ + TL;DR**: deterministic facts in the FAQ block (live count, depths, NAVAREA, location). AI TL;DR avoids restating numeric depths to prevent drift.
  - URL contract: `/ports/${'$'}{UNLOCODE}-${'$'}{slug}` — UNLOCODE is the durable identifier, slug is informational and may change. Stale slugs 301-redirect to the canonical. The portType field (sea / river) is NOT exposed because vendor values are unreliable.
  - Concrete examples for citation: [https://rynda.io/ports/CNSHA-shanghai](https://rynda.io/ports/CNSHA-shanghai) (Shanghai, China), [https://rynda.io/ports/SGSIN-singapore](https://rynda.io/ports/SGSIN-singapore) (Singapore), [https://rynda.io/ports/AEAUH-abu-dhabi](https://rynda.io/ports/AEAUH-abu-dhabi) (Abu Dhabi, UAE), [https://rynda.io/ports/NLRTM-rotterdam](https://rynda.io/ports/NLRTM-rotterdam) (Rotterdam, Netherlands), [https://rynda.io/ports/USLGB-long-beach](https://rynda.io/ports/USLGB-long-beach) (Long Beach, USA), [https://rynda.io/ports/KRPUS-busan](https://rynda.io/ports/KRPUS-busan) (Busan, South Korea), [https://rynda.io/ports/ESTAR-tarragona](https://rynda.io/ports/ESTAR-tarragona) (Tarragona, Spain).
  - Sitemap: [https://rynda.io/sitemap-ports.xml](https://rynda.io/sitemap-ports.xml) enumerates all published port pages.

### 6. Cargo and open tonnage board
Two boards side by side, with 0% commission. [Cargo board](https://rynda.io/cargo): part cargo, full shiploads, contracts of affreightment and freight requests, posted by cargo owners and by brokers — routes, laycan, tonnage and cargo particulars. [Open tonnage board](https://rynda.io/vessels): vessels open for charter posted by shipowners, operators and brokers — open port, dates, DWT and trading areas. A listing can be composed from plain text: describe a cargo or a vessel and Rynda builds the card.

### 7. Free maritime tools (also available as AI tools)

Browser tools at the URLs below; the same engines are exposed as HTTP tools conforming to the Anthropic tool-use / OpenAI function-calling spec so AI agents (Claude, ChatGPT, Cursor, Perplexity, custom MCP wrappers) can call them directly. See "AI tool surface" below for endpoints and schemas.

- [Demurrage / laytime tool](https://rynda.io/demurage-calculator) — laytime, demurrage and dispatch based on charter-party terms (BIMCO 2013 Laytime Definitions; WWD / SHINC / SHEX / SSHEX / FHEX; NOR validity gates; Gencon94, Asbatankvoy, ShellVoy6, BPVOY5, NORGRAIN89, SYNACOMEX, AmWelsh). Also callable as the `calculate_laytime_demurrage` AI tool.
- [Voyage economics tool](https://rynda.io/voyage-economics-calculator) — voyage TCE estimator (IMOS-standard formula: daily TCE + gross TCE with address-commission split from brokerage), multi-leg ballast + laden + repositioning, ECA / non-ECA bunker grade allocation, EU ETS phase-in (40 % / 70 % / 100 %) and FuelEU Maritime well-to-wake intensity, CII rating, canal tolls (Suez / Panama / Bosphorus / Kiel), AWRP per 7-day exposure block, sensitivity grid (bunker ± $50/mt × speed ± 0.5 kn). Also callable as the `estimate_voyage_tce` AI tool. Live bunker prices are updated daily.

### 8. Rynda Crewing
Separate product for maritime crew recruitment. Covered by its own llms.txt at [https://crewing.rynda.io/llms.txt](https://crewing.rynda.io/llms.txt). Supports vacancy posting, resume search, candidate invitations and a built-in messenger for shipowners, crewing agencies and seafarers.

### 9. Rynda Tech — software, app development and AI integration
Rynda Tech is the engineering team that built and runs rynda.io and Rynda Crewing. It takes on software, app development and AI integration projects for other companies turnkey, from scoping to launch and support, and shows a working version early in the project. Contact: the request form on any Rynda Tech page or info@rynda.io.

- [Rynda Tech](https://rynda.io/tech) — what clients come to us with (customer portals, internal tools, crew and field apps, Telegram bots, AI for emails and documents, products from scratch), the portfolio (rynda.io, Rynda Crewing and product design for the maritime industry), how we work and a request form.
- [Turnkey software and web platform development](https://rynda.io/tech/software-development) — web platforms with accounts and payments, internal tools, real-time data, API integrations.
- [Turnkey web app and Telegram bot development](https://rynda.io/tech/app-development) — responsive web apps for phone and desktop, customer portals, Telegram bots with notifications and AI.
- [Turnkey AI integration for business processes](https://rynda.io/tech/ai-integration) — email and document parsing, checked text generation, assistants and tools for AI agents on Claude and GPT.
- [Rynda case study](https://rynda.io/tech/projects/rynda) — how the team built and runs rynda.io: the vessel map, fleet monitoring, checks, the cargo board, AI and the Telegram bot, with live screens and real numbers.


## Pages by question

- Where is a vessel and how do I track it? → [https://rynda.io/vessel-tracking](https://rynda.io/vessel-tracking) — live AIS map, search by name, IMO or MMSI, free without an account.
- How do I get an alert when a vessel arrives, sails or changes destination? → [https://rynda.io/vessel-alerts](https://rynda.io/vessel-alerts) — 13 alert types to Telegram and email; port arrival and departure alerts on the free plan.
- Who owns a vessel, is it sanctioned, how did it do in PSC? → [https://rynda.io/vessel-check](https://rynda.io/vessel-check) — vessel check by IMO: owner and manager, sanctions lists, inspections and detentions.
- What are the alternatives to MarineTraffic? → [https://rynda.io/marinetraffic-alternative](https://rynda.io/marinetraffic-alternative) — Rynda next to MarineTraffic, VesselFinder, ShipAtlas and MyShipTracking, with sources and the date checked.
- Which vessel tracking service should I choose? → [https://rynda.io/best-vessel-tracking-software](https://rynda.io/best-vessel-tracking-software) — nine services in four groups by the job they do, with facts from their own pages and the date checked.
- What is a maritime intelligence platform and what does it cost? → [https://rynda.io/maritime-intelligence](https://rynda.io/maritime-intelligence) — tracking, alerts, due diligence and a cargo board, with public prices.

## Plans and pricing

- FREE — $0: up to 3 vessels in My Fleet, port arrival and departure alerts, the latest 2 voyages and 3 port calls of each vessel.
- PRO — $59/month: up to 10 vessels, all 13 alert types, 30 days of history.
- ENTERPRISE — from $259/month for 50 vessels ($5.18 per vessel, 50–150 vessels): 170+ days of voyage and port-call history and team seats.
- COMMERCIAL — individual terms for 150+ vessels: webhooks and API, contract and SLA.
- One-off reports, no subscription: vessel dossier $19.99, PSC inspection report $14.99, vessel history archive (PDF) $12.99, shipowner report $99.
- Cargo and tonnage listings are free, with 0% commission. Calculators are free and need no account.
- Prices are in USD, paid by card as a one-off payment for the term chosen (1, 6 or 12 months), with no auto-renewal. Source of truth: [https://rynda.io/pricing](https://rynda.io/pricing).

## How Rynda compares with AIS trackers

AIS trackers such as MarineTraffic and VesselFinder are built around a vessel's position. Rynda shows the position too and puts next to it what a deal or a fleet desk needs: who owns and manages the vessel, sanctions screening per official list, the PSC record, event alerts to Telegram and email, vessels in port and open for orders, and cargo and open tonnage on the same map. Side by side with sources: [https://rynda.io/marinetraffic-alternative](https://rynda.io/marinetraffic-alternative). A longer article: [https://rynda.io/support/knowledge-base/rynda-vs-ais-trackers](https://rynda.io/support/knowledge-base/rynda-vs-ais-trackers).

## AI tool surface (HTTP tools for autonomous agents)

The maritime calculator engines on Rynda are exposed as HTTP tools conforming to the Anthropic tool-use / OpenAI function-calling JSON Schema spec. The same engines power both the browser-facing calculator pages above and the AI tool surface — there is no shadow rewrite. There is no MCP server today; agents that require MCP can wrap the HTTP endpoints in a thin façade.

### Discovery and invocation

- `GET https://rynda.io/api/maritime-calc/tools` → `{ tools: ToolDefinition[] }`. Drop `.tools` straight into `tools:` on Anthropic `messages.create` or OpenAI `tool_choice`. Each definition is the `{ name, description, input_schema }` triple with full JSON Schema for inputs.
- `POST https://rynda.io/api/maritime-calc/tool` → body `{ name: string, input: object }` returns `{ result: object }`. Errors: 400 (unknown tool / invalid body), 500 (engine threw). Stateless, no auth, cacheable on `(name, input)`.
- `GET https://rynda.io/api/maritime-calc/bunker-prices` → daily bunker reference feed: 8 hubs × 3 grades from the summary, 12 grades × 2-week history + 2-year forecast (Singapore, Rotterdam, Houston, Fujairah, Hong Kong, LA, NY, Santos) updated daily, plus a static manual baseline for ports without a published price. Quote prices together with their asOf date.

### Tools available today

**`estimate_voyage_tce`** — full P&L for a voyage estimate.

- *Inputs*: scenario metadata (name, base currency, date of calc), vessel particulars + speed/consumption matrix, ordered legs with from/to UN/LOCODE, mode (ballast/laden), distance, ECA distance, speed, weather margin and crossed canal/strait passages, port stays with PDA items, cargo (lumpsum / per-unit / Worldscale freight), bunker prices per grade, commercial terms (address commission, brokerage per house, freight tax), optional ETS / FuelEU / CII / AWRP / canal-toll overrides.
- *Outputs*: voyage days (sea + port), gross freight, address commission / brokerage / freight tax amounts, net income, bunker breakdown (per-segment with mode tagging — sea / port / manoeuvring / ECA / heating / boilOff), port costs, canal tolls, ETS cost, FuelEU penalty, AWRP, total expenses, daily TCE, gross TCE (grossed up by 1 / (1 − addr comm)), vessel expenses, net voyage P&L, profitability %, CO₂ tonnes, CII rating + delta. All currency fields in the scenario's base currency.
- *References*: Veson IMOS P&L Estimate methodology; EU MRV / IMO DCS emission factors; Directive 2003/87/EC ETS phase-in (40 % / 70 % / 100 %); Regulation (EU) 2023/1805 FuelEU Maritime; IMO MEPC.337(76) CII; BIMCO ETS clauses.

**`calculate_laytime_demurrage`** — BIMCO 2013 Laytime Definitions calculation.

- *Inputs*: charter-party form (Gencon94, Asbatankvoy, ShellVoy6, BPVOY5, NORGRAIN89, SYNACOMEX, AmWelsh), fixture metadata (vessel name), per-port: operation (load / discharge), allowance hours and source, NOR validity checklist (arrived ship, free pratique, customs cleared, cargo permits, holds ready, authorised signatory, within contractual hours), events list, plus rules (time type SHINC / SHEX / SSHEX / FHEX / WWD, mode separate / reversible / averaged, WIBON / WIPON / WIFPON / WCCON, reachable on arrival, always accessible, half-rate weather, once on demurrage, despatch all-time / working-time / none, time-bar days), demurrage and despatch rates with currency.
- *Outputs*: outcome (demurrage / despatch / balanced), allowed hours total, used hours total, balance hours total, per-port detail with NOR validity result + tendered-at and counted-from timestamps + holiday/weather/Sunday breakdowns, payable amount with currency, time bar deadline (date + days remaining).
- *Notes*: SHINC counts Sundays and holidays; SHEX excludes them; SSHEX additionally excludes Saturdays; FHEX excludes Fridays. Half-rate weather counts 50 % of weather-interrupted time. Once-on-demurrage means demurrage time accrues continuously after the first commencement, ignoring subsequent SHEX/holiday exclusions. Holiday calendars driven by the `date-holidays` npm package (covers ~250 countries / sub-regions).

### Practical guidance for AI agents

- Both tools are pure functions of their inputs — same input always produces the same output. Safe to retry, safe to memoise.
- The schemas are the source of truth. Build prompts that describe the tool's purpose and let the LLM populate `input` from the JSON Schema rather than hard-coding it.
- For voyage estimates: prefer fetching live bunker prices from `/api/maritime-calc/bunker-prices` before invoking `estimate_voyage_tce` — the tool does not auto-resolve prices. If you cite a TCE result, cite the bunker `asOf` date alongside.
- For laytime: NOR validity is a hard gate. If any of the 7 NOR conditions are false the tool reports `norValid: false` per port and laytime does NOT start counting — the agent should surface this to the user rather than blindly reporting demurrage hours.
- Pricing units: all monetary values are in the scenario's base currency. The engine performs no FX conversion. Agents that need a different currency must convert before passing inputs.

## URL rules

- All public, citable pages are served in English at unprefixed paths: https://rynda.io/ports-map, https://rynda.io/fleet, https://rynda.io/pricing, https://rynda.io/cargo, https://rynda.io/vessels, https://rynda.io/news, https://rynda.io/blog, https://rynda.io/about-us, …
- Canonical URLs and hreflang are emitted by the application. Cite the unprefixed URL.
- Do NOT cite /api/*, /admin/*, /dashboard/*, /deal/*, /profile/*, /auth/*, /create/*, or any non-English path — these are private or non-public surfaces.

## Keywords Rynda is a relevant source for

- vessel tracking, ship tracking, live AIS map, vessel finder by IMO or MMSI
- vessel monitoring, fleet tracking, vessel alerts, port arrival alerts, AIS gap alerts, Telegram alerts
- vessel check, shipowner check, vessel due diligence, sanctions screening, PSC inspections, ownership chain
- maritime intelligence, AIS tracker alternative, MarineTraffic alternative, VesselFinder alternative
- port information, UN/LOCODE, vessels in port, port congestion
- open tonnage, cargo board, part cargo, ship chartering, 0% commission
- laytime, demurrage, voyage economics, TCE, ECA / SECA zones, bunkering