How transparency-everywhere/ais-api works
AIS API is a discontinued vessel-position scraper/API. Clients request a vessel’s latest position, vessels in a port, an area, or near coordinates; the server dispatches to the corresponding scraper, maps results where applicable, and returns them. The combined position lookup compares MarineTraffic data with a VesselFinder fallback, which currently always reports an error. README documents discontinuation but no further product capabilities; scraper wiring is based on the sampled source.
Main entry points: api.js Position & Port API · server.js HTTP Server · area.js Area & Nearby Search · puppeteer.js Response Scraper
Components 13
HTTP API
- App Entry
index.js - HTTP Server
server.js
Position Lookup
- Position & Port API
api.js - VesselFinder Stub
api.js - MarineTraffic Position
api.js - Latest Position
api.js
Vessel Search
- Port Vessel Search
api.js - Area & Nearby Search
area.js - Search Query Builder
area.js - Vessel Result Mapping
area.js
Browser Scraping
- Response Scraper
lib/puppeteer.js
Other components
- API Client
- MarineTraffic
Connections 16
- API Client → HTTP Server: HTTP requests
- App Entry → HTTP Server: starts
- HTTP Server → Position & Port API: dispatches position and port
- HTTP Server → Area & Nearby Search: dispatches area and nearby
- Position & Port API → VesselFinder Stub: checks fallback
- Position & Port API → MarineTraffic Position: checks position
- Position & Port API → Latest Position: compares results
- MarineTraffic Position → MarineTraffic: requests position data
- Position & Port API → Port Vessel Search: searches port
- Port Vessel Search → MarineTraffic: requests port data
- Area & Nearby Search → Search Query Builder: builds search
- Area & Nearby Search → Vessel Result Mapping: maps results
- Search Query Builder → Response Scraper: fetches response
- Response Scraper → MarineTraffic: loads reports
- MarineTraffic → Response Scraper: returns JSON
- HTTP Server → API Client: sends results