Logistics Port Call Schedule
by SiteCheck Trade & Energy in Other
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.
https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule- Price
- $0.002
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 16 min ago, next in 41 min
Reliability
Latest check failed 16 min ago: Amount "0.002" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule
Each call costs $0.002 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule?days=5&port=RotterdamParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
days | string | No | 1 to 30 (default 7) |
port | string | Yes | PortWatch port name, e.g. Rotterdam, Singapore |
Example response
The listing has no example response.
Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.002.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule?days=5&port=Rotterdam'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule?days=5&port=Rotterdam' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.tradeenergy-api.workers.dev%2Fapi%2Flogistics%2Fport-call-schedule
const res = await pay("https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule?days=5&port=Rotterdam");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.tradeenergy-api.workers.dev/api/logistics/port-call-schedule?days=5&port=Rotterdam")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 16 min ago | Amount "0.002" is not in atomic token units | 402 | 738 ms | $0.002 |
| 9 h ago | Amount "0.002" is not in atomic token units | 402 | 69 ms | $0.002 |
| 17 h ago | Amount "0.002" is not in atomic token units | 402 | 1.8 s | $0.002 |
| 25 h ago | Amount "0.002" is not in atomic token units | 402 | 974 ms | $0.002 |
| 33 h ago | Amount "0.002" is not in atomic token units | 402 | 96 ms | $0.002 |
Show 10 older checks
| 41 h ago | Amount "0.002" is not in atomic token units | 402 | 125 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 111 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 923 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 40 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 38 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 91 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 40 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 802 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 38 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 104 ms | $0.002 |