vessel-api-python 1.3.1__tar.gz → 2.0.1__tar.gz

vessel_api_python-2.0.1/CHANGELOG.md

@@ -0,0 +1,138 @@
+# Changelog
+
+All notable changes to this package are documented here.
+This project follows [Semantic Versioning](https://semver.org/).
+
+## [2.0.1] - 2026-10-08
+
+Documentation only. No method, parameter or model changed.
+
+### Fixed
+
+- The bundled OpenAPI spec named the satellite fallback parameter `sat`; the
+  API's parameter is `filter.sat`. Descriptions corrected.
+
+### Changed
+
+- README: the satellite fallback note says when it fires (no recent terrestrial
+  position stored); the radius example describes the time window it searches
+  (default 2 hours, at most 4).
+
+## [2.0.0] - 2026-08-16
+
+Vessel ownership, classification and inspection data, and NAVTEX messages, were
+retired from the VesselAPI service on **10 August 2026**. This release removes
+the corresponding client surface and brings the SDK back in line with the API.
+
+Every change below applies to both the sync and async clients.
+
+### Removed (breaking)
+
+These endpoints no longer exist. Calling them returned HTTP 410 from 10 August
+2026 onward; the methods are now gone so the failure surfaces at import or call
+time rather than as a runtime error.
+
+| Removed | Replacement |
+|---|---|
+| `vessels.classification()` | none |
+| `vessels.inspections()` | none |
+| `vessels.inspection_detail()` | none |
+| `vessels.ownership()` | none |
+| `client.navtex` (whole service: `list()`, `list_all()`) | none |
+
+Also removed:
+
+- **Search filters** `filter_class_society` and `filter_owner` on
+  `search.vessels()`. The API began rejecting both with HTTP 400, so any call
+  passing them was already failing.
+- **Vessel fields** `builder`, `class_society`, `owner_name`, `manager_name`.
+- **Models** for the removed endpoints (26 classes), plus the four
+  backwards-compatibility aliases `Classification`, `Inspection`,
+  `InspectionDetail` and `Ownership`: 30 public names in total.
+
+**Migrating from 1.x:** remove calls to the methods above. There is no
+alternative source for that data through this API. Drop `filter_class_society`
+and `filter_owner` from any search call. If you read `owner_name`,
+`manager_name`, `builder` or `class_society` from a vessel, those attributes are
+gone.
+
+### Added
+
+- **Search**: `q` (free-text across name, IMO, MMSI, ENI and callsign) and
+  `filter_eni` on `search.vessels()`.
+- **Repeatable filters.** `filter_flag` and `filter_vessel_type` on
+  `search.vessels()`, and `filter_country`, `filter_port_type`, `filter_size`,
+  `filter_harbor_size` and `filter_harbor_use` on `search.ports()`, now accept
+  `str | list[str]` (exported as `MultiFilter`). A list matches any of the
+  values. Passing a plain string behaves exactly as before.
+- **`filter_sat`** on `vessels.position()`. ⚠️ Satellite lookups draw on a
+  prepaid balance and are charged per call. Omit it to serve stored positions.
+- **`time_from` / `time_to`** on `port_events.by_port()`, `by_ports()`,
+  `by_vessels()` and their iterators.
+- **Vessel fields**: `eni`, `teu`, `vessel_subtype`, `name_ais`,
+  `summer_draught`, `draught_calculated_avg`, `draught_observed_max`,
+  `speed_calculated_avg`, `speed_observed_max`. All are declared by the API and
+  were previously discarded by the models. Each is optional, and how often one
+  is populated varies by field and by vessel.
+- **Search metadata**: `FindVesselsResponse.meta` (`matched_on`, `query`) via
+  the new `VesselSearchMeta` model, and `ResolutionMeta.suggested_id_type`, a
+  hint to retry with the other identifier type when a lookup misses.
+- **Error handling**: `VesselPaymentRequiredError` (402, satellite credits
+  exhausted) and `VesselForbiddenError` (403, key suspended or feature not on
+  your plan), plus `is_payment_required` / `is_forbidden` properties. All errors
+  now expose the API's machine-readable `code` and `error_type`. Branch on
+  those rather than on `message`, which may be reworded.
+
+### Changed (breaking)
+
+- **Parameters the API requires are now required in Python too.** They are
+  keyword-only with no default, so omitting one raises `TypeError` at the call
+  instead of returning HTTP 400 from the server. Previously they defaulted to
+  `None`, which type-checked cleanly and then failed at runtime.
+  - `location.*_bounding_box()`: `lat_min`, `lat_max`, `lon_min`, `lon_max`.
+  - `location.*_radius()`: `latitude`, `longitude`, `radius`.
+  - `search.dgps()`, `search.light_aids()`, `search.modus()`,
+    `search.radio_beacons()`: `filter_name`.
+  - `port_events.by_ports()`: `filter_port_name`.
+    `port_events.by_vessels()`: `filter_vessel_name`.
+  - `vessels.positions()`: `filter_ids`.
+  - The matching `all_*` iterators enforce the same set. 38 methods in total,
+    on both the sync and async clients.
+- **`vessels.positions()` parameter order changed.** `filter_ids` now precedes
+  `filter_id_type`. Both are keyword-only, so callers are unaffected.
+- `search.vessels()` and `search.ports()` are unaffected: the API marks their
+  `filter_name` optional, and it stays optional here.
+- `filter_id_type` is unchanged. The API requires it, but the SDK sends it on
+  every call and it keeps its `"imo"` default.
+- **Iterator signatures are now explicit.** 50 of the `all_*` / `*_all`
+  iterators accepted `**kwargs` and forwarded blindly. They now declare exactly
+  the parameters they support, so mistyped keywords raise `TypeError` instead of
+  being silently ignored, and type checkers and editors can see them. This one
+  is breaking only in a narrow case:
+  - Anyone passing valid keyword arguments is unaffected.
+  - Passing `pagination_next_token` to an iterator is now rejected at the call.
+    It was already broken: the iterator supplies that token itself, so it
+    raised `got multiple values for keyword argument` at first iteration.
+
+**Migrating from 1.x:** any call that relied on the server rejecting a missing
+bound or name now fails at the call site instead. Supply the values listed above.
+
+### Fixed
+
+- **`vessels.all_positions()` could not be time-bounded.** It did not accept
+  `time_from` / `time_to` at all, although `positions()` supported them, so
+  auto-paginating a historical window was impossible without hand-rolling the
+  token loop.
+- **`ports.inbound()` and `ports.inbound_all()` required an ETA window** they
+  should not have. `eta_from` and `eta_to` were mandatory since 1.2.0, although
+  the service treats both as optional and defaults them to now and 72 hours
+  ahead. Both are now optional.
+- The User-Agent reported `1.1.0` regardless of the installed version.
+- Source distributions previously included files beyond the package itself. The
+  sdist is now scoped to the library, README, licence and metadata.
+
+### Attribution
+
+Emissions and casualty data: © European Union. Source: European Maritime Safety
+Agency (EMSA), THETIS-MRV (EU MRV, Regulation (EU) 2015/757) and the European
+Marine Casualty Information Platform (EMCIP). See the README.

{vessel_api_python-1.3.1 → vessel_api_python-2.0.1}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.5
 Name: vessel-api-python
-Version: 1.3.1
-Summary: Python client for the Vessel Tracking API — maritime vessel tracking, port events, emissions, and navigation data.
+Version: 2.0.1
+Summary: Python client for the Vessel Tracking API: maritime vessel tracking, port events, emissions, and nautical infrastructure.
 Project-URL: Documentation, https://vesselapi.com/docs
 Project-URL: Repository, https://github.com/vessel-api/vesselapi-python
 Project-URL: Issues, https://github.com/vessel-api/vesselapi-python/issues
@@ -10,7 +10,7 @@ Author-email: Vessel API <support@vesselapi.com>
 License-Expression: MIT
 License-File: LICENSE
 Keywords: ais,maritime,sdk,tracking,vessel,vesselapi
-Classifier: Development Status :: 7 - Inactive
+Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
@@ -34,25 +34,12 @@ Description-Content-Type: text/markdown
 
 # vesselapi-python
 
-> [!WARNING]
-> **This version is no longer maintained.** Several endpoints wrapped by 1.x
-> were retired from the VesselAPI service on 10 August 2026 and now return
-> HTTP 410. Please upgrade:
->
-> ```bash
-> pip install 'vessel-api-python>=2'
-> ```
->
-> 2.x removes the retired surface, requires the parameters the API requires,
-> and adds unified search, repeatable filters and satellite position fallback.
-> See the CHANGELOG for migration notes.
-
 [![CI](https://github.com/vessel-api/vesselapi-python/actions/workflows/ci.yml/badge.svg?branch=master)](https://github.com/vessel-api/vesselapi-python/actions/workflows/ci.yml)
 [![PyPI](https://img.shields.io/pypi/v/vessel-api-python.svg)](https://pypi.org/project/vessel-api-python/)
 [![Python](https://img.shields.io/pypi/pyversions/vessel-api-python.svg)](https://pypi.org/project/vessel-api-python/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-Python client for the [Vessel Tracking API](https://vesselapi.com) — maritime vessel tracking, port events, emissions, and navigation data.
+Python client for the [Vessel Tracking API](https://vesselapi.com): maritime vessel tracking, port events, emissions, and nautical infrastructure.
 
 **Resources**: [Documentation](https://vesselapi.com/docs) | [API Explorer](https://vesselapi.com/api-reference) | [Dashboard](https://dashboard.vesselapi.com) | [Contact Support](mailto:support@vesselapi.com)
 
@@ -104,15 +91,33 @@ asyncio.run(main())
 
 | Service | Methods | Description |
 |---------|---------|-------------|
-| `vessels` | `get`, `position`, `casualties`, `classification`, `emissions`, `eta`, `inspections`, `inspection_detail`, `ownership`, `positions` | Vessel details, positions, and records |
-| `ports` | `get` | Port lookup by UN/LOCODE |
+| `vessels` | `get`, `position`, `casualties`, `emissions`, `eta`, `positions` | Vessel details, positions, and records |
+| `ports` | `get`, `inbound`, `inbound_all` | Port lookup by UN/LOCODE and inbound vessels |
 | `port_events` | `list`, `by_port`, `by_ports`, `by_vessel`, `last_by_vessel`, `by_vessels` | Vessel arrival/departure events |
 | `emissions` | `list` | EU MRV emissions data |
 | `search` | `vessels`, `ports`, `dgps`, `light_aids`, `modus`, `radio_beacons` | Full-text search across entity types |
 | `location` | `vessels_bounding_box`, `vessels_radius`, `ports_bounding_box`, `ports_radius`, `dgps_bounding_box`, `dgps_radius`, `light_aids_bounding_box`, `light_aids_radius`, `modus_bounding_box`, `modus_radius`, `radio_beacons_bounding_box`, `radio_beacons_radius` | Geo queries by bounding box or radius |
-| `navtex` | `list` | NAVTEX maritime safety messages |
 
-**37 methods total.**
+**33 methods total**, one per API endpoint, plus 28 auto-pagination iterators.
+
+## Required Parameters
+
+Parameters the API requires are keyword-only with no default, so leaving one out
+raises `TypeError` at the call instead of returning HTTP 400 from the server:
+
+```python
+client.location.vessels_radius(latitude=51.9225, longitude=4.47917, radius=10000)
+client.location.vessels_radius(latitude=51.9225)  # TypeError: missing longitude, radius
+```
+
+This covers the geo bounds on every `location` method (`lat_min`, `lat_max`,
+`lon_min`, `lon_max` for bounding boxes; `latitude`, `longitude`, `radius` for
+radius queries), `filter_name` on `search.dgps`, `search.light_aids`,
+`search.modus` and `search.radio_beacons`, `filter_port_name` on
+`port_events.by_ports`, `filter_vessel_name` on `port_events.by_vessels`, and
+`filter_ids` on `vessels.positions`, along with the matching `all_*` iterators.
+`filter_id_type` is required by the API but keeps its `"imo"` default, since the
+SDK always sends it.
 
 ## Vessel Lookup & Location
 
@@ -121,16 +126,48 @@ asyncio.run(main())
 vessel = client.vessels.get("9811000")
 print(f"{vessel.vessel.name} ({vessel.vessel.vessel_type})")
 
-# Get the vessel's latest AIS position.
-pos = client.vessels.position("9811000")
+# Get a vessel's latest stored AIS position. A vessel that exists may have no
+# stored position, which raises VesselNotFoundError rather than returning empty.
+pos = client.vessels.position("232003239", filter_id_type="mmsi")
 print(f"Position: {pos.vessel_position.latitude}, {pos.vessel_position.longitude}")
 
-# Find all vessels within 10 km of Rotterdam.
+# filter_sat=True falls back to satellite AIS when no recent terrestrial position is stored.
+# ⚠️ Satellite lookups draw on a prepaid balance and are charged per call.
+# Omit it unless you need that fallback.
+
+# Find vessels with an AIS position within 10 km of Rotterdam in the last 2 hours
+# (the default time window, at most 4 hours).
 nearby = client.location.vessels_radius(latitude=51.9225, longitude=4.47917, radius=10000)
 for v in nearby.vessels or []:
     print(f"{v.vessel_name} at {v.latitude}, {v.longitude}")
 ```
 
+## Search
+
+`search.vessels` accepts `q`, a unified search across IMO, MMSI, ENI, callsign and
+name. One value can return several vessels, and `_meta.matched_on` maps each result's
+index to the fields it matched on.
+
+```python
+res = client.search.vessels(q="4606770")
+print(res.meta.matched_on)  # {"0": ["eni"]}
+```
+
+Filters the API declares as repeatable take either one value or a list. A list is
+sent as a repeated query parameter, so the values are OR-ed:
+
+```python
+# ?filter.flag=PA&filter.flag=LR&filter.vesselType=Container%20Ship
+client.search.vessels(filter_flag=["PA", "LR"], filter_vessel_type="Container Ship")
+
+client.search.ports(filter_country=["NL", "BE"], filter_size=["LARGE", "MEDIUM"])
+```
+
+These are `filter_flag` and `filter_vessel_type` on `search.vessels`;
+`filter_country`, `filter_port_type`, `filter_size`, `filter_harbor_size` and
+`filter_harbor_use` on `search.ports`; and `filter_ids` on `vessels.positions`,
+which also accepts the comma-separated single-string form.
+
 ## Error Handling
 
 All methods raise specific exception types on non-2xx responses:
@@ -144,7 +181,7 @@ except VesselAPIError as err:
     if err.is_not_found:
         print("Port not found")
     elif err.is_rate_limited:
-        print("Rate limited — back off")
+        print("Rate limited, backing off")
     elif err.is_auth_error:
         print("Check API key")
     print(err.status_code, err.message)
@@ -163,8 +200,14 @@ for vessel in client.search.all_vessels(filter_vessel_type="Tanker"):
 async for vessel in client.search.all_vessels(filter_vessel_type="Tanker"):
     print(vessel.name)
 
-# Collect a bounded set at once
+# Collect every match at once. pagination_limit is the page size, not a total:
+# .collect() walks to the end, so this is one request per page until exhausted.
 vessels = client.search.all_vessels(filter_vessel_type="Tanker", pagination_limit=50).collect()
+
+# To take a fixed number, stop the iterator yourself.
+from itertools import islice
+
+first_50 = list(islice(client.search.all_vessels(filter_vessel_type="Tanker"), 50))
 ```
 
 ## Configuration
@@ -183,15 +226,24 @@ Retries use exponential backoff with jitter on 429 and 5xx responses. The `Retry
 
 ## Documentation
 
-- [API Documentation](https://vesselapi.com/docs) — endpoint guides, request/response schemas, and usage examples
-- [API Explorer](https://vesselapi.com/api-reference) — interactive API reference
-- [Dashboard](https://dashboard.vesselapi.com) — manage API keys and monitor usage
+- [API Documentation](https://vesselapi.com/docs): endpoint guides, request/response schemas, and usage examples
+- [API Explorer](https://vesselapi.com/api-reference): interactive API reference
+- [Dashboard](https://dashboard.vesselapi.com): manage API keys and monitor usage
 
 ## Contributing & Support
 
 Found a bug, have a feature request, or need help? You're welcome to [open an issue](https://github.com/vessel-api/vesselapi-python/issues). For API-level bugs and feature requests, please use the [main VesselAPI repository](https://github.com/vessel-api/VesselApi/issues).
 
-For security vulnerabilities, **do not** open a public issue — email security@vesselapi.com instead. See [SECURITY.md](SECURITY.md).
+For security vulnerabilities, **do not** open a public issue. Email security@vesselapi.com instead. See [SECURITY.md](SECURITY.md).
+
+## Data Sources & Attribution
+
+Emissions and casualty data: © European Union. Source: European Maritime Safety Agency
+(EMSA): THETIS-MRV (EU MRV, Regulation (EU) 2015/757) and the European Marine Casualty
+Information Platform (EMCIP). Reused under the European Commission reuse notice
+(Commission Decision 2011/833/EU), which authorises reuse for commercial and
+non-commercial purposes with acknowledgement of the source. Data may be transformed and
+combined; EMSA does not endorse this service.
 
 ## License
 

{vessel_api_python-1.3.1 → vessel_api_python-2.0.1}/README.md

@@ -1,24 +1,11 @@
 # vesselapi-python
 
-> [!WARNING]
-> **This version is no longer maintained.** Several endpoints wrapped by 1.x
-> were retired from the VesselAPI service on 10 August 2026 and now return
-> HTTP 410. Please upgrade:
->
-> ```bash
-> pip install 'vessel-api-python>=2'
-> ```
->
-> 2.x removes the retired surface, requires the parameters the API requires,
-> and adds unified search, repeatable filters and satellite position fallback.
-> See the CHANGELOG for migration notes.
-
 [![CI](https://github.com/vessel-api/vesselapi-python/actions/workflows/ci.yml/badge.svg?branch=master)](https://github.com/vessel-api/vesselapi-python/actions/workflows/ci.yml)
 [![PyPI](https://img.shields.io/pypi/v/vessel-api-python.svg)](https://pypi.org/project/vessel-api-python/)
 [![Python](https://img.shields.io/pypi/pyversions/vessel-api-python.svg)](https://pypi.org/project/vessel-api-python/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 
-Python client for the [Vessel Tracking API](https://vesselapi.com) — maritime vessel tracking, port events, emissions, and navigation data.
+Python client for the [Vessel Tracking API](https://vesselapi.com): maritime vessel tracking, port events, emissions, and nautical infrastructure.
 
 **Resources**: [Documentation](https://vesselapi.com/docs) | [API Explorer](https://vesselapi.com/api-reference) | [Dashboard](https://dashboard.vesselapi.com) | [Contact Support](mailto:support@vesselapi.com)
 
@@ -70,15 +57,33 @@ asyncio.run(main())
 
 | Service | Methods | Description |
 |---------|---------|-------------|
-| `vessels` | `get`, `position`, `casualties`, `classification`, `emissions`, `eta`, `inspections`, `inspection_detail`, `ownership`, `positions` | Vessel details, positions, and records |
-| `ports` | `get` | Port lookup by UN/LOCODE |
+| `vessels` | `get`, `position`, `casualties`, `emissions`, `eta`, `positions` | Vessel details, positions, and records |
+| `ports` | `get`, `inbound`, `inbound_all` | Port lookup by UN/LOCODE and inbound vessels |
 | `port_events` | `list`, `by_port`, `by_ports`, `by_vessel`, `last_by_vessel`, `by_vessels` | Vessel arrival/departure events |
 | `emissions` | `list` | EU MRV emissions data |
 | `search` | `vessels`, `ports`, `dgps`, `light_aids`, `modus`, `radio_beacons` | Full-text search across entity types |
 | `location` | `vessels_bounding_box`, `vessels_radius`, `ports_bounding_box`, `ports_radius`, `dgps_bounding_box`, `dgps_radius`, `light_aids_bounding_box`, `light_aids_radius`, `modus_bounding_box`, `modus_radius`, `radio_beacons_bounding_box`, `radio_beacons_radius` | Geo queries by bounding box or radius |
-| `navtex` | `list` | NAVTEX maritime safety messages |
 
-**37 methods total.**
+**33 methods total**, one per API endpoint, plus 28 auto-pagination iterators.
+
+## Required Parameters
+
+Parameters the API requires are keyword-only with no default, so leaving one out
+raises `TypeError` at the call instead of returning HTTP 400 from the server:
+
+```python
+client.location.vessels_radius(latitude=51.9225, longitude=4.47917, radius=10000)
+client.location.vessels_radius(latitude=51.9225)  # TypeError: missing longitude, radius
+```
+
+This covers the geo bounds on every `location` method (`lat_min`, `lat_max`,
+`lon_min`, `lon_max` for bounding boxes; `latitude`, `longitude`, `radius` for
+radius queries), `filter_name` on `search.dgps`, `search.light_aids`,
+`search.modus` and `search.radio_beacons`, `filter_port_name` on
+`port_events.by_ports`, `filter_vessel_name` on `port_events.by_vessels`, and
+`filter_ids` on `vessels.positions`, along with the matching `all_*` iterators.
+`filter_id_type` is required by the API but keeps its `"imo"` default, since the
+SDK always sends it.
 
 ## Vessel Lookup & Location
 
@@ -87,16 +92,48 @@ asyncio.run(main())
 vessel = client.vessels.get("9811000")
 print(f"{vessel.vessel.name} ({vessel.vessel.vessel_type})")
 
-# Get the vessel's latest AIS position.
-pos = client.vessels.position("9811000")
+# Get a vessel's latest stored AIS position. A vessel that exists may have no
+# stored position, which raises VesselNotFoundError rather than returning empty.
+pos = client.vessels.position("232003239", filter_id_type="mmsi")
 print(f"Position: {pos.vessel_position.latitude}, {pos.vessel_position.longitude}")
 
-# Find all vessels within 10 km of Rotterdam.
+# filter_sat=True falls back to satellite AIS when no recent terrestrial position is stored.
+# ⚠️ Satellite lookups draw on a prepaid balance and are charged per call.
+# Omit it unless you need that fallback.
+
+# Find vessels with an AIS position within 10 km of Rotterdam in the last 2 hours
+# (the default time window, at most 4 hours).
 nearby = client.location.vessels_radius(latitude=51.9225, longitude=4.47917, radius=10000)
 for v in nearby.vessels or []:
     print(f"{v.vessel_name} at {v.latitude}, {v.longitude}")
 ```
 
+## Search
+
+`search.vessels` accepts `q`, a unified search across IMO, MMSI, ENI, callsign and
+name. One value can return several vessels, and `_meta.matched_on` maps each result's
+index to the fields it matched on.
+
+```python
+res = client.search.vessels(q="4606770")
+print(res.meta.matched_on)  # {"0": ["eni"]}
+```
+
+Filters the API declares as repeatable take either one value or a list. A list is
+sent as a repeated query parameter, so the values are OR-ed:
+
+```python
+# ?filter.flag=PA&filter.flag=LR&filter.vesselType=Container%20Ship
+client.search.vessels(filter_flag=["PA", "LR"], filter_vessel_type="Container Ship")
+
+client.search.ports(filter_country=["NL", "BE"], filter_size=["LARGE", "MEDIUM"])
+```
+
+These are `filter_flag` and `filter_vessel_type` on `search.vessels`;
+`filter_country`, `filter_port_type`, `filter_size`, `filter_harbor_size` and
+`filter_harbor_use` on `search.ports`; and `filter_ids` on `vessels.positions`,
+which also accepts the comma-separated single-string form.
+
 ## Error Handling
 
 All methods raise specific exception types on non-2xx responses:
@@ -110,7 +147,7 @@ except VesselAPIError as err:
     if err.is_not_found:
         print("Port not found")
     elif err.is_rate_limited:
-        print("Rate limited — back off")
+        print("Rate limited, backing off")
     elif err.is_auth_error:
         print("Check API key")
     print(err.status_code, err.message)
@@ -129,8 +166,14 @@ for vessel in client.search.all_vessels(filter_vessel_type="Tanker"):
 async for vessel in client.search.all_vessels(filter_vessel_type="Tanker"):
     print(vessel.name)
 
-# Collect a bounded set at once
+# Collect every match at once. pagination_limit is the page size, not a total:
+# .collect() walks to the end, so this is one request per page until exhausted.
 vessels = client.search.all_vessels(filter_vessel_type="Tanker", pagination_limit=50).collect()
+
+# To take a fixed number, stop the iterator yourself.
+from itertools import islice
+
+first_50 = list(islice(client.search.all_vessels(filter_vessel_type="Tanker"), 50))
 ```
 
 ## Configuration
@@ -149,15 +192,24 @@ Retries use exponential backoff with jitter on 429 and 5xx responses. The `Retry
 
 ## Documentation
 
-- [API Documentation](https://vesselapi.com/docs) — endpoint guides, request/response schemas, and usage examples
-- [API Explorer](https://vesselapi.com/api-reference) — interactive API reference
-- [Dashboard](https://dashboard.vesselapi.com) — manage API keys and monitor usage
+- [API Documentation](https://vesselapi.com/docs): endpoint guides, request/response schemas, and usage examples
+- [API Explorer](https://vesselapi.com/api-reference): interactive API reference
+- [Dashboard](https://dashboard.vesselapi.com): manage API keys and monitor usage
 
 ## Contributing & Support
 
 Found a bug, have a feature request, or need help? You're welcome to [open an issue](https://github.com/vessel-api/vesselapi-python/issues). For API-level bugs and feature requests, please use the [main VesselAPI repository](https://github.com/vessel-api/VesselApi/issues).
 
-For security vulnerabilities, **do not** open a public issue — email security@vesselapi.com instead. See [SECURITY.md](SECURITY.md).
+For security vulnerabilities, **do not** open a public issue. Email security@vesselapi.com instead. See [SECURITY.md](SECURITY.md).
+
+## Data Sources & Attribution
+
+Emissions and casualty data: © European Union. Source: European Maritime Safety Agency
+(EMSA): THETIS-MRV (EU MRV, Regulation (EU) 2015/757) and the European Marine Casualty
+Information Platform (EMCIP). Reused under the European Commission reuse notice
+(Commission Decision 2011/833/EU), which authorises reuse for commercial and
+non-commercial purposes with acknowledgement of the source. Data may be transformed and
+combined; EMSA does not endorse this service.
 
 ## License
 

{vessel_api_python-1.3.1 → vessel_api_python-2.0.1}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vessel-api-python"
-version = "1.3.1"
-description = "Python client for the Vessel Tracking API — maritime vessel tracking, port events, emissions, and navigation data."
+version = "2.0.1"
+description = "Python client for the Vessel Tracking API: maritime vessel tracking, port events, emissions, and nautical infrastructure."
 readme = "README.md"
 requires-python = ">=3.9"
 license = "MIT"
@@ -14,7 +14,7 @@ authors = [
 ]
 keywords = ["vesselapi", "maritime", "vessel", "tracking", "ais", "sdk"]
 classifiers = [
-    "Development Status :: 7 - Inactive",
+    "Development Status :: 5 - Production/Stable",
     "Intended Audience :: Developers",
     "License :: OSI Approved :: MIT License",
     "Programming Language :: Python :: 3",
@@ -49,6 +49,19 @@ Changelog = "https://github.com/vessel-api/vesselapi-python/releases"
 [tool.hatch.build.targets.wheel]
 packages = ["src/vessel_api_python"]
 
+# Scope the sdist explicitly. Hatchling's default is "everything not gitignored",
+# which pulls in the specification, the smoke tests and the CI workflows. Keep
+# this list to what a consumer of the package actually needs.
+[tool.hatch.build.targets.sdist]
+include = [
+  "src/vessel_api_python",
+  "README.md",
+  "CHANGELOG.md",
+  "LICENSE",
+  "SECURITY.md",
+  "pyproject.toml",
+]
+
 [tool.ruff]
 target-version = "py39"
 line-length = 120
@@ -58,7 +71,12 @@ select = ["E", "F", "I", "W", "UP", "B", "SIM"]
 ignore = ["E501"]  # Line length handled by formatter
 
 [tool.mypy]
-python_version = "3.9"
+# 3.10 is the lowest version current mypy accepts. The package still supports
+# 3.9 (see requires-python): that floor is enforced by ruff's target-version
+# below, which rejects 3.10-only idioms, and verified by the 3.9 job in the CI
+# matrix, which runs the full test suite. Setting 3.9 here is silently ignored
+# by mypy, which then checks against whatever interpreter it happens to run on.
+python_version = "3.10"
 strict = true
 warn_return_any = true
 warn_unused_configs = true