# 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.