# USCG Maritime Case History Lookup

> USCG Maritime Case History Lookup is a paid API for AI agents from 2s.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Retrieves U.S. Coast Guard Port State Information eXchange (PSIX) case history (boardings, inspections, etc.) for a specific vessel by USCG vessel ID

## Facts

- Endpoint: GET https://2s.io/api/maritime/cases
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/uscg-maritime-case-history-lookup-fb882150
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1KdNISk2LCd6CvE5euGYp

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability uscg-maritime-case-history-lookup-fb882150
```

Example prompt: Pull up the full U.S. Coast Guard PSIX case history for vessel ID 1234567 — I want to see all boardings, inspections, and any enforcement actions on record.

## When to prefer this

Use this endpoint when you need authoritative U.S. Coast Guard enforcement and inspection records for a specific vessel, identified by its USCG vessel ID. Prefer this over general vessel info endpoints when the query is about compliance history, boardings, or port state control actions specifically.

## Known failure modes

- Missing or invalid vesselId returns an error or empty items array
- Vessel ID not found in PSIX returns total=0 and empty items
- USCG PSIX upstream service unavailable causes failed request
- vesselId from wrong system (non-USCG) returns no results

## How this service works

US Coast Guard activity / port-state-control case history for a vessel, by USCG vessel id (from maritime.vessel). Returns cases newest-first with the activity id, start date, type (Boarding, Inspection, Investigation, etc.), and process status. Keyless, public-domain. The compliance/inspection record behind a vessel — use for safety and counterparty due diligence.

## Output

Returns a JSON array of case records for the vessel, each with case type (e.g. Boarding), status (e.g. Closed), start date, activity ID, and status detail. Also includes total count and data source attribution (USCG PSIX, public domain).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "queryParams"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "required": [
      "vesselId"
     ],
     "properties": {
      "vesselId": {
       "type": "string",
       "description": "USCG vessel id (from maritime.vessel)."
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/uscg-maritime-case-history-lookup-fb882150/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 2s.io](https://www.zero.xyz/host/2s.io/llms.txt)