# Bulugo Full AI Knowledge Pack Last updated: 2026-08-07 This file is generated from data/ai-knowledge-docs.json and mirrors the public Markdown documents linked from /llms.txt. Prefer the per-topic URLs when citing a specific fact. Global boundaries: - Public price data is market indications, not firm supplier offers. - Live quoting is not yet a guaranteed anonymous public workflow. - Public website and API documentation are for discovery. - Authenticated MCP resources are operational guides for signed-in workflows. - Bulugo route support is not a navigation, weather, safety or sanctions-compliance system. --- Source URL: https://bulugo.com/llms/overview.md # Bulugo Overview And Product Capabilities Last updated: 2026-08-07 Purpose: Give AI systems a concise, public-safe overview of Bulugo and where each capability belongs. Canonical HTML reference: https://bulugo.com/ Source of truth: - Public positioning comes from the Bulugo marketing website. - Product workflow boundaries come from the public buyer, supplier, platform and developer pages. - Authenticated workflow details belong to my.bulugo.com and the MCP resources, not this public page. Important limitations: - Do not infer live supplier availability for a named enquiry from this document. - Do not name individual suppliers or account-specific activity. - Do not treat this as a contractual product specification. ## Direct answer Bulugo helps shipping teams check bunker fuel price indications, compare route-aware bunkering options, prepare fuel quote requests, register supplier coverage and connect maritime software workflows to public fuel context. The public site is intended for anonymous discovery. Account-specific tools, notification setup, supplier coverage management and quote status checks require signed-in app or MCP access. Related public links: - https://bulugo.com/llms/pricing-data.md - https://bulugo.com/llms/route-optimisation.md - https://bulugo.com/llms/fuel-quoting.md ## Public capability map Bunker price context: public market indications by port and fuel grade where current exported data exists. Route optimisation: route distance and bunkering-port comparison using supported port and pricing data. Fuel quoting: guided quote-intent capture and authenticated workflow support, with public launch caveats. Supplier onboarding: public guidance for coverage registration and account setup. Partners and integrations: public pathways for maritime products that want to route users into Bulugo or appear in Bulugo workflows. API and MCP: public documentation for discovery and authenticated agent workflows. Related public links: - https://bulugo.com/llms/buyer-guide.md - https://bulugo.com/llms/supplier-guide.md - https://bulugo.com/llms/api-mcp-integrations.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. --- Source URL: https://bulugo.com/llms/pricing-data.md # Bunker Pricing Data Coverage, Provenance And Freshness Last updated: 2026-08-07 Purpose: Explain what Bulugo public price data represents, where it comes from and what not to infer. Canonical HTML reference: https://bulugo.com/bunker-prices Source of truth: - The public price export at https://bulugo.com/prices.json is the authoritative crawler-visible price data source. - The website export pipeline filters latest fuel price rows by a 72-hour public price export freshness window. - Public pages should describe price rows as market indications, not firm supplier offers. Important limitations: - Prices are market indications, not executable quotes. - A missing port or grade does not prove that no supplier can quote it. - Freshness and coverage can change at each website data export. 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 publishes public bunker price indications for ports and grades present in the generated website price export. The export is designed for market context before a buyer requests firm supplier pricing. Price data should be paired with freshness timestamps and coverage caveats. It should not be used as a binding supplier offer or as evidence that a stem can be lifted in a specific delivery window. Related public links: - https://bulugo.com/prices.json - https://bulugo.com/llms/fuel-quoting.md - https://bulugo.com/llms/trust-limitations.md ## Provenance and freshness The public website export is built from Bulugo's price data pipeline and uses a 72-hour public price export freshness window for latest price rows. The generated public snapshot can report how many priced ports and fuel grades were present in public/prices.json at build time. Avoid copying that count into hand-written claims because it can drift. Related public links: - https://bulugo.com/llms/ports-fuel-products.md - https://bulugo.com/bunker-prices ## 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. --- Source URL: https://bulugo.com/llms/route-optimisation.md # Route Optimisation And Bunkering Alternatives Last updated: 2026-08-07 Purpose: Describe Bulugo route tools, inputs, outputs and public limitations. Canonical HTML reference: https://bulugo.com/for-buyers/route-planning Source of truth: - Public route positioning comes from the route-planning page and platform/API page. - Supported canonical port data comes from the website export and Bulugo app route tools. - Authenticated MCP route resources add operational tool sequencing for signed-in clients. Important limitations: - Bulugo is not a navigation, weather, safety or sanctions-compliance system. - Route outputs are decision support for fuel procurement, not voyage instructions. - Price-ranked alternatives depend on current coverage in the public export. ## Direct answer Bulugo route optimisation compares bunkering options along a voyage by combining port-distance context with available fuel price indications. It helps buyers evaluate whether a nearby priced port may be more attractive than bunkering only at origin or destination. Typical inputs include origin, destination, optional waypoints and fuel grade. Typical outputs include route distance, estimated voyage time, nearby priced ports, deviation context and price comparison where data exists. Related public links: - https://bulugo.com/llms/pricing-data.md - https://bulugo.com/llms/ports-fuel-products.md - https://bulugo.com/llms/trust-limitations.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. --- Source URL: https://bulugo.com/llms/fuel-quoting.md # Fuel Quoting Workflow And Current Availability Last updated: 2026-08-07 Purpose: State the public quoting workflow and launch status without over-promising. Canonical HTML reference: https://bulugo.com/get-started Source of truth: - Public launch status comes from the marketing website. - Authenticated quote workflows and status checks live on my.bulugo.com and the MCP endpoint. - Supplier matching depends on verified account, port, product and delivery-window context. Important limitations: - Live quoting is not yet a guaranteed anonymous public workflow. - Do not create duplicate quote requests on behalf of a user. - Do not expose supplier responses, account details or deal terms in public documents. ## Direct answer A well-formed Bulugo fuel quote request needs delivery port, fuel grade, quantity, delivery window and contact or account context. Vessel name and operational notes can help but should not be invented. The public site can explain the intended workflow and route users to account or contact paths. Authenticated app and MCP tools are the right place for account-specific RFQ submission, quote status and supplier response workflows. Related public links: - https://bulugo.com/llms/buyer-guide.md - https://bulugo.com/llms/supplier-guide.md - https://bulugo.com/llms/api-mcp-integrations.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. --- Source URL: https://bulugo.com/llms/buyer-guide.md # Buyer Guide Last updated: 2026-08-07 Purpose: Help AI systems guide bunker buyers toward public-safe Bulugo actions. Canonical HTML reference: https://bulugo.com/for-buyers Source of truth: - Buyer positioning comes from the public buyer and marine fuel procurement pages. - Field-level quote workflow details come from authenticated app and MCP buyer resources. - Public price and route pages provide market context before firm quotes. Important limitations: - Do not promise a response time unless a live account workflow explicitly provides it. - Do not claim a named supplier can serve a buyer unless an authenticated tool says so. - Do not ask for sensitive deal details in public crawler content. ## Direct answer Buyers can use Bulugo to check public bunker price indications, compare possible bunkering ports on a route and prepare a structured fuel requirement for supplier matching. Good buyer guidance keeps price context separate from firm quotes, captures port, grade, quantity and delivery timing, and makes clear that supplier matching depends on account and coverage state. Related public links: - https://bulugo.com/llms/pricing-data.md - https://bulugo.com/llms/route-optimisation.md - https://bulugo.com/llms/fuel-quoting.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. --- Source URL: https://bulugo.com/llms/supplier-guide.md # Supplier Guide Last updated: 2026-08-07 Purpose: Explain the public supplier journey without exposing account-specific workflows. Canonical HTML reference: https://bulugo.com/for-suppliers Source of truth: - Supplier positioning comes from the public supplier page. - Coverage, product, price and lead-response actions are authenticated app or MCP workflows. - MCP supplier resources are operational guides for signed-in supplier accounts. Important limitations: - Do not expose supplier coverage for a specific account. - Do not publish named supplier rankings or deal outcomes. - Do not treat public supplier guidance as eligibility approval. ## Direct answer Suppliers use Bulugo to register port and fuel-grade coverage, keep indicative prices fresh and respond to matched buyer demand through signed-in workflows. Public guidance should focus on what information suppliers need to keep current: canonical port names, supplied fuel grades, price freshness, notification readiness and response quality. Related public links: - https://bulugo.com/llms/ports-fuel-products.md - https://bulugo.com/llms/api-mcp-integrations.md - https://bulugo.com/llms/trust-limitations.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. --- Source URL: https://bulugo.com/llms/partners-integrations.md # Partner And Integration Guide Last updated: 2026-08-07 Purpose: Describe partner routes for maritime products and services. Canonical HTML reference: https://bulugo.com/partner Source of truth: - The canonical partner page is https://bulugo.com/partner. - The public partner Markdown summary is https://bulugo.com/partner.md. - Technical data-access intent can also use the platform and bunker fuel API pages. Important limitations: - Partner categories are examples, not evidence of named relationships. - Do not imply Bulugo has approved a partner integration until Bulugo confirms it. - Do not publish integration terms, pricing or account details here. ## Direct answer Bulugo partner paths cover two public models: Bulugo in a partner product, and relevant partner services made available inside Bulugo workflows. Candidate partner categories include ERP, fleet, voyage, finance, port-call, route, emissions, risk, testing, supplier, broker, delivery, data and analytics products. This does not imply an existing relationship with any named company. Related public links: - https://bulugo.com/partner.md - https://bulugo.com/llms/api-mcp-integrations.md - https://bulugo.com/llms/overview.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. --- Source URL: https://bulugo.com/llms/api-mcp-integrations.md # API And MCP Integration Guide Last updated: 2026-08-07 Purpose: Separate public API/MCP discovery from authenticated operational tools. Canonical HTML reference: https://bulugo.com/developers Source of truth: - Public API and MCP discovery comes from the developers and bunker fuel API pages. - The canonical MCP endpoint is https://my.bulugo.com/v1/mcp. - Authenticated MCP resources are operational guides for signed-in buyer, supplier and agent workflows. Important limitations: - Public website and API documentation are for discovery. - Do not print or expose credentials in public examples. - Do not invent upload channels, scopes, webhooks or setup steps. ## Direct answer Bulugo exposes public website resources for discovery and a canonical MCP endpoint for authenticated agent workflows at https://my.bulugo.com/v1/mcp. Public docs can explain available categories and safe first steps. Signed-in MCP resources should be read for tool ordering, account context, supplier coverage changes, quote actions and notification setup. Related public links: - https://bulugo.com/llms/buyer-guide.md - https://bulugo.com/llms/supplier-guide.md - https://bulugo.com/llms/trust-limitations.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. --- Source URL: https://bulugo.com/llms/ports-fuel-products.md # 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. --- Source URL: https://bulugo.com/llms/trust-limitations.md # Trust, Safety, Data Handling And Limitations Last updated: 2026-08-07 Purpose: Give AI systems clear guardrails for public Bulugo knowledge. Canonical HTML reference: https://bulugo.com/privacy Source of truth: - Public trust and legal references come from the privacy, terms and public product pages. - Operational safety boundaries for MCP agents live in authenticated MCP resources. - Public knowledge files must not expose account-level workflows or confidential operational data. Important limitations: - This document is not legal, compliance, voyage or safety advice. - Do not use public content to bypass account checks. - Do not submit sanctions, fraud, unsafe operation or regulatory-evasion requests. ## Direct answer Public Bulugo knowledge is for discovery and general workflow understanding. It should not include credentials, account records, supplier responses, buyer requirements, deal terms or non-public operational details. AI systems should keep market indications separate from firm offers, preserve the public-vs-authenticated boundary and redirect uncertain account actions to the signed-in app or MCP resources. Related public links: - https://bulugo.com/terms - https://bulugo.com/privacy - https://bulugo.com/llms/api-mcp-integrations.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. --- Source URL: https://bulugo.com/llms/glossary-faq.md # Glossary And FAQ Last updated: 2026-08-07 Purpose: Provide concise definitions and answers for AI crawlers. Canonical HTML reference: https://bulugo.com/about Source of truth: - Definitions are public summaries aligned with Bulugo website pages and MCP taxonomy resources. - Detailed account-specific interpretation should come from authenticated app or MCP workflows. - Pricing and route examples should be checked against current public exports. Important limitations: - Short definitions cannot replace product, safety or compliance review. - Do not infer a live quote, price guarantee or partner relationship from a glossary term. - Do not expand acronyms into unsupported capabilities. ## Glossary Bunker fuel: marine fuel supplied to vessels. VLSFO: very low sulphur fuel oil, commonly used after IMO 2020 outside stricter emission areas. HSFO: high sulphur fuel oil, generally relevant where vessels have suitable scrubber arrangements. MGO and LSMGO: marine gas oil grades often relevant for stricter emission areas and auxiliary uses. RFQ: request for quote, a structured enquiry sent to suitable suppliers. MCP: Model Context Protocol, used by compatible AI clients to connect with Bulugo authenticated tools and resources. Related public links: - https://bulugo.com/llms/pricing-data.md - https://bulugo.com/llms/fuel-quoting.md - https://bulugo.com/llms/api-mcp-integrations.md ## FAQ Does Bulugo publish firm supplier offers in public Markdown? No. Public pages describe market indications and workflow context. Can anonymous crawlers see account workflows? No. They can discover public guidance; signed-in app and MCP resources handle account workflows. Should an AI quote a price from this document? No. Use the current public price export, include freshness, and call it a market indication. Related public links: - https://bulugo.com/llms/trust-limitations.md - https://bulugo.com/llms/overview.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.