For agents & integrators
NERMO is API-first: one canonical API drives the portals, and the same surface runs as a hosted MCP server. A vessel-side procurement agent can discover NERMO, match products, request quotes, place orders, and track delivery — structured end to end.
// discover & match list_canonical_products · match_products list_substitutes // quote request_quote · update_rfq · send_rfq list_rfqs · get_rfq · list_quotes // order & track submit_order · order_status
The agent surface
The MCP tools are a projection of the canonical API: the same entities your operator sees in the portal — one catalog, one order, one set of statuses. What the agent does, the fleet manager can audit.
Search the canonical catalog, match requisition lines against 50,000+ marine stores and provisions, and pull curated substitutes when an item can't ship.
Draft an RFQ for a port-of-call, update it line by line, send it to vetted local vendors, and read the quotes back — prices exactly as submitted.
Turn a chosen quote into a routed purchase order and track it to delivery — the same status enums the vendor and NERMO ops see.
{
"tool": "request_quote",
"arguments": {
"port": "NLRTM", // Rotterdam
"eta": "2026-07-14T22:00Z",
"items": [
{ "name": "Mooring rope 64mm", "qty": 4, "unit": "coil" },
{ "name": "Welding electrodes", "qty": 20, "unit": "box" }
]
}
}{
"rfq_id": "rfq_8f31a2",
"port": "NLRTM",
"quotes": [
{ "vendor": "(vetted · KYC · sanctions-screened)",
"total": { "amount": "as quoted", "currency": "EUR" },
"delivery_window": "berth, within ETA ±6h" }
],
"pricing": "vendor-submitted, no markup" // always
}Integration model
OAuth 2.1 with PKCE for user-present assistants — the human signs in, the agent never sees a password. Headless agents get service accounts with their own credentials and scopes.
Ports, items, quotes, orders, and statuses are typed entities shared across the API, MCP, and all three portals — your integration never parses prose.
Every write tool takes an idempotency key: mint a UUID per intent, replay it on retry, and a flaky connection can never double-order.
Every order-affecting action an agent takes is written to the audit trail and lands in the operator's portal. Procurement teams supervise their agents with full visibility — by design, not by export.
Connecting a client is not having an account. Any agent can register as an OAuth client and discover the endpoint — but quotes and orders only flow for operators who have been verified and onboarded by NERMO. If your operator isn't on the network yet, start with Request access. And if you just want to connect Claude or ChatGPT to a fleet that's already aboard, that's the MCP page.
For agents & integrators
Building procurement automation for a fleet? Get the operator verified, connect over MCP, and the loop is yours — request, order, track.
Reference documentation and the full OpenAPI contract are public; credentials ship with onboarding.