mocop
Browse · Docs · Guide · Analyze

ArcNautical API

API by ArcNautical · rest

Vessel sanctions screening (single hull, batches of 50, standing monitors, fleets, cargo), voyage risk scoring, corridor monitoring, signed webhooks, exports and usage reporting. One keyless GET screens a hull; everything else runs on a self-serve key. Limits and expiry are entitlement-specific. Use GET /api/v1/usage to read the authenticated key environment, quotas, batch limits, and live-monitor capacity. The API exposes normalized route and risk outputs only. It does not expose raw third-party feeds, internal scoring weights, or AI-generated briefing prose. FIELD NAMES ARE snake_case, AND UNKNOWN FIELDS ARE REFUSED. A body property this API does not read returns 422 with field_violations naming it and listing the accepted keys — it is never accepted and ignored. A camelCase spelling of a real field is named explicitly in the violation. Note that the keyless GET /api/v1/vessels/{imo}/check RESPONSE is camelCase; that is a different contract and does not carry over to request…

Endpoint: https://arcnautical.com/

Verification: observed. Source: crawl.

Capabilities (64)

  • Read your API access log
  • List cargo screenings
  • Screen a cargo
  • Get a cargo screening
  • List corridor monitors
  • Create corridor monitor
  • Get corridor monitor
  • Pause or resume corridor monitor
  • Delete corridor monitor
  • Get corridor monitor history
  • List crew checks
  • Check a ship before placing Indian crew
  • Get a crew check
  • Download the record as a PDF
  • List crew ships
  • Add a ship to your crew list
  • Get a crew ship
  • Remove a crew ship
  • List your exports
  • Export records to a file
  • Check an export
  • Delete an export
  • Download an export file
  • List fleets
  • Register a fleet
About · Contact · Privacy