bol-ai

endpoint

https://bol.ai/api/mcp

door code

30d970aadfce6465

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is bol-ai live?

Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.

Is bol-ai free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does bol-ai have?

8 tools: list_documents, get_document, extract_bol, save_corrections, export_documents, get_usage, get_related_documents, extract_batch.

Is bol-ai safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• list_documents reads auth-required 14h ago

  List the 100 most recent documents for this account with id, filename, status (pending/done/failed), doc_type and primary reference number.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_document reads auth-required 14h ago

  Get the extraction result for a document by id: doc_type, extracted fields, user corrections (when present), and deterministic verification warnings (ISO 6346 container check digits, plausibility flags). `fields` is the best available data (corrections win); `original_fields` and `corrected_fields` show both sides.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Document id"
      }
    }
  }

  arguments 12 lines copy
• extract_bol reads auth-required never probed

  Extract structured data from a freight document (PDF, PNG or JPG, max 10 MB): Bill of Lading, commercial invoice, packing list, or CMR road waybill. The document type is detected automatically and returned as `doc_type`. Provide either a fetchable `url` or `base64` file content. Fields not present in the document are null — never guessed. Each successful extraction bills one document.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "properties": {
      "url": {
        "type": "string",
        "description": "URL of the document to fetch and extract"
      },
      "base64": {
        "type": "string",
        "description": "Base64-encoded file content (alternative to url)"
      },
      "filename": {
        "type": "string",
        "description": "Filename including extension, e.g. shipment-4711.pdf"
      }
    }
  }

  arguments 17 lines copy
• save_corrections changes data auth-required never probed

  Save corrected field values for an extracted document. The original extraction is kept alongside the corrections; corrected data takes precedence in get_document, exports and reconciliation. Pass the complete corrected fields object (same shape as returned by get_document).

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "id",
      "fields"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Document id"
      },
      "fields": {
        "type": "object",
        "description": "Complete corrected fields object, including doc_type"
      }
    }
  }

  arguments 17 lines copy
• export_documents reads auth-required never probed

  Export completed extractions as TMS/ERP-ready normalized line rows (one row per container / invoice line / package / goods line), newest first. Optional doc_type filter and max_rows cap. Corrected data wins over the original extraction. For CSV/XLSX files use GET /api/bol/export on the REST API.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "properties": {
      "type": {
        "enum": [
          "bill_of_lading",
          "commercial_invoice",
          "packing_list",
          "cmr"
        ],
        "type": "string",
        "description": "Only include documents of this type"
      },
      "max_rows": {
        "type": "number",
        "description": "Maximum rows to return (default 500)"
      }
    }
  }

  arguments 19 lines copy
• get_usage reads auth-required 14h ago

  Check this account's remaining prepaid credits and subscription status. Call this before large batches to avoid running out of credits mid-workflow. When the account cannot bill more documents, a human can top up at the returned buy_credits_url.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_related_documents reads auth-required 10h ago

  Cross-document reconciliation: find the other documents in this shipment (linked by shared reference numbers such as B/L number and invoice number) and compare them field by field — shipper/seller and consignee/buyer names, total gross weight (5% tolerance) and package counts. Returns matches and mismatches per linked document. Catches the discrepancies that cause customs holds, amended entries and demurrage. Deterministic — no extra document billed.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "string",
        "description": "Document id to reconcile against the rest of the account"
      }
    }
  }

  arguments 12 lines copy
• extract_batch reads auth-required never probed

  Extract up to 10 freight documents in one call. Provide an array of fetchable URLs; each document is processed and billed independently, and the response reports a per-document outcome so partial success (e.g. running out of credits mid-batch) is explicit.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "required": [
      "urls"
    ],
    "properties": {
      "urls": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "maxItems": 10,
        "minItems": 1,
        "description": "URLs of documents to fetch and extract (max 10)"
      }
    }
  }

  arguments 17 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.