Free AIS feeds (aisstream.io, AISHub): what it returns, and whether it works in Clay

Free AIS feeds (aisstream.io, AISHub) is not available in Clay. It is best for Content demo, Monitoring. Pricing: Free. Access: aisstream.io: free API key; 3 subscribed connections per account and 3 per IP; subscription must arrive within 3 seconds; no SLA, no replay; messages dropped if not consumed; per-user bandwidth limits from September 2026. AISHub: free, but only for members who run their own AIS receiver and feed it to AISHub (station with 10 or more vessels, 90 percent uptime); 1 request per minute; commercial use allowed with credit 'Data: AISHub contributors'; raw data may not be redistributed..

Data domains: Transport, Locations, Signals.

What does Free AIS feeds (aisstream.io, AISHub) return?

Official fields: aisstream PositionReport MessageID; RepeatIndicator; UserID (MMSI); Valid; NavigationalStatus; RateOfTurn; Sog; Cog; TrueHeading; Longitude; Latitude; PositionAccuracy; Timestamp; SpecialManoeuvreIndicator; Raim; plus MetaData MMSI, ShipName, Latitude, Longitude; ShipStaticData message type carries the AIS static fields (schema in aisstream's models repo). AISHub vessel record MMSI; TIME (TSTAMP in CSV and XML); LONGITUDE; LATITUDE; COG; SOG; HEADING; ROT; NAVSTAT; IMO; NAME; CALLSIGN; TYPE; A; B; C; D; DRAUGHT; DEST; ETA.

What can you derive from it?

1. Live presence in a polygon: vessels inside a port, berth or anchorage right now. 2. Dwell time: time between entering and leaving a berth polygon, a turnaround proxy. 3. Own port-call counter: build arrival and departure events from position streams without paying for an events API. 4. Prototype validation: test a vessel-based trigger before buying Kpler or Spire.

How would a GTM team use it?

1. Revenue trigger: stream positions for a client's port bounding box and alert on first-time visitors by MMSI. 2. Competitive watch: watch a competitor's fleet MMSIs for route changes. 3. Market map: collect static data (NAME, TYPE, dimensions) for every vessel seen in a region over a month. 4. Diligence: check whether a target's vessels actually operate where claimed over a few weeks of streaming.

What are the caveats?

Not a native Clay integration as of 2026-10-17 (checked against Clay's integrations catalog). Can be called through Clay's HTTP API column where an API exists. Terrestrial receivers only, so coverage is coastal and patchy; no satellite AIS; no history or replay, you must store the stream yourself. Volunteer-sourced data with no accuracy guarantee and not for navigation. DEST and ETA are crew-entered. Positions prove presence, not cargo or revenue.