Voyager Portal

Voyager Portal is an AI-powered voyage and demurrage management platform for bulk commodity charterers, traders, brokers, and manufacturers, streamlining maritime shipping workflows from pre-fixture planning through post-fixture claim resolution. The platform provides AI-driven demurrage claims management and laytime calculations, cargo allocation, AIS vessel tracking, ETA tracking, noon reporting, and analytics, and exposes a documented public REST API for managing voyages, cargoes, claims, SOFs, vessels, ports, and workflows, plus outbound webhooks.

Voyager Portal is listed with 1 API on the APIs.io network. Tagged areas include Company, Maritime, Shipping, Logistics, and Demurrage.

The Voyager Portal catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Voyager Portal’s developer surface includes documentation, API reference, getting-started guide, engineering blog, authentication, sandbox, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

38.3/100 thin ▬ flat Agent 23/100 agent aware Front door AI 4/6 moderate saas Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

1 API

Company Maritime Shipping LogisticsDemurrageLaytimeVoyagesWorkflowsBulk Commodities

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 38.3/100 · thin

Contract Quality 8.3 / 21

Developer Ergonomics 8.5 / 17

Access Clarity 4.7 / 17

Operational Transparency 3.2 / 11

Contract Governance 0.5 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/voyager-portal: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Maritime Logistics (ocean shipping, eBL, ports)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Voyager Portal Public API

REST API for managing voyages and workflows on the Voyager Portal maritime operations platform. Resources include voyages (schedules, cargoes, documents, categories, models), cl...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Voyager Portal Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Voyager Portal Authentication

http · 1 scheme

SECURITY

Voyager Portal Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Login

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Webhooks

Conformance

DataModel

Build 1

SDKs, sample code, and the tooling you integrate with

SourceCode

SourceCode

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: voyager-portal
name: Voyager Portal
description: Voyager Portal is an AI-powered voyage and demurrage management platform for bulk commodity charterers, traders,
  brokers, and manufacturers, streamlining maritime shipping workflows from pre-fixture planning through post-fixture claim
  resolution. The platform provides AI-driven demurrage claims management and laytime calculations, cargo allocation, AIS
  vessel tracking, ETA tracking, noon reporting, and analytics, and exposes a documented public REST API for managing voyages,
  cargoes, claims, SOFs, vessels, ports, and workflows, plus outbound webhooks.
url: https://raw.githubusercontent.com/api-evangelist/voyager-portal/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
image: https://www.voyagerportal.com/wp-content/uploads/2025/08/teste-1.png
tags:
- Company
- Maritime
- Shipping
- Logistics
- Demurrage
- Laytime
- Voyages
- Workflows
- Bulk Commodities
apis:
- name: Voyager Portal Public API
  description: REST API for managing voyages and workflows on the Voyager Portal maritime operations platform. Resources include
    voyages (schedules, cargoes, documents, categories, models), claims and claim port-calls, statement of facts (SOF) upload
    and parsing, cargoes, companies, groups, datasets, ports, regions, vessels, and workflow instances (start, save task,
    complete task). Authenticated with a bearer token issued by the platform token endpoint; results are paginated with page
    and rowsPerPage parameters.
  image: https://www.voyagerportal.com/wp-content/uploads/2025/08/teste-1.png
  humanURL: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/home
  baseURL: https://kong.voyagerportal.com/api
  tags:
  - Voyages
  - Claims
  - Demurrage
  - SOF
  - Vessels
  - Ports
  - Cargoes
  - Workflows
  properties:
  - type: Documentation
    url: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/home
  - type: APIReference
    url: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/home
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://voyagerportal.com/
- type: Documentation
  url: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/home
- type: APIReference
  url: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/home
- type: GettingStarted
  url: https://gitlab.com/voyager-portal/voyager-public-api/-/wikis/Authentication
- type: Login
  url: https://app.voyagerportal.com/
- type: Blog
  url: https://www.voyagerportal.com/resources/
- type: StatusPage
  url: https://status.voyagerportal.com/
- type: TermsOfService
  url: https://www.voyagerportal.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.voyagerportal.com/privacy/
- type: SourceCode
  url: https://gitlab.com/voyager-portal
- type: Authentication
  url: authentication/voyager-portal-authentication.yml
- type: Conventions
  url: conventions/voyager-portal-conventions.yml
- type: ErrorCatalog
  url: errors/voyager-portal-problem-types.yml
- type: Lifecycle
  url: lifecycle/voyager-portal-lifecycle.yml
- type: Webhooks
  url: asyncapi/voyager-portal-webhooks.yml
- type: WellKnown
  url: well-known/voyager-portal-well-known.yml
- type: Sandbox
  url: sandbox/voyager-portal-sandbox.yml
- type: LLMsTxt
  url: llms/voyager-portal-llms.txt
- type: X-MCPServerCandidate
  url: mcp/voyager-portal-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Conformance
  url: conformance/voyager-portal-conformance.yml
- type: DataModel
  url: data-model/voyager-portal-data-model.yml
- type: DomainSecurity
  url: security/voyager-portal-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 12
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/voyager-portal"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/voyager-portal/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/voyager-portal/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.