Logistics Seaport Unlocode
by SiteCheck Trade & Energy in Weather & location
UN/LOCODE location lookup by 5-character code (country + place, e.g. FIHEL): name, subdivision, status, port/rail/road/airport functions, IATA code and coordinates. Data is the UN/LOCODE list as mirrored on DataHub (ODC-PDDL), not the UNECE site itself.
https://api.tradeenergy-api.workers.dev/api/logistics/seaport-unlocode- Price
- $0.002
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 8 h ago, next any minute now
Reliability
Latest check failed 8 h 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/seaport-unlocode
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/seaport-unlocode?code=FIHELParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | UN/LOCODE, 5 letters: 2-letter country + 3-character location, e.g. FIHEL, SGSIN |
Example response
The provider's example. We can't check it without paying.
{
"checkedAt": "2026-10-23T09:37:58.254Z",
"code": "FIHEL",
"coordinates": {
"lat": 60.1667,
"lon": 24.9333
},
"country": "FI",
"functions": [
"port",
"road terminal"
],
"iata": null,
"name": "Helsinki",
"source": "https://datahub.io/core/un-locode/r/code-list.csv",
"status": "AS",
"subdivision": "18"
}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/seaport-unlocode?code=FIHEL'
# 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/seaport-unlocode?code=FIHEL' \
| 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%2Fseaport-unlocode
const res = await pay("https://api.tradeenergy-api.workers.dev/api/logistics/seaport-unlocode?code=FIHEL");
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/seaport-unlocode?code=FIHEL")
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 |
|---|---|---|---|---|
| 8 h ago | Amount "0.002" is not in atomic token units | 402 | 128 ms | $0.002 |
| 16 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 | 851 ms | $0.002 |
| 33 h ago | Amount "0.002" is not in atomic token units | 402 | 41 ms | $0.002 |
| 41 h ago | Amount "0.002" is not in atomic token units | 402 | 101 ms | $0.002 |
Show 10 older checks
| 2 days ago | Timed out | - | - | - |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 97 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 47 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 689 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 815 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 1.4 s | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 98 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 120 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 105 ms | $0.002 |
| 5 days ago | Amount "0.002" is not in atomic token units | 402 | 124 ms | $0.002 |