ShipFinder AIS Data API · Arazzo Workflow

Plan a port-to-port route, predict ETA and check active tropical cyclones

Version 1.0.0

Native Arazzo workflow over the ShipFinder Global Maritime Data API. Generated by API Evangelist on 2026-08-09; every operationId is verified against openapi/shipfinder-ais-data-api-openapi.yml.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AISMaritime DataVessel TrackingShip TrackingVessel DataHistorical AISGeospatialGISLogisticsSupply ChainWeatherMeteorologyTradeCommoditiesComplianceRiskEvent StreamingWebhookArazzoWorkflows

Provider

shipfinder-ais-data-api

Workflows

voyagePlanAndEta
Plan a port-to-port route, predict ETA and check active tropical cyclones
3 steps inputs: apiKey, endPortCode, mmsi, startPortCode outputs: cyclones
2
eta
3
cyclones

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
arazzo: 1.0.1
info:
  title: Plan a port-to-port route, predict ETA and check active tropical cyclones
  version: 1.0.0
  description: Native Arazzo workflow over the ShipFinder Global Maritime Data API. Generated by API Evangelist on 2026-08-09; every operationId is verified against openapi/shipfinder-ais-data-api-openapi.yml.
  x-realizes-capability-ids:
  - BC-2510.30
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-2510.30
      capability_name: ETA Prediction Management
      spec: shipfinder-ais-data-api-prediction-dataset-api-openapi.yml
      confidence: 0.72
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: meteorologyDatasetApi
  url: ../openapi/shipfinder-ais-data-api-meteorology-dataset-api-openapi.yml
  type: openapi
- name: predictionDatasetApi
  url: ../openapi/shipfinder-ais-data-api-prediction-dataset-api-openapi.yml
  type: openapi
workflows:
- workflowId: voyagePlanAndEta
  summary: Plan a port-to-port route, predict ETA and check active tropical cyclones
  inputs:
    type: object
    required:
    - apiKey
    - startPortCode
    - endPortCode
    - mmsi
    properties:
      apiKey:
        type: string
        description: ShipFinder API key
      startPortCode:
        type: string
        description: Origin UN/LOCODE
      endPortCode:
        type: string
        description: Destination UN/LOCODE
      mmsi:
        type: string
        description: MMSI of the vessel on the voyage
  steps:
  - stepId: route
    operationId: getRoutePlanPortToPort
    parameters:
    - name: key
      in: query
      value: $inputs.apiKey
    - name: start_port_code
      in: query
      value: $inputs.startPortCode
    - name: end_port_code
      in: query
      value: $inputs.endPortCode
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.status == 0
      type: jsonpath
    outputs:
      route: $response.body#/data
  - stepId: eta
    operationId: getETA
    parameters:
    - name: key
      in: query
      value: $inputs.apiKey
    - name: mmsi
      in: query
      value: $inputs.mmsi
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.status == 0
      type: jsonpath
    outputs:
      eta: $response.body#/data
  - stepId: cyclones
    operationId: getCyclonesList
    parameters:
    - name: key
      in: query
      value: $inputs.apiKey
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.status == 0
      type: jsonpath
    outputs:
      cyclones: $response.body#/data
  outputs:
    cyclones: $steps.cyclones.outputs.cyclones

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/voyage-plan-and-eta"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.