Endpoint

?

aisfleet.com/api/x402/v1/ais/vessels/:mmsi/port-calls

AIS Fleet · not enough data yet · recomputed 13d ago

Get the UN/LOCODE port calls of the last 30 days for a 9-digit MMSI as JSON: arrivals, departures, estimated flags, and the port the vessel is in now. Boundaries not directly observed are flagged estimated, and the response names when capture coverage began.

NOT_RESPONDING
First seen
21d ago
Probes stored
2
Payers
1
On-chain volume
$0.01
No score yet: there are not enough observations. We do not assign a low grade for missing data — a new endpoint would otherwise look dead. The prepay verdict in that case is warn: unknown is a risk, not a clean bill of health.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
20d ago 404 234 ms — — — E_NO_402:404
21d ago 404 87 ms — — — E_NO_402:404

Settlements to this wallet

WhenPayerAmountFacilitatorTransaction
45d ago 0x6a76…8a20 $0.01 not in registry 0x3ac1cb…6cb0

Reference

URLhttps://aisfleet.com/api/x402/v1/ais/vessels/:mmsi/port-calls
Sourcesbazaar
Recipient per catalogue0xa4b5056e8260d49213e64c081b504c8535c14bc4
Price per catalogue0.020000
Machine access/v1/endpoint · /full · badge

Is this your endpoint?

The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.

We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.