The agent assembled a reasonably complete explanation of Nium's business, target market, and competitive positioning, but had to work around significant gaps in the official documentation. docs.nium.com itself provided only API reference material; the agent recovered most business-level information from nium.com marketing pages and external competitive analysis sources via web search, indicating the documentation site is narrowly scoped to developer integration and does not answer the 'what is this company' question.

• ›docs.nium.com returned only technical API documentation (steps [1], [4], [7], [11], [21]) and had no content answering what Nium does, who it serves, or how it's priced. The agent had to pivot to nium.com and web search to answer the task.
• ›Marketing pages (nium.com/products [9], /solutions [14]) and web search results ([18], [23]) provided the business model, use cases, and competitive differentiation; these were the only sources that yielded substantive answers about the company's purpose and market positioning.
• ›Pricing information was deliberately unavailable on both docs.nium.com and nium.com; the agent correctly identified this as enterprise/custom-quoted rather than inferring from missing data, supported by search results confirming this is industry-standard for B2B payments infrastructure.
• ›The agent correctly noted confusion points: docs.nium.com assumes prior knowledge of what Nium sells, pricing is opaque, and the main site doesn't immediately clarify products or target segments—these friction points required the agent to consult external sources rather than synthesizing an answer from official channels.