Logistics Imo Vessel Dossier
by SiteCheck Trade & Energy in Other
Ship particulars by IMO number: name, type, flag, MMSI, call sign, year built, gross tonnage, length and beam, current draught and navigation status from VesselFinder's public page, plus deadweight, builder, engine, owner, manager and class society (when listed) from BalticShipping's public vessel register, with that record's last update date. Owner and class data can be years old.
https://api.tradeenergy-api.workers.dev/api/logistics/imo-vessel-dossier- Price
- $0.002
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 5 h ago, next any minute now
Reliability
Latest check failed 5 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/imo-vessel-dossier
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/imo-vessel-dossier?imo=9321483Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
imo | string | Yes | 7-digit IMO ship number, e.g. 9321483 |
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/imo-vessel-dossier?imo=9321483'
# 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/imo-vessel-dossier?imo=9321483' \
| 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%2Fimo-vessel-dossier
const res = await pay("https://api.tradeenergy-api.workers.dev/api/logistics/imo-vessel-dossier?imo=9321483");
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/imo-vessel-dossier?imo=9321483")
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 |
|---|---|---|---|---|
| 5 h ago | Amount "0.002" is not in atomic token units | 402 | 490 ms | $0.002 |
| 13 h ago | Amount "0.002" is not in atomic token units | 402 | 563 ms | $0.002 |
| 21 h ago | Amount "0.002" is not in atomic token units | 402 | 129 ms | $0.002 |
| 29 h ago | Amount "0.002" is not in atomic token units | 402 | 97 ms | $0.002 |
| 37 h ago | Amount "0.002" is not in atomic token units | 402 | 935 ms | $0.002 |
Show 10 older checks
| 45 h ago | Amount "0.002" is not in atomic token units | 402 | 1.1 s | $0.002 |
| 2 days ago | Amount "0.002" is not in atomic token units | 402 | 140 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 115 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 682 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 96 ms | $0.002 |
| 3 days ago | Amount "0.002" is not in atomic token units | 402 | 97 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 41 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 129 ms | $0.002 |
| 4 days ago | Amount "0.002" is not in atomic token units | 402 | 132 ms | $0.002 |
| 5 days ago | Amount "0.002" is not in atomic token units | 402 | 108 ms | $0.002 |