USCG PSIX Vessel Incident Scraper
Pricing
from $19.00 / 1,000 result items
USCG PSIX Vessel Incident Scraper
Scrapes USCG PSIX vessel incident reports by vessel name and returns each incident as a flat row with date, location, nature of the case, and vessel details. Export to CSV, JSON, Excel, or XML.
Pricing
from $19.00 / 1,000 result items
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
6 days ago
Last modified
Categories
Share
USCG PSIX Vessel Incident Scraper
Scrape vessel incident reports from the USCG PSIX database by vessel name, up to a million per run. Every incident comes with its date, location, nature, and involved parties. No API key or registration. Export to CSV, JSON, Excel, or XML.
The Coast Guard's Port State Information Exchange (PSIX) holds the official record of marine incidents, pollution cases, and safety violations for U.S. vessels, but there is no bulk download and the web interface forces you to search one vessel at a time. This Actor reads the public PSIX vessel search, collects every incident for the names you supply, and returns them in a single flat dataset you can filter and analyze offline.
| Who uses it | What they scrape USCG PSIX for |
|---|---|
| Maritime safety officers | Reviewing a fleet's incident history before a port call or audit. |
| Marine insurers | Checking a vessel's casualty and pollution record to price a policy. |
| Journalists and researchers | Investigating safety patterns across a class of vessels or a shipping company. |
| Maritime lawyers | Gathering evidence of prior incidents for a liability or injury case. |
What it does
This Actor collects USCG PSIX vessel incident reports by vessel name and returns each incident as a flat row.
- š Vessel name search: supply one or more vessel names and the Actor fetches every incident PSIX has on file.
- š Flat incident rows: each row is one incident with its date, location, nature of the case, and vessel details, ready for a spreadsheet.
- āļø Configurable limit: set a ceiling from 1 to 1,000,000 incidents per run so you control the scope and the runtime.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with USCG PSIX data
š³ļø Pre-charter due diligence.
A ship broker runs a list of candidate vessels through the Actor and reviews each one's incident history before recommending a charter to a client.
š Fleet risk scoring.
A marine insurer scrapes the incident records for every vessel in an insured fleet, then scores each one by frequency and severity of past casualties to adjust premiums.
š° Investigative reporting.
A journalist collects all pollution incidents for tankers calling at a specific port over five years and cross-references the operators to uncover repeat offenders.
āļø Litigation support.
A maritime attorney scrapes a vessel's full PSIX history to establish a pattern of negligence in a personal injury lawsuit.
Why choose this scraper
| What you get | |
|---|---|
| Official source | Data comes directly from the U.S. Coast Guard's PSIX database, the authoritative record for U.S. flagged vessels. |
| No API key | Reads the public search interface. No registration, no OAuth, no rate-limit headaches. |
| Bulk collection | Feed it a list of vessel names and get all their incidents in one dataset instead of clicking through pages manually. |
| Fixed schema | Every incident arrives in the same flat structure so you can merge runs and compare vessels without cleaning. |
How it compares
No other Store actor targets USCG PSIX the same way, so the honest comparison is with the alternatives teams actually weigh.
| USCG PSIX Vessel Incident Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When USCG PSIX changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with one or more vessel names and set a maximum number of incidents to collect per run. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.021 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $2.10 |
| 1,000 results | $21.00 |
| 10,000 results | $210.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the USCG PSIX Vessel Incident Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to USCG PSIX through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results for a vessel I know has incidents?
Check the spelling of the vessel name. PSIX search is exact; try a partial name or a shorter version. Also confirm the vessel is U.S. flagged or has been in U.S. waters, as PSIX primarily covers those.
The Actor stopped before collecting all the incidents I expected.
Check the 'Maximum incidents' setting in your input. The Actor stops when it reaches that number across all vessel names. Increase the limit and rerun.
I am getting a timeout or the run is taking too long.
Reduce the number of vessel names or lower the maximum incidents limit. If you are scraping a vessel with thousands of incidents, try breaking the work into smaller runs.
Some incident fields are empty in my dataset.
PSIX does not always populate every field for every incident. Empty fields mean the Coast Guard did not record that piece of information for that particular case.
The Actor returns incidents for a different vessel with a similar name.
PSIX search matches substrings. If you search for 'Liberty' you may get 'Liberty Star' and 'Liberty Belle'. Use the most specific name you have and filter the dataset afterward if needed.
FAQ
| Question | Answer |
|---|---|
| What is the USCG PSIX database? | The Port State Information Exchange is the U.S. Coast Guard's public database of marine safety incidents, pollution cases, and enforcement actions involving U.S. flagged vessels and foreign vessels in U.S. waters. |
| Do I need a Coast Guard account or API key to use this Actor? | No. The Actor reads the public PSIX vessel search web interface, so no login, registration, or API key is required. |
| Can I search by something other than vessel name, like an official number or a date range? | The current version accepts vessel names only. If you need to search by official number, hull ID, or date range, you can request that feature through the Apify issue tracker. |
| How many vessel names can I feed into one run? | You can supply as many names as you want. The Actor processes them sequentially and stops when it hits the maximum incidents you set. |
| What information does each incident row contain? | Each row includes the incident date, location, nature of the case (e.g., pollution, casualty, violation), vessel name, and any involved parties as returned by PSIX. |
| Does this Actor scrape historical incidents or only recent ones? | It returns whatever incidents PSIX holds for the vessel, which can span many years. There is no date filter built in; the Actor collects the full record. |
| Can I export the results to Excel? | Yes. Apify supports exports to CSV, JSON, Excel, and XML from the dataset tab after the run finishes. |
| Is this Actor suitable for scraping the entire PSIX database? | It is designed for targeted vessel searches. Scraping the entire database would require iterating over every possible vessel name, which is not practical with this tool. |
| What happens if I enter a vessel name that does not exist in PSIX? | The Actor will return zero incidents for that name and move on to the next one in your list. It will not fail or stop the run. |
| How long does a typical run take? | It depends on the number of vessels and the incidents each one has. A single vessel with a few incidents takes seconds; a large list with thousands of incidents will take longer. |
Related actors
Browse the full ParseForge collection for more scrapers.
š Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
ā ļø Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by United States Coast Guard. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
