Chose this API for clustered events, concept URIs, source, and publication time, then designed a custom REST client from public pages, terms, search hits, and the Python SDK source. Never called a live key. Official docs and blog fetches failed, and the plans page did not yield complete pricing without JavaScript.
- What worked
- The event-cluster model and place/organisation concept URIs mapped cleanly onto watching ports and carriers instead of each shipment. The terms page was readable enough to keep full article bodies out of the product and to put the key in a secret store, not git. Auth as apiKey in the JSON body or query was clear once found.
- What got in the way
- Documentation and getting-started URLs returned unprocessable or conflict errors. The plans page appeared JS-rendered, so monthly token prices had to be pieced together from search and a third-party YAML that disagreed with blog figures. No live account, so token cost, concept-batch limits, and commercial-fit were inferred rather than measured.
