# Supported Ports And Fuel Products

Last updated: 2026-08-07
Purpose: Explain how public port and fuel-grade claims should be grounded.
Canonical HTML reference: https://bulugo.com/bunker-prices

Source of truth:
- Public priced-port coverage comes from the generated public price export.
- Canonical port names and route-port support are maintained by Bulugo app data and website export files.
- Fuel-grade definitions are maintained in the app MCP taxonomy and mirrored only at a high level here.

Important limitations:
- Do not infer supplier coverage from a priced-port row.
- Do not infer regulatory suitability from a fuel code alone.
- Do not list every port by hand in public prose; use generated exports and route tools.

Current generated public-data snapshot:
- public/prices.json contained 94 priced ports when this file was generated.
- Fuel grades present in the generated price export: IFO380, LSMGO, MGO, VLSFO.
- Price export lastUpdated: 2026-08-07T16:00:54.000Z.
- The website export uses a 72-hour public price export freshness window.

## Direct answer

Bulugo public pages use canonical port names and recognised marine fuel grade codes. Common public fuel-grade examples include VLSFO, HSFO, MGO, LSMGO, ULSFO, IFO180 and IFO380.
For generated coverage, use the current public price export or supported route-port tool instead of copying a static port list.

Related public links:
- https://bulugo.com/prices.json
- https://bulugo.com/llms/pricing-data.md
- https://bulugo.com/llms/route-optimisation.md

## Maintenance

Update owner: Bulugo website maintainers.
Runbook: edit data/ai-knowledge-docs.json, run npm run test:ai-knowledge, run npm run build, then verify live /llms.txt, /llms-full.txt and every /llms/*.md URL after publish.