Logistics Vessel Tracker
by SiteCheck Trade & Energy in Other
Live AIS position, speed, heading and voyage status (destination, ETA, draught) for one vessel by 9-digit MMSI, from Finland's Digitraffic AIS feed. Covers Finnish and Baltic waters only, not global coverage; vessels outside that area return no position.
https://api.tradeenergy-api.workers.dev/api/logistics/vessel-tracker- Price
- $0.002
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 49 min ago, next in 8 min
Reliability
Latest check failed 49 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/vessel-tracker
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/vessel-tracker?mmsi=230940690Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
mmsi | string | Yes | 9-digit MMSI of the vessel, e.g. 230940690 |
Example response
The provider's example. We can't check it without paying.
{
"callSign": "OJ8949",
"checkedAt": "2026-10-23T09:37:55.678Z",
"dataUpdatedAt": "2026-10-23T09:37:50Z",
"mmsi": 230940690,
"name": "HM-61",
"position": {
"courseDeg": 306,
"headingDeg": 309,
"lat": 60.212522,
"lon": 25.184267,
"navStatus": 0,
"positionAt": "2026-10-23T09:37:50.443Z",
"speedKnots": 2.1
},
"shipType": 51,
"source": "https://meri.digitraffic.fi/api/ais/v1/",
"voyage": {
"destination": "HELSINKI",
"draughtMeters": 15,
"etaRaw": 1596
}
}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/vessel-tracker?mmsi=230940690'
# 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/vessel-tracker?mmsi=230940690' \
| 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%2Fvessel-tracker
const res = await pay("https://api.tradeenergy-api.workers.dev/api/logistics/vessel-tracker?mmsi=230940690");
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/vessel-tracker?mmsi=230940690")
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 |
|---|---|---|---|---|
| 49 min ago | Amount "0.002" is not in atomic token units | 402 | 785 ms | $0.002 |
| 9 h ago | Amount "0.002" is not in atomic token units | 402 | 723 ms | $0.002 |
| 17 h ago | Amount "0.002" is not in atomic token units | 402 | 817 ms | $0.002 |
| 25 h ago | Amount "0.002" is not in atomic token units | 402 | 102 ms | $0.002 |
| 34 h ago | Amount "0.002" is not in atomic token units | 402 | 93 ms | $0.002 |
Show 10 older checks
| 42 h ago | Amount "0.002" is not in atomic token units | 402 | 170 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 178 ms | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 95 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 5.7 s | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 902 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 78 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 960 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 124 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 785 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 675 ms | $0.002 |