MTI API documentation

Transparency scoring for vessels. MTI combines vessel identity, reporting behaviour, voyage activity, sanctions exposure and emissions performance into a single score, plus the five category scores behind it, so you can compare ships before you commit to one.

MTI is a separate product from Insights and from PurpleTRAC, on its own host, with its own authentication. If you already integrate against either of those, nothing carries over except the company you buy it from.

This documentation is a draft

The MTI reference is newly published and the pages around it are still under review by the MTI product team. Endpoint paths, field names and the base URL may change before general availability. Talk to your Pole Star representative before you build against it.

When to use it

You want to	Start at
Score one ship you are about to charter, insure or finance	`GET /vessels/{imo}/scores`
Score a whole portfolio or watchlist in one call	`POST /vessels/scores/batch`
Build a fleet table with filters on flag, type and score	`GET /vessels`
See everything we hold on a ship, including ownership and management	`GET /vessels/{imo}`
Place one ship against its peers	`GET /vessels/score-distribution`

How the API is put together

There is one resource: a vessel, keyed by its IMO number. Everything else is a different view of that vessel, or a different way of asking for several at once.

One key

Every lookup takes a seven digit IMO number. IMO numbers survive a change of name, flag, MMSI or owner, which is why we key on them and not on a vessel name. Nothing in this API is keyed by MMSI or by a Pole Star asset id.

Three access shapes

Shape	Endpoints	Use it when
List	`GET /vessels`	You are browsing or building a table, and you want filtering, sorting and paging
Single	`GET /vessels/{imo}`, `/scores`, `/scores/overall`	You know the ship and want one of three levels of detail
Batch	`POST /vessels/scores/batch`, `/scores/overall/batch`	You hold a list of IMO numbers and want them scored in one round trip

The three single-vessel endpoints return progressively less: the full vessel record, then the scores alone, then the composite score alone. Pick the smallest one that answers your question.

One response envelope

Every response, on every endpoint, is meta plus data.

{
    "meta": {
        "requestId": "266ea41d-adf5-4e12-9a11-9c9a6f12b0a1",
        "requestTimestamp": "2026-09-22T09:14:22Z"
    },
    "data": { }
}

meta always carries requestId and requestTimestamp. On GET /vessels it also carries limit, offset and totalCount. On the batch endpoints it carries requestedCount and returnedCount, and the batch responses add a third top-level key, notFound, listing the IMO numbers we could not resolve.

data is an object on the single endpoints and an array on the list and batch endpoints.

What is in it

Getting Started

Your first call, the three levels of detail, paging a large result set, and screening a portfolio in one request.

Authentication

The OAuth 2.0 client credentials exchange, the mti:api scope, and where the access token goes.

Understanding Scores

The 0 to 5 scale, the five categories behind the composite, and what the API does and does not tell you.

What MTI is not

MTI is decision support. A score reflects the information available when we assessed the vessel. It is not a legal finding, it does not designate a vessel as sanctioned, and it does not establish intent. Read it as a prompt for enhanced due diligence, and keep your own expert judgement in the loop.

The vessel type classification MTI uses to compute peer averages is its own. It does not align with PurpleTRAC's classification, so do not treat the two as equivalent.

Maritime Transparency Index

When to use it#

How the API is put together#

One key#

Three access shapes#

One response envelope#

What is in it#

What MTI is not#