# SiteCheck Trade & Energy – Port Call Schedule

> SiteCheck Trade & Energy – Port Call Schedule is a paid API for AI agents from api.tradeenergy-api.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-29).

Returns recorded daily port calls (vessel arrivals) at a specified port by ship type, derived from AIS data via IMF PortWatch, for up to 30 recent days.

## Facts

- Endpoint: GET https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sitecheck-trade-energy-port-call-schedule-1e5a8895
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KYUofZ6MzQlrfK-m7pd5P

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 sitecheck-trade-energy-port-call-schedule-1e5a8895
```

Example prompt: Pull the last 14 days of port call records for Rotterdam — I want to see how many vessels arrived each day and what ship types they were.

## When to prefer this

Use this endpoint when you need recent historical vessel arrival counts at a specific port, broken down by ship type, based on AIS tracking data. It is ideal for trade flow monitoring, supply chain analysis, port congestion assessment, and energy/commodity trade research. Prefer this over live vessel trackers when you need aggregated daily call counts rather than real-time ship positions, and over forward schedules when you need what actually happened rather than what was planned.

## Known failure modes

- Invalid or unrecognized port name returns an error or empty result
- Days parameter out of range (less than 1 or greater than 30) may return an error or default to 7
- Port with no AIS coverage or sparse data may return incomplete records
- Data lag means very recent days may not yet appear in results
- Network or Cloudflare worker timeout on slow responses

## How this service works

Recorded daily port calls (vessel arrivals) at one port by ship type, from IMF PortWatch (AIS-derived), for the most recent days. These are past calls, not a forward arrival or departure schedule, and the latest date lags real time.

## Output

A list of daily port call records for the specified port, covering up to 30 recent days. Each record includes the date, ship type categories, and the count of vessel arrivals derived from AIS data. Note that the latest date lags real time and data reflects historical arrivals, not a forward schedule.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "port"
     ],
     "properties": {
      "days": {
       "type": "string",
       "description": "1 to 30 (default 7)"
      },
      "port": {
       "type": "string",
       "description": "PortWatch port name, e.g. Rotterdam, Singapore"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sitecheck-trade-energy-port-call-schedule-1e5a8895/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.tradeenergy-api.workers.dev](https://www.zero.xyz/host/api.tradeenergy-api.workers.dev/llms.txt)