{
  "catalog": {
    "name": "Konyx Knowledge Catalog",
    "version": "1.0",
    "updatedAt": "2026-10-27",
    "owner": "Konyx Industrial Intelligence",
    "contact": "ceo@konyxai.com",
    "site": "https://konyxai.com",
    "description": "The structured, versioned facts about Konyx — industrial procurement software for MRO and indirect spend — that konyxai.com and AI assistants answer from. Every record names its source and the date it was last checked against the product; a capability says whether it is live, planned or not offered.",
    "formats": {
      "html": "https://konyxai.com/knowledge",
      "json": "https://konyxai.com/api/knowledge",
      "markdown": "https://konyxai.com/llms-full.txt",
      "index": "https://konyxai.com/llms.txt"
    }
  },
  "domains": [
    {
      "slug": "company",
      "name": "Company",
      "description": "What Konyx is, the problem it exists for, who it is for and how it differs from the systems a plant already has.",
      "question": "What is Konyx?",
      "url": "https://konyxai.com/knowledge/company",
      "json": "https://konyxai.com/api/knowledge/company",
      "records": 6
    },
    {
      "slug": "capabilities",
      "name": "Product capabilities",
      "description": "Every capability as a record: what goes in, what comes out, and whether it is live, planned or deliberately not offered.",
      "question": "What can Konyx do?",
      "url": "https://konyxai.com/knowledge/capabilities",
      "json": "https://konyxai.com/api/knowledge/capabilities",
      "records": 24
    },
    {
      "slug": "how-it-works",
      "name": "How it works",
      "description": "The four steps from a request on the floor to quotes side by side and a vendor chosen, and exactly what the AI does and does not do at each one.",
      "question": "How does Konyx work?",
      "url": "https://konyxai.com/knowledge/how-it-works",
      "json": "https://konyxai.com/api/knowledge/how-it-works",
      "records": 6
    },
    {
      "slug": "use-cases",
      "name": "Problems and solutions",
      "description": "Concrete situations in a plant's purchasing, and what Konyx does about each.",
      "question": "What problems does Konyx solve?",
      "url": "https://konyxai.com/knowledge/use-cases",
      "json": "https://konyxai.com/api/knowledge/use-cases",
      "records": 10
    },
    {
      "slug": "industries",
      "name": "Industries",
      "description": "Where Konyx fits: asset-heavy plants and the purchasing patterns they share.",
      "question": "Who is Konyx built for?",
      "url": "https://konyxai.com/knowledge/industries",
      "json": "https://konyxai.com/api/knowledge/industries",
      "records": 6
    },
    {
      "slug": "faq",
      "name": "Questions and answers",
      "description": "The questions buyers, finance and IT ask before a pilot, answered once.",
      "question": "Does Konyx replace our ERP?",
      "url": "https://konyxai.com/knowledge/faq",
      "json": "https://konyxai.com/api/knowledge/faq",
      "records": 17
    },
    {
      "slug": "control",
      "name": "Control, security and audit",
      "description": "How Konyx keeps a person in charge of every send, isolates each company, and records what happened.",
      "question": "How is Konyx controlled and secured?",
      "url": "https://konyxai.com/knowledge/control",
      "json": "https://konyxai.com/api/knowledge/control",
      "records": 10
    },
    {
      "slug": "pilot",
      "name": "The pilot",
      "description": "How a company starts: one facility, ninety days, a baseline from its own purchasing history.",
      "question": "How do we start with Konyx?",
      "url": "https://konyxai.com/knowledge/pilot",
      "json": "https://konyxai.com/api/knowledge/pilot",
      "records": 5
    },
    {
      "slug": "integrations",
      "name": "Integrations and data",
      "description": "What connects to Konyx today, what comes in by spreadsheet, and what is planned.",
      "question": "Does Konyx integrate with our systems?",
      "url": "https://konyxai.com/knowledge/integrations",
      "json": "https://konyxai.com/api/knowledge/integrations",
      "records": 5
    },
    {
      "slug": "proof",
      "name": "Evidence",
      "description": "What Konyx can and cannot show yet, and how its claims are measured.",
      "question": "What evidence is there that Konyx works?",
      "url": "https://konyxai.com/knowledge/proof",
      "json": "https://konyxai.com/api/knowledge/proof",
      "records": 3
    }
  ],
  "records": [
    {
      "id": "company.what-konyx-is",
      "domain": "company",
      "slug": "what-konyx-is",
      "name": "What Konyx is",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — home page"
      },
      "summary": "Konyx is industrial procurement software for MRO (maintenance, repair and operations) and indirect spend. It takes a request from the plant floor to quotes side by side: it reads the request, matches it against the company's own catalog and purchase history, ranks vendors, sends the RFQ and lines the quotes up so the buyer can pick the winner — and a person reviews every step.",
      "body": [
        "Konyx is a web application used from a browser on a desk or a phone. It is not an ERP and does not replace one: the ERP stays the system of record for the order and the money, and Konyx owns the work that happens before the order exists — the request, the sourcing, the RFQ, the quotes and the decision.",
        "The company is Konyx Industrial Intelligence. The product is at an early stage: complete for pilots, with no published customer results yet."
      ],
      "fields": {
        "Legal name": "Konyx Industrial Intelligence",
        "Website": "https://konyxai.com",
        "Product type": "Web application, browser-based, phone-first",
        "Category": "Procurement software — MRO and indirect spend",
        "Stage": "Pilot-ready; first design-partner pilots",
        "Contact": "ceo@konyxai.com"
      },
      "related": [
        "company.problem",
        "company.who-konyx-is-for",
        "company.how-konyx-differs",
        "how-it-works.overview"
      ],
      "url": "https://konyxai.com/knowledge/company#what-konyx-is"
    },
    {
      "id": "company.problem",
      "domain": "company",
      "slug": "problem",
      "name": "The problem Konyx exists for",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — Purpose"
      },
      "summary": "In most plants the request-for-quotation cycle for MRO and indirect parts takes days: a technician describes a part without its number, a buyer chases vendors by phone and email, quotes come back as PDFs, and nobody sees what was paid last time. Konyx collapses that cycle to minutes.",
      "body": [
        "The cost is not only the buyer's day. A rush part bought from whoever answers first costs more than the contract price; a quote compared against nothing is accepted as it is; a request that sits in an inbox delays maintenance. Konyx puts the company's own data — catalog, vendors, purchase history, contracts — beside every line, so the decision is informed and quick."
      ],
      "related": [
        "company.what-konyx-is",
        "use-cases.last-paid-price",
        "use-cases.no-part-number"
      ],
      "url": "https://konyxai.com/knowledge/company#problem"
    },
    {
      "id": "company.who-konyx-is-for",
      "domain": "company",
      "slug": "who-konyx-is-for",
      "name": "Who Konyx is for",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Who it's for"
      },
      "summary": "Konyx is built for asset-heavy plants — refining, chemicals, LNG, aerospace, mills — and for four kinds of people in them: maintenance and operations, procurement, plant and finance leadership, and IT and security.",
      "body": [
        "Maintenance and operations raise requests without leaving the job and see where each one is. Procurement receives structured requests, ranked vendors and comparable quotes instead of chasing. Leadership sees what was asked, what it cost last time, what it cost now and how long each step took. IT and security get one backend, isolation between companies, permissions on every call and an append-only log."
      ],
      "audiences": [
        "technicians",
        "buyers",
        "finance",
        "IT and security"
      ],
      "industries": [
        "refining",
        "chemicals",
        "LNG and energy",
        "aerospace",
        "mills",
        "general manufacturing"
      ],
      "related": [
        "industries.refining",
        "industries.general-manufacturing",
        "company.what-konyx-is"
      ],
      "url": "https://konyxai.com/knowledge/company#who-konyx-is-for"
    },
    {
      "id": "company.how-konyx-differs",
      "domain": "company",
      "slug": "how-konyx-differs",
      "name": "How Konyx differs from an ERP, a portal or a marketplace",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — What Konyx does"
      },
      "summary": "Konyx is not an ERP, not a vendor portal for technicians to learn, and not a marketplace. It is the front door that understands a request in plain words and the back office that finishes it — with the company's own vendors, its own prices and its own rules.",
      "body": [
        "Against an ERP: the ERP records orders and money; it does not read a photo of a nameplate, find a vendor for a niche part, or send an RFQ to six suppliers at once. Konyx does that work, up to the quotes compared and the vendor chosen, and the ERP keeps the record.",
        "Against an e-procurement portal: a portal asks the requester to know the catalog. Konyx asks what they need, in their words, and does the lookup itself.",
        "Against a marketplace: Konyx does not sit between the buyer and the vendor. The company's own vendors quote directly to the company through a link; Konyx supplies the structure, the comparison and the record."
      ],
      "related": [
        "faq.replace-erp",
        "faq.marketplace",
        "capabilities.ask-konyx"
      ],
      "url": "https://konyxai.com/knowledge/company#how-konyx-differs"
    },
    {
      "id": "company.principles",
      "domain": "company",
      "slug": "principles",
      "name": "Principles Konyx is built on",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §1, §3.7, §3.8"
      },
      "summary": "Five rules govern the product: the AI is never the system of record; a person presses Send; the database is the source of truth and the model interprets it; every state change is recorded in the same transaction as the change; and each company is isolated below the application, in the database.",
      "body": [
        "These are not policies layered on afterwards. Drafting an RFQ and sending it are separate permissions; the model's confidence is computed in code from what it could and could not confirm, never taken from the model's own estimate; the audit log cannot drift from reality because the same function that changes a status is the only thing that writes the audit event."
      ],
      "related": [
        "control.person-presses-send",
        "control.append-only-audit",
        "control.tenant-isolation",
        "how-it-works.what-the-ai-does"
      ],
      "url": "https://konyxai.com/knowledge/company#principles"
    },
    {
      "id": "company.contact",
      "domain": "company",
      "slug": "contact",
      "name": "How to reach Konyx",
      "verifiedAt": "2026-10-26",
      "version": 4,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — footer"
      },
      "summary": "Email ceo@konyxai.com, or book a demo through the form on konyxai.com. Customers sign in at app.konyxai.com.",
      "body": [
        "A demo is about thirty minutes and walks the flow from a request to the quotes side by side, with the prospect's own part numbers and vendors. No account is created by the demo form; the details are only used to reply."
      ],
      "fields": {
        "Email": "ceo@konyxai.com",
        "Book a demo": "https://konyxai.com/#demo",
        "Customer sign-in": "https://app.konyxai.com"
      },
      "related": [
        "pilot.shape"
      ],
      "url": "https://konyxai.com/knowledge/company#contact"
    },
    {
      "id": "capabilities.ask-konyx",
      "domain": "capabilities",
      "slug": "ask-konyx",
      "name": "Ask Konyx — request intake",
      "status": "live",
      "verifiedAt": "2026-10-27",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — the Ask Konyx screen; prompt request-extract v4"
      },
      "summary": "The first screen is a question: what do you need? A person says it, types it, photographs the nameplate or drops in a spreadsheet, and Konyx turns it into a structured request — items, quantities, part numbers, manufacturer, urgency — then asks one or two specific questions with the usual answers ready to tap.",
      "body": [
        "Every extracted field carries a state — confirmed, inferred or unknown — and the request's confidence is computed from those states in code, not reported by the model. The person sees the draft, corrects anything, answers the open questions and confirms; nothing is created until they do. A short answer such as a size is enough on its own, and follow-ups re-send the original photos so the model still sees the item.",
        "It works on a phone browser on the plant floor: the composer is pinned at the bottom, the draft opens as a sheet, and voice is transcribed on the server when the browser cannot do it.",
        "On the Search plan, Ask Konyx stops at the vendors. It reads the request the same way — typed, spoken, a photo or a spreadsheet — and finds the company's own vendors, the Konyx network and Konyxions, ranked with reasons, each with its contact details and a link to the matching product where one was found, so the buyer contacts them directly. It creates no request or RFQ and sends nothing. Each new request asked counts as one of the plan's searches; moving to Starter or above adds RFQ drafts."
      ],
      "fields": {
        "Inputs": [
          "typed text",
          "voice",
          "photos (nameplates, labels, the part itself)",
          "spreadsheets and CSV files"
        ],
        "Outputs": [
          "a structured request with one line per item",
          "per-field confirmed / inferred / unknown state",
          "clarifying questions with tappable answers",
          "catalog matches and purchase history per line",
          "vendors ranked with reasons"
        ],
        "Not in v1": [
          "barcode scanning",
          "email-to-request",
          "a native mobile app"
        ]
      },
      "audiences": [
        "technicians",
        "buyers"
      ],
      "related": [
        "capabilities.catalog-matching",
        "capabilities.vendor-ranking",
        "how-it-works.ask",
        "use-cases.no-part-number",
        "capabilities.plan-limits"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#ask-konyx"
    },
    {
      "id": "capabilities.catalog-matching",
      "domain": "capabilities",
      "slug": "catalog-matching",
      "name": "Matching against the company's own catalog",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/item-match.ts"
      },
      "summary": "Every request line is matched against what the company already buys — its item master and its vendors' catalogs — by part number and normalised description. It is a lookup in the database, not a model's guess: nothing a model invents, a record found in the company's own data.",
      "body": [
        "Matching is identifier similarity: a request for a Lovejoy L190 finds the catalog's Lovejoy L-190. Each match carries the vendor that sells it, the contract or catalog price, and the vendor's own part number. A stated manufacturer must agree on both sides; when two catalog rows disagree Konyx leaves the match blank rather than guess, because a wrong part number in front of a vendor is worse than none.",
        "A row only counts as the item when it is the item: the size (2\", 2 in and 2-inch are the same), the material and grade, the end connection, the pressure rating, the maker and any code written into the description must agree, and a 3-way valve or a repair kit is not the valve. A vendor that only has other sizes or materials is shown as having similar items — never pre-selected as carrying it."
      ],
      "fields": {
        "Method": "Trigram and word similarity in Postgres on normalised names and part numbers, scoped to the company, then a same-item check on size, material, ends, rating, maker and codes — in code, not a model",
        "Outputs": [
          "matched item",
          "vendor and price",
          "the vendor's own part number",
          "contract price when one exists"
        ]
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "capabilities.bought-before",
        "capabilities.vendor-ranking",
        "faq.ai-models"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#catalog-matching"
    },
    {
      "id": "capabilities.bought-before",
      "domain": "capabilities",
      "slug": "bought-before",
      "name": "Purchase history beside every line",
      "status": "live",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/purchase-context.ts"
      },
      "summary": "Under each line of a draft, Konyx shows whether the company bought this before — from its imported purchase history, earlier quotes and earlier requests — and what it paid. The same last-paid price sits beside every quote later.",
      "body": [
        "This is a query over the company's own rows, so it costs nothing and cannot hallucinate. It is what makes a quote comparison credible: you paid this in August; this quote is that."
      ],
      "fields": {
        "Sources": [
          "imported purchase history",
          "quotes received in Konyx",
          "earlier requests"
        ],
        "Shown": [
          "on the intake draft",
          "on the request page",
          "beside every quoted line"
        ]
      },
      "audiences": [
        "buyers",
        "finance"
      ],
      "related": [
        "capabilities.quote-comparison",
        "use-cases.last-paid-price",
        "integrations.spreadsheets"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#bought-before"
    },
    {
      "id": "capabilities.vendor-ranking",
      "domain": "capabilities",
      "slug": "vendor-ranking",
      "name": "Vendors ranked with reasons",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/vendor-rank.ts"
      },
      "summary": "For every request, the company's own approved vendors are ranked best-first with the reasons on the card: how many lines they carry, exact part-number hits, the lowest price on a line, volume pricing, and whether there is someone to email. Then the Konyx network, then Konyxions — vendors Konyx found on the open web.",
      "body": [
        "The buyer picks from one list. Ranking is explainable arithmetic over the company's data, so two buyers see the same order and can say why a vendor is first.",
        "Konyx network vendors and Konyxions are also ordered by where they are: when two cover the same lines, the one based in the buyer's country comes first. The buyer's country is the country of the requester's site, when their site in Konyx has one; otherwise the company's country; otherwise the country the request is being made from. It breaks a tie and never hides anyone: a vendor abroad that matches better still ranks above."
      ],
      "fields": {
        "Order": [
          "the company's own vendors",
          "the Konyx network",
          "Konyxions — vendors Konyx found on the web"
        ],
        "Reasons": [
          "lines covered",
          "exact part numbers",
          "lowest price on a line",
          "volume pricing",
          "contactable",
          "near the buyer — based in the buyer's country (Konyx network and Konyxions)"
        ]
      },
      "audiences": [
        "buyers"
      ],
      "related": [
        "capabilities.konyx-network",
        "capabilities.vendor-discovery",
        "capabilities.rfq"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#vendor-ranking"
    },
    {
      "id": "capabilities.konyx-network",
      "domain": "capabilities",
      "slug": "konyx-network",
      "name": "The Konyx network",
      "status": "live",
      "verifiedAt": "2026-10-09",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-api — platform vendors and catalogs"
      },
      "summary": "The Konyx network is a set of vendors and catalogs maintained by Konyx, suggested beneath a company's own vendors only when a catalog line actually matches the request. Choosing one copies it into the company's own list.",
      "body": [
        "Network vendors are platform data, not any customer's. A company never sees another company's vendors; it sees Konyx's, and only where they carry the part.",
        "A network or Konyxion product is found by its words, then checked once by a small model call — is it the item asked for, a close variant, or something else that merely shares a word — before the vendor is said to carry it. A close variant is labelled as one; anything else is not shown. The answer is kept, so the same question is never paid for twice."
      ],
      "audiences": [
        "buyers"
      ],
      "related": [
        "capabilities.vendor-ranking",
        "faq.konyx-network"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#konyx-network"
    },
    {
      "id": "capabilities.vendor-discovery",
      "domain": "capabilities",
      "slug": "vendor-discovery",
      "name": "Konyxions — vendors found on the open web",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 4,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/discovery"
      },
      "summary": "For niche parts nobody in the company's list carries, Konyx searches the web, filters the results cheapest-first, reads the survivors' contact pages, scores each candidate with the score's parts kept, and shows them as Konyxions — with contacts, reasons and a link to the matching product on the vendor's own site, so the buyer can open it and check it is the right item. Konyxions are looked for worldwide, starting near the buyer. Nothing is emailed until a person picks the vendor and checks the address.",
      "body": [
        "The search for Konyxions is not limited to one country. Each one is pointed at the buyer's country — the country of the requester's site, when their site in Konyx has one; otherwise the company's country, set in Settings, filled in from the billing address when a company signs up online, and settable by Konyx staff; otherwise the country the request is being made from, taken from the connection. Results are localised to that country, so nearby vendors come up first, and vendors elsewhere still appear.",
        "A Konyxion based in that country gets a small boost and its card says it is near. It is a tie-breaker, not a filter: a vendor abroad that matches better still ranks above.",
        "Search returns links and snippets without fetching pages; a denylist, free heuristics and one cheap model call remove retailers and noise before any page is read. Each find is kept as platform data with its product pages crawled afterwards, so the next request from any company benefits.",
        "The page the search found is read for the product on it before the answer comes back — the vendor's SKU, the maker's part number and the maker, from the data shops publish for search engines, from labelled text, or from a short model read of that one page. The card says how the vendor lists the item and links to that product page, and that vendor's RFQ carries their number.",
        "Konyxions are gated behind buyer review by design: it is the quality gate, the deliverability gate and the legal gate in one."
      ],
      "fields": {
        "Outputs": [
          "candidate vendors with domain, contact and reasons",
          "the product on the page each was found on, with its part number, maker and a link to it",
          "an explainable confidence score",
          "their catalog, crawled in the background"
        ],
        "Where": "worldwide, localised to the buyer's country so nearby vendors come up first",
        "Buyer's country, in order": [
          "the requester's site, when it has a country",
          "the company's country (Settings; from the billing address at online sign-up; or set by Konyx staff)",
          "the country the request is made from, taken from the connection"
        ],
        "Never does": [
          "email a Konyxion automatically",
          "scrape a search engine directly",
          "leave out a vendor for being abroad"
        ]
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "control.discovered-vendors-reviewed",
        "use-cases.rush-part-no-supplier"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#vendor-discovery"
    },
    {
      "id": "capabilities.rfq",
      "domain": "capabilities",
      "slug": "rfq",
      "name": "One RFQ to all the vendors",
      "status": "live",
      "verifiedAt": "2026-10-27",
      "version": 6,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — RFQ page and send screen"
      },
      "summary": "A buyer drafts one request for quotation, sees the exact email each vendor will receive — subject, opening, note, deadline, the vendor's own quote link and their own part numbers — and presses Send. RFQs are never sent automatically: sending is a separate permission from drafting.",
      "body": [
        "Each recipient's copy is rendered on its own, so the greeting, the reply address and the item numbers differ per vendor. A vendor's emailed reply always reaches a person: it comes back onto the RFQ where Konyx's reply address is switched on, and otherwise goes to the team's own inbox or to whoever sent the RFQ — by company setting, and never to an address nobody reads. An RFQ that bounces shows on the vendor's row with the reason, and Send retries only that vendor once the address is fixed. A draft can be deleted while nothing has gone to a vendor.",
        "A request has one draft at a time: choosing other vendors changes that draft rather than starting another. The request stays with the buyer while the RFQ is a draft and reads RFQ sent once it has gone out.",
        "Every item table reads: item number (that vendor's own code), item, description, manufacturer, quantity — the way a vendor identifies a part. When the request names no maker, each vendor sees the one they list the item under.",
        "A company can set a standard opening paragraph in Settings, so every RFQ it sends starts with the same words; one RFQ can still be reworded before it goes. The reply-by date is never lost: when the opening does not state it, it follows as a sentence of its own.",
        "Every RFQ — the email and the vendor's quote page — carries Konyx's referral code, KONYX, in a box beside the logo, so a supplier can tell the request came through Konyx.",
        "Drafting RFQs comes with Starter and up; sending them comes with Growth and up. On Starter the draft and its email can be read and changed, but nothing goes out to a vendor and no quote link is handed out. The Search plan has no RFQs: Ask Konyx finds the vendors, with their contact details, and the buyer contacts them directly."
      ],
      "fields": {
        "Plans": [
          "drafting: Starter, Growth, Professional, Enterprise",
          "sending: Growth, Professional, Enterprise",
          "Search: no RFQs — vendor search only"
        ],
        "Send from": [
          "Konyx",
          "the buyer's own mailbox, via their mail app"
        ],
        "Opening": [
          "the RFQ's own words",
          "the company's standard paragraph",
          "Konyx's wording"
        ],
        "Referral code": "KONYX, beside the logo on every RFQ",
        "Replies to": [
          "the RFQ in Konyx, with a copy to the buyer",
          "the team's own inbox",
          "the person who sent it"
        ],
        "Permission": "rfq.send, separate from rfq.create"
      },
      "audiences": [
        "buyers"
      ],
      "related": [
        "capabilities.own-email-sending",
        "capabilities.vendor-quote-portal",
        "capabilities.email-replies",
        "control.person-presses-send",
        "use-cases.supplier-part-numbers"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#rfq"
    },
    {
      "id": "capabilities.own-email-sending",
      "domain": "capabilities",
      "slug": "own-email-sending",
      "name": "Sending from the buyer's own email",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — send screen, mailto mode"
      },
      "summary": "An RFQ can go out from the buyer's own mailbox instead of a Konyx address. Konyx prepares each vendor's message and the buyer sends it from their own mail app, then ticks the recipients they sent; quotes still come back through the vendor's link.",
      "body": [
        "Some plants must send from their own domain by policy, and a message from procurement at the customer's own domain lands better than one from a platform. A per-company default chooses the mode; the send screen can switch it.",
        "It is a way of sending, so it comes with the plans that send RFQs: Growth and up."
      ],
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "capabilities.rfq",
        "integrations.email",
        "use-cases.send-from-own-domain"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#own-email-sending"
    },
    {
      "id": "capabilities.vendor-quote-portal",
      "domain": "capabilities",
      "slug": "vendor-quote-portal",
      "name": "The vendor's quote link",
      "status": "live",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — portal pages; konyx-api — portal"
      },
      "summary": "Vendors answer an RFQ through a link in the email — no account, no login. They price each line, state lead time and terms, and can revise; every revision is kept, never overwritten.",
      "body": [
        "The link is unique to the vendor and the RFQ and is rate-limited. Quotes land in Konyx as comparable lines the moment they are submitted."
      ],
      "audiences": [
        "vendors",
        "buyers"
      ],
      "related": [
        "capabilities.quote-comparison",
        "faq.vendor-account"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#vendor-quote-portal"
    },
    {
      "id": "capabilities.quote-comparison",
      "domain": "capabilities",
      "slug": "quote-comparison",
      "name": "Quotes side by side",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — quote comparison grid"
      },
      "summary": "Quotes come back into one grid: every vendor's price per line, the lowest highlighted, beside what the company last paid. The buyer compares them and picks the winning lines.",
      "body": [
        "Lines are compared as lines, not as documents, so a partial quote and a full one sit in the same table. On a phone the grid stacks into labelled cards."
      ],
      "audiences": [
        "buyers",
        "finance"
      ],
      "related": [
        "capabilities.bought-before",
        "capabilities.vendor-quote-portal",
        "how-it-works.compare-and-order"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#quote-comparison"
    },
    {
      "id": "capabilities.request-routing",
      "domain": "capabilities",
      "slug": "request-routing",
      "name": "Routing, escalation, notes and notifications",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/request-state.ts, core/approver.ts, core/notify.ts"
      },
      "summary": "A request moves through an eleven-state lifecycle behind one guarded transition function. Someone who cannot source it themselves sends it up the supervisor chain to the first person who holds the needed permission; notes travel with the request; a bell announces anything that happens to yours.",
      "body": [
        "Escalation is mechanical: the first person up the chain with the permission, then any holder, the owner last — so a request cannot dead-end because a direct manager lacks the right. The requester can amend a request from Ask Konyx while nothing has gone to a vendor.",
        "Notifications are written in the same transaction as the thing they announce — a request sent to you, a note, a change, a quote back."
      ],
      "fields": {
        "States": "eleven, with an explicit allowed-transition map",
        "Notes": "plain messages between the requester and whoever the request is with",
        "Bell": "polled every 45 seconds and on focus; no sockets"
      },
      "audiences": [
        "technicians",
        "buyers"
      ],
      "related": [
        "capabilities.roles-and-permissions",
        "use-cases.employee-cannot-send",
        "use-cases.tracking-a-request"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#request-routing"
    },
    {
      "id": "capabilities.roles-and-permissions",
      "domain": "capabilities",
      "slug": "roles-and-permissions",
      "name": "Roles and permissions",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-api — authz; 26 permissions"
      },
      "summary": "Each company defines its own roles from 26 hard-coded permission toggles. A person holds the union of their roles; the owner holds everything. Requesting, drafting an RFQ and sending it are separate permissions.",
      "body": [
        "That matches how procurement delegates: an administrator grants one maintenance lead the right to send RFQs without promoting them. Default roles come with every company, including Procurement and a built-in Super user, and can be cloned and changed."
      ],
      "fields": {
        "Permissions": "26, as a closed list checked on every API call",
        "Examples": [
          "request.create",
          "rfq.create",
          "rfq.send",
          "vendor.discover",
          "request.assign"
        ]
      },
      "audiences": [
        "IT and security",
        "buyers"
      ],
      "related": [
        "control.permissions-on-every-call",
        "capabilities.request-routing"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#roles-and-permissions"
    },
    {
      "id": "capabilities.activity-log",
      "domain": "capabilities",
      "slug": "activity-log",
      "name": "The activity log",
      "status": "live",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/audit.ts"
      },
      "summary": "Every action — who, what, when — is written to an append-only log in the same transaction as the change, and shown in plain sentences on the request, the person and the company.",
      "body": [
        "The log is append-only at the database level, not by convention. Changes made by Konyx staff through the console are written as done by Konyx, so a company can always see what its vendor did."
      ],
      "audiences": [
        "IT and security",
        "finance"
      ],
      "related": [
        "control.append-only-audit"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#activity-log"
    },
    {
      "id": "capabilities.savings-audit",
      "domain": "capabilities",
      "slug": "savings-audit",
      "name": "The savings audit",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-admin — Audit page; konyx-api — core/savings-analysis.ts"
      },
      "summary": "From one export of a company's purchasing history, Konyx computes what it would have saved: price gaps against the company's own best price and the Konyx network, cycle time, late deliveries, quote competition, rush and card spend, and buyer hours — then writes the findings up as a five-page report.",
      "body": [
        "Every figure is computed in code from the file; the model only writes the narrative from those figures. The audit runs before any contract and is how a pilot's baseline is set. It is prepared by Konyx staff from the company's file, not self-served."
      ],
      "fields": {
        "Input": "one CSV of past purchases, a row per purchase or per line, any column names — mapping is confirmed on screen",
        "Outputs": [
          "money: price gaps and where they are",
          "buyer hours and calendar days, manual process versus Konyx",
          "findings, price gaps, vendors, method",
          "a PDF report"
        ]
      },
      "audiences": [
        "finance",
        "buyers"
      ],
      "related": [
        "pilot.baseline",
        "proof.savings-audit-method"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#savings-audit"
    },
    {
      "id": "capabilities.time-saved",
      "domain": "capabilities",
      "slug": "time-saved",
      "name": "Time saved, RFQ by RFQ",
      "status": "live",
      "verifiedAt": "2026-10-01",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/time-saved.ts; konyx-erp — Time saved page; konyx-admin — Time saved"
      },
      "summary": "For every RFQ that goes out, Konyx sets what it would have taken a buyer by hand against the time it actually took in Konyx — per RFQ, per company and across the platform. By hand is estimated step by step from the RFQ's own items, vendors, new vendors and quoted lines; in Konyx is measured from the recorded steps, with idle time capped.",
      "body": [
        "In Konyx runs from the first thing the person asked Konyx for the request to the moment the RFQ went out, adding the time between each recorded step — model calls and every logged action. A pause longer than ten minutes counts as ten, so a draft left overnight is not counted as a night's work. The clock time from first question to sent is shown beside it.",
        "By hand counts only the steps that applied: going back to the requester for details, checking stock and past prices per item, finding each vendor (a vendor new to the company takes longer than one on file), writing the RFQ and typing each item, emailing each vendor, retyping each quoted line that came back through the vendor's link, and laying two or more quotes side by side. The minutes per step are set by Konyx for every company and listed on the page; nothing is estimated by a model.",
        "A company's people with the analytics permission see the Time saved page and a line on their overview; anyone who can read RFQs sees the figure on each sent RFQ. Konyx staff see every company and the platform total, and set the minutes."
      ],
      "fields": {
        "Measured": [
          "time in Konyx, first question to sent, idle capped at 10 minutes",
          "clock time, first question to sent"
        ],
        "Estimated per RFQ (built-in minutes)": [
          "clarify the request: 10 per request",
          "stock and past prices: 4 per item",
          "vendor on file: 5 each",
          "new vendor: 30 each",
          "write the RFQ: 10, plus 3 per item",
          "email each vendor: 4",
          "retype a quoted line: 2",
          "compare two or more quotes: 10"
        ],
        "Also shown": [
          "value of the time at a buyer's hourly cost, $45 by default",
          "medians per RFQ, both ways",
          "where the by-hand minutes would have gone"
        ]
      },
      "audiences": [
        "buyers",
        "finance"
      ],
      "related": [
        "proof.savings-audit-method",
        "capabilities.rfq",
        "proof.customer-results"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#time-saved"
    },
    {
      "id": "capabilities.data-import",
      "domain": "capabilities",
      "slug": "data-import",
      "name": "Bringing vendors, catalogs and people in",
      "status": "live",
      "verifiedAt": "2026-10-27",
      "version": 4,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — vendor import, team import"
      },
      "summary": "Vendors and their catalogs come in from one spreadsheet, with contacts; columns are mapped with the model's help and confirmed on screen; every problem row is shown before anything is committed, per vendor; an import can be undone as a unit. The team comes in from a five-column CSV with invitation links.",
      "body": [
        "Each row is judged after it is chosen, by its content rather than its file label, so a phone can pick the file and an Excel workbook gets a clear ask to save as CSV. A test set of 20 vendors and 6,600 catalog rows lands in about six seconds.",
        "Uploading the company's own vendor file — its own vendor database — comes with Professional and Enterprise. On Search, Starter and Growth, vendors are added one at a time, and come from the Konyx network and Konyxions; an earlier upload can still be undone."
      ],
      "fields": {
        "Vendor file plans": "Professional, Enterprise",
        "Vendor file": "one CSV: vendor, contacts, item, part number, price ladder",
        "Team file": "ID, Name, Email, Role, Manager",
        "Purchase history": "any export of past purchases, mapped on screen — used by the savings audit and for last-paid prices",
        "Planned": [
          "inventory",
          "open orders from the company's ERP",
          "contracts"
        ]
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "integrations.spreadsheets",
        "pilot.adoption"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#data-import"
    },
    {
      "id": "capabilities.plan-limits",
      "domain": "capabilities",
      "slug": "plan-limits",
      "name": "Plan limits per company",
      "status": "live",
      "verifiedAt": "2026-10-27",
      "version": 5,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/limits.ts, billing/plans.ts"
      },
      "summary": "Each company has limits: how many RFQs it may create in a month, or on the Search plan how many searches it may make (a plan bought online counts by billing month, from the day the plan renews; a company Konyx sets up counts by calendar month), how many items one RFQ may carry, how many people may hold an account, and what it can do beyond searching for vendors: draft RFQs, send them, and upload its own vendor database. A plan bought online sets the RFQs per month, or the searches per month on Search — counted for the whole company, whoever creates or asks them — and what the company can do, and has no per-person pricing. They are enforced in the API and shown to the company under Settings → Plan and billing.",
      "body": [
        "On the Search plan the count is of searches, not RFQs. One new request asked of Ask Konyx counts once, for the whole company, whoever asks; the answers to Konyx's follow-up questions on that request, and its Konyxions, are part of the same search. The count runs per billing month and starts again when the plan renews. When the 25 are used, Ask Konyx says so and a super user can move to a bigger plan under Settings → Plan and billing. Only Search counts searches: the other plans count RFQs and do not limit searches.",
        "A company whose plan has ended keeps everything it has in Konyx, but no new RFQ can be created or sent — and on Search, Ask Konyx can't search for vendors — until a plan is chosen again. A failed payment changes nothing for seven days while Stripe retries the card; after that, or as soon as Stripe stops trying, the plan ends. A payment disputed with the bank, or reported as possibly unauthorised, stops the plan at once until Konyx lifts the hold. Each of these is emailed to the company's super users."
      ],
      "fields": {
        "Plans bought online": [
          "Search: 25 searches per month — vendor search only: no RFQs drafted or sent — no free trial",
          "Starter: 25 RFQs per month — vendor search and RFQ drafts — the first 14 days free for a company that signs up online",
          "Growth: 50 RFQs per month — adds RFQ sending",
          "Professional: 250 RFQs per month — adds the company's own vendor database"
        ],
        "A search": "one new request asked of Ask Konyx, counted once for the whole company; its follow-up answers and Konyxions are part of it; counted on Search only",
        "Items per RFQ": "30",
        "People": "no per-person limit on a plan bought online",
        "Companies Konyx sets up": "limits and switches for RFQ sending and the vendor upload set from the console (defaults: 5 people, 250 RFQs per month, 30 items per RFQ, both on); every change is written to the company's log"
      },
      "audiences": [
        "finance",
        "IT and security"
      ],
      "related": [
        "faq.pricing",
        "capabilities.online-signup"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#plan-limits"
    },
    {
      "id": "capabilities.online-signup",
      "domain": "capabilities",
      "slug": "online-signup",
      "name": "Buying a plan online",
      "status": "live",
      "verifiedAt": "2026-10-27",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-api — billing; konyx-erp — /signup"
      },
      "summary": "A company can start on its own: choose a plan on konyxai.com — Search, Starter, Growth or Professional — enter a name, work email, company name and password, confirm the email with a six-digit code, and enter a card on Stripe's page. Starter starts with 14 days free; Search, Growth and Professional are charged straight away. The company is created as soon as Stripe's page is completed, with that person as its super user, signed straight in.",
      "body": [
        "Card details are entered on Stripe's own page and never reach Konyx. A super user changes plan from Settings → Plan and billing (the difference is settled on the next invoice) — a company on Search moves to Starter or above there to add RFQ drafts — and updates the card, downloads invoices or cancels on Stripe's billing page, reached from the same place; a cancelled plan runs to the end of the month paid for. The company's country is filled in from the billing address entered there and can be changed in Settings.",
        "Starter's free trial: the card is entered on Stripe's payment page at sign-up and nothing is charged during the first 14 days. On day 15 Starter is charged at $99 a month, unless the plan was cancelled before then — Settings → Plan and billing → Card and invoices opens Stripe's billing page, where it can be ended. Moving up to Growth or Professional during the trial ends it, and that plan is charged straight away. Search, Growth and Professional have no trial, and a company whose plan ended and that chooses a plan again does not get another one.",
        "An email address that already has a Konyx account cannot start a second company; the person is told by email, and the sign-up page says the same thing to everyone. Enterprise plans are arranged with Konyx and set up from the console."
      ],
      "fields": {
        "Plans": [
          "Search: $29 a month — 25 searches per month",
          "Starter: $99 a month — 25 RFQs per month",
          "Growth: $249 a month — 50 RFQs per month",
          "Professional: $499 a month — 250 RFQs per month",
          "Enterprise: arranged with Konyx"
        ],
        "Steps": [
          "choose a plan",
          "name, work email, company, password",
          "six-digit email code",
          "card on Stripe's page — charged now, or on day 15 for Starter",
          "company created, signed in as super user"
        ],
        "Free trial": "Starter only: 14 days, nothing charged, then $99 a month unless cancelled before day 15; once per company",
        "Payment": "monthly, by card, through Stripe",
        "Change or cancel": "Settings → Plan and billing"
      },
      "audiences": [
        "finance",
        "buyers",
        "IT and security"
      ],
      "related": [
        "faq.pricing",
        "capabilities.plan-limits"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#online-signup"
    },
    {
      "id": "capabilities.approval-rules",
      "domain": "capabilities",
      "slug": "approval-rules",
      "name": "Approval rules and the simulator",
      "status": "planned",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.7, Next"
      },
      "summary": "Approval rules that route a purchase or an RFQ for approval by amount, category or exception, with a simulator that shows who would approve a given one before the rule goes live. Not shipped yet; today the control is the permissions a company gives its roles, such as who may send an RFQ.",
      "audiences": [
        "finance",
        "buyers"
      ],
      "related": [
        "capabilities.roles-and-permissions",
        "control.person-presses-send"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#approval-rules"
    },
    {
      "id": "capabilities.email-replies",
      "domain": "capabilities",
      "slug": "email-replies",
      "name": "Vendor replies by email, on the RFQ",
      "status": "live",
      "verifiedAt": "2026-10-02",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/inbound-mail.ts, email/inbound.ts; konyx-erp — RFQ page, Replies by email"
      },
      "summary": "When a vendor answers an RFQ by email instead of using the quote link, the message appears on that RFQ exactly as they wrote it — their words, the address it really came from, their files, and the original to download — and a copy goes to the buyer's inbox. Where an installation has not switched Konyx's reply address on, the reply goes to the team's inbox or the sender instead.",
      "body": [
        "Each vendor on an RFQ gets a reply address of their own, so a reply is matched to the right RFQ and vendor even when a colleague answers from a different address. The page says whether the sender is the address on file, someone at the same company, or unknown, and whether the sending mail server passed the usual checks; an unknown or unverified sender carries a plain warning before anything is acted on.",
        "The message is shown as plain text, in full, never as a summary. A model may add one label from a fixed list — looks like a quote, a decline, a question, asks for a call — as a hint beside the message; it cannot write text onto the page or change a price, a status or anything else. Out-of-office and automatic replies are recognised from the mail's own headers.",
        "A reply's prices are not read into the quote comparison: quotes are compared when a vendor fills in their quote link."
      ],
      "fields": {
        "Kept from each reply": [
          "the text exactly as written",
          "files up to 10 MB each",
          "the original message"
        ],
        "Not kept": [
          "programs, scripts, web pages and macro files"
        ],
        "The buyer is told": [
          "on the RFQ",
          "in the app's notifications",
          "by email, with a reply that goes straight to the vendor"
        ]
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "capabilities.rfq",
        "capabilities.vendor-quote-portal",
        "control.outside-email",
        "integrations.email"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#email-replies"
    },
    {
      "id": "capabilities.email-quote-capture",
      "domain": "capabilities",
      "slug": "email-quote-capture",
      "name": "Quotes read out of an email",
      "status": "planned",
      "verifiedAt": "2026-10-02",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.6"
      },
      "summary": "Reading the prices out of a vendor's emailed PDF or spreadsheet into the quote comparison, as a fallback to the quote link. Not shipped: an emailed reply is shown on the RFQ as written, but its prices are not extracted; quotes are compared when they come back through the link.",
      "audiences": [
        "buyers"
      ],
      "related": [
        "capabilities.email-replies",
        "capabilities.vendor-quote-portal",
        "integrations.email"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#email-quote-capture"
    },
    {
      "id": "capabilities.mailbox-connectors",
      "domain": "capabilities",
      "slug": "mailbox-connectors",
      "name": "Sending through Microsoft 365 or Gmail",
      "status": "planned",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — Next"
      },
      "summary": "Sending RFQs through the buyer's mailbox by API, so they appear in Sent without the buyer's mail app being involved. Not shipped; own-email sending works today through the buyer's mail app.",
      "audiences": [
        "IT and security",
        "buyers"
      ],
      "related": [
        "capabilities.own-email-sending",
        "integrations.mailbox-connectors"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#mailbox-connectors"
    },
    {
      "id": "capabilities.native-mobile-app",
      "domain": "capabilities",
      "slug": "native-mobile-app",
      "name": "A native mobile app",
      "status": "not-offered",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — Scope decisions"
      },
      "summary": "There is no iOS or Android app. The web application is built phone-first — voice, photos and the request draft all work in a phone browser — and nothing in the product requires an installed app.",
      "audiences": [
        "technicians",
        "IT and security"
      ],
      "related": [
        "capabilities.ask-konyx",
        "faq.phones"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#native-mobile-app"
    },
    {
      "id": "capabilities.autonomous-purchasing",
      "domain": "capabilities",
      "slug": "autonomous-purchasing",
      "name": "Autonomous purchasing",
      "status": "not-offered",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.7, decision log"
      },
      "summary": "Konyx never sends an RFQ or awards a quote on its own. The AI interprets and prepares; a named person with the permission releases every send, and the buyer picks the winning quote. This is a design decision, not a missing feature.",
      "audiences": [
        "finance",
        "IT and security"
      ],
      "related": [
        "control.person-presses-send",
        "company.principles"
      ],
      "url": "https://konyxai.com/knowledge/capabilities#autonomous-purchasing"
    },
    {
      "id": "how-it-works.overview",
      "domain": "how-it-works",
      "slug": "overview",
      "name": "Four steps, a person at each one",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — How it works"
      },
      "summary": "Ask: a technician says what is needed and Konyx drafts the request from the catalog and history. Route: it goes to whoever may act on it. Send the RFQ: the buyer reviews every line and the email itself, then sends. Compare and choose: quotes come back into one grid and the buyer picks the winner.",
      "body": [
        "The AI interprets and prepares; people decide. That is what makes the product usable in a plant and defensible in a security review."
      ],
      "related": [
        "how-it-works.ask",
        "how-it-works.route",
        "how-it-works.send-the-rfq",
        "how-it-works.compare-and-order",
        "how-it-works.what-the-ai-does"
      ],
      "url": "https://konyxai.com/knowledge/how-it-works#overview"
    },
    {
      "id": "how-it-works.ask",
      "domain": "how-it-works",
      "slug": "ask",
      "name": "Step 1 — Ask",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — Ask Konyx"
      },
      "summary": "A technician says what is needed, from the floor — a sentence, a voice note, a photo of the nameplate or a spreadsheet. Konyx reads it, checks the company's catalog and purchase history, and drafts the request with any open questions.",
      "body": [
        "The person confirms the draft. Each field shows whether it was confirmed, inferred or unknown; the person can change any of it. Only then does a request exist."
      ],
      "related": [
        "capabilities.ask-konyx",
        "capabilities.catalog-matching"
      ],
      "url": "https://konyxai.com/knowledge/how-it-works#ask"
    },
    {
      "id": "how-it-works.route",
      "domain": "how-it-works",
      "slug": "route",
      "name": "Step 2 — Route",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — request lifecycle"
      },
      "summary": "The request goes to whoever may act on it. A buyer sources it directly; a requester who cannot sends it to a supervisor — the first person up the chain with the permission. Notes go back and forth on the request, and it can be corrected before anything is sent.",
      "related": [
        "capabilities.request-routing",
        "capabilities.roles-and-permissions"
      ],
      "url": "https://konyxai.com/knowledge/how-it-works#route"
    },
    {
      "id": "how-it-works.send-the-rfq",
      "domain": "how-it-works",
      "slug": "send-the-rfq",
      "name": "Step 3 — Send the RFQ",
      "verifiedAt": "2026-10-07",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — RFQ send screen"
      },
      "summary": "Vendors are ranked with reasons: the company's own first, then the Konyx network, then Konyxions — vendors Konyx found on the web. The buyer picks, reviews every line and the exact email each vendor will receive, ticks the review box, and sends — from Konyx or from their own mailbox.",
      "related": [
        "capabilities.vendor-ranking",
        "capabilities.rfq",
        "control.person-presses-send"
      ],
      "url": "https://konyxai.com/knowledge/how-it-works#send-the-rfq"
    },
    {
      "id": "how-it-works.compare-and-order",
      "domain": "how-it-works",
      "slug": "compare-and-order",
      "name": "Step 4 — Compare and choose",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — comparison grid"
      },
      "summary": "Vendors quote through their link. Quotes land as comparable lines in one grid, the lowest per line highlighted beside the last price paid. The buyer picks the winning lines; every step is on the request's timeline.",
      "related": [
        "capabilities.quote-comparison",
        "capabilities.vendor-quote-portal"
      ],
      "url": "https://konyxai.com/knowledge/how-it-works#compare-and-order"
    },
    {
      "id": "how-it-works.what-the-ai-does",
      "domain": "how-it-works",
      "slug": "what-the-ai-does",
      "name": "What the AI does, and what it never does",
      "verifiedAt": "2026-10-26",
      "version": 4,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.8"
      },
      "summary": "The AI reads a request into structure, asks the clarifying question, helps map spreadsheet columns, classifies web search results, checks that a network vendor's product is the item asked for, and writes the savings-audit narrative from figures computed in code. It never sends anything, never picks the winning quote, and is never the system of record.",
      "body": [
        "Confidence is not the model's opinion: it is computed from which fields were confirmed, inferred or unknown. Every model call is recorded — who asked, which prompt version, what it cost — and shown per company in the console. Prompts are versioned files; a change is a new version, never an edit.",
        "Matching a request to the company's own catalog, finding what was paid last time and ranking vendors are database queries, not model calls. They cost nothing, run in milliseconds and cannot invent a part. Products from the Konyx network and Konyxions are found the same way, then checked once by a small model call before a vendor is said to carry them; that check can only confirm or drop what the query found, never add a vendor or a part."
      ],
      "fields": {
        "Model calls": [
          "request extraction",
          "clarifying questions",
          "column mapping for imports",
          "filtering web search results",
          "reading product pages of vendors found on the web",
          "checking that a network vendor's product is the item asked for",
          "the audit narrative"
        ],
        "Never a model call": [
          "matching the company's own catalog",
          "purchase history lookup",
          "vendor ranking",
          "sending",
          "state changes"
        ]
      },
      "audiences": [
        "IT and security",
        "finance"
      ],
      "related": [
        "faq.ai-models",
        "control.ai-provenance",
        "company.principles"
      ],
      "url": "https://konyxai.com/knowledge/how-it-works#what-the-ai-does"
    },
    {
      "id": "use-cases.no-part-number",
      "domain": "use-cases",
      "slug": "no-part-number",
      "name": "The technician does not know the part number",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — Ask Konyx with photos"
      },
      "summary": "Problem: a coupling has failed and the technician knows the machine, not the part. Konyx: they photograph the nameplate or the part and say what it is for; Konyx drafts the line, asks the one question that matters (size, material, seal type — with answers to tap), matches it against the catalog and purchase history, and ranks the vendors who carry it.",
      "body": [
        "What the buyer receives is a structured request with the catalog match, the last price paid and the candidate vendors — not a phone call to decode."
      ],
      "audiences": [
        "technicians",
        "buyers"
      ],
      "related": [
        "capabilities.ask-konyx",
        "capabilities.catalog-matching"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#no-part-number"
    },
    {
      "id": "use-cases.supplier-part-numbers",
      "domain": "use-cases",
      "slug": "supplier-part-numbers",
      "name": "The same gasket has a different number at every supplier",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/supplier-part.ts"
      },
      "summary": "Problem: one gasket is 101-100-234 at one distributor and LSV-BV-200 at the next; a request with the wrong code gets the wrong part quoted. Konyx: each vendor's copy of the RFQ carries that vendor's own item number, resolved from the item master, a lead list, that vendor's catalog or — for a vendor found on the web — their own product page, and left blank when there is no confident match.",
      "body": [
        "The manufacturer's part number sits under the manufacturer on every RFQ, so nothing is lost."
      ],
      "audiences": [
        "buyers",
        "vendors"
      ],
      "related": [
        "capabilities.rfq",
        "capabilities.catalog-matching"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#supplier-part-numbers"
    },
    {
      "id": "use-cases.rush-part-no-supplier",
      "domain": "use-cases",
      "slug": "rush-part-no-supplier",
      "name": "A rush part with no known supplier",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/discovery"
      },
      "summary": "Problem: a niche part nobody on the vendor list carries, and the line is down. Konyx: after the company's own vendors and the Konyx network have answered, it searches the web, reads the candidates' contact pages, and shows them as Konyxions with contacts, reasons, a score and a link to each matching product on the vendor's site. Konyxions are looked for worldwide, starting in the buyer's own country, so a nearby distributor comes up first and one abroad still appears. The buyer checks the product, picks who to ask; nothing is emailed until they do.",
      "audiences": [
        "buyers"
      ],
      "related": [
        "capabilities.vendor-discovery",
        "control.discovered-vendors-reviewed"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#rush-part-no-supplier"
    },
    {
      "id": "use-cases.last-paid-price",
      "domain": "use-cases",
      "slug": "last-paid-price",
      "name": "What did we pay last time?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/purchase-context.ts"
      },
      "summary": "Problem: a quote arrives and nobody has the last invoice to hand, so it is accepted as it is. Konyx: the price paid last time — from imported history, earlier quotes and earlier requests — sits under the request line and beside every quoted line, and the contract price appears where a contract exists.",
      "audiences": [
        "buyers",
        "finance"
      ],
      "related": [
        "capabilities.bought-before",
        "capabilities.quote-comparison"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#last-paid-price"
    },
    {
      "id": "use-cases.quotes-in-pdfs",
      "domain": "use-cases",
      "slug": "quotes-in-pdfs",
      "name": "Quotes come back as PDFs and email threads",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — vendor portal and comparison grid"
      },
      "summary": "Problem: six vendors answer in six formats and the buyer retypes them into a spreadsheet to compare. Konyx: vendors price each line through a no-login link, quotes land as comparable lines in one grid with the lowest highlighted, and revisions are kept rather than overwritten.",
      "audiences": [
        "buyers",
        "vendors"
      ],
      "related": [
        "capabilities.vendor-quote-portal",
        "capabilities.quote-comparison"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#quotes-in-pdfs"
    },
    {
      "id": "use-cases.employee-cannot-send",
      "domain": "use-cases",
      "slug": "employee-cannot-send",
      "name": "An employee who may raise a request but not send an RFQ",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — permissions and escalation"
      },
      "summary": "Problem: the plant wants anyone to be able to ask for a part, but only procurement to talk to vendors. Konyx: request.create and rfq.send are separate permissions. An employee's request routes to the first person up their supervisor chain who can act; an employee calling the RFQ endpoint directly gets a refusal, not a hidden button.",
      "audiences": [
        "IT and security",
        "buyers"
      ],
      "related": [
        "capabilities.roles-and-permissions",
        "capabilities.request-routing"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#employee-cannot-send"
    },
    {
      "id": "use-cases.send-from-own-domain",
      "domain": "use-cases",
      "slug": "send-from-own-domain",
      "name": "Vendors must hear from the plant's own domain",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — own-email sending"
      },
      "summary": "Problem: policy or vendor relationships require RFQs to come from procurement at the company's own address. Konyx: the buyer switches the send screen to their own email; Konyx prepares each vendor's message, the buyer sends it from their mail app and ticks who they sent; the record shows it and the quotes still come back through the link.",
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "related": [
        "capabilities.own-email-sending",
        "integrations.email"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#send-from-own-domain"
    },
    {
      "id": "use-cases.business-case-before-contract",
      "domain": "use-cases",
      "slug": "business-case-before-contract",
      "name": "Proving the case before signing anything",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-admin — Audit page"
      },
      "summary": "Problem: finance wants a number before a pilot, and vendor claims are not evidence. Konyx: the company sends one export of its purchasing history; Konyx computes the price gaps, cycle times and buyer hours from that file and writes the findings up. The baseline is the company's own data, before any contract.",
      "audiences": [
        "finance"
      ],
      "related": [
        "capabilities.savings-audit",
        "pilot.baseline",
        "proof.savings-audit-method"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#business-case-before-contract"
    },
    {
      "id": "use-cases.spreadsheet-of-parts",
      "domain": "use-cases",
      "slug": "spreadsheet-of-parts",
      "name": "A shutdown list of thirty lines in a spreadsheet",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — Ask Konyx with spreadsheets"
      },
      "summary": "Problem: a turnaround list arrives as a spreadsheet and each line would be a separate request. Konyx: drop the file into Ask Konyx; every row becomes a line on one request, matched against the catalog, with vendors ranked by how many of the lines they cover — then one RFQ goes to all of them.",
      "audiences": [
        "buyers",
        "technicians"
      ],
      "related": [
        "capabilities.ask-konyx",
        "capabilities.vendor-ranking",
        "capabilities.plan-limits"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#spreadsheet-of-parts"
    },
    {
      "id": "use-cases.tracking-a-request",
      "domain": "use-cases",
      "slug": "tracking-a-request",
      "name": "Where is my request?",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — request page, notes, notifications"
      },
      "summary": "Problem: the technician who asked for the part has to phone the buyer to find out what happened. Konyx: the request page shows where it is, who it is with and every step on its timeline; notes go back and forth on the request; the bell announces a note, a change or a quote; and the requester can change the request themselves before anything goes out.",
      "audiences": [
        "technicians"
      ],
      "related": [
        "capabilities.request-routing"
      ],
      "url": "https://konyxai.com/knowledge/use-cases#tracking-a-request"
    },
    {
      "id": "industries.refining",
      "domain": "industries",
      "slug": "refining",
      "name": "Refining",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Who it's for"
      },
      "industries": [
        "refining"
      ],
      "summary": "Refineries buy MRO parts under time pressure — turnarounds, unplanned outages, rush replacements for rotating equipment, valves and instrumentation — often against approved-vendor lists and contract pricing that the person raising the request never sees. Konyx puts the contract price, the last price paid and the approved vendors beside the request before it goes out.",
      "fields": {
        "Typical requests": [
          "valves by class, size and material",
          "pump and compressor spares",
          "gaskets and seals",
          "instrumentation",
          "safety consumables"
        ],
        "What matters": [
          "a rush part sourced at the right price, not the first price",
          "vendors who carry the exact manufacturer part",
          "an audit trail for every purchase"
        ]
      },
      "related": [
        "use-cases.rush-part-no-supplier",
        "use-cases.last-paid-price",
        "control.append-only-audit"
      ],
      "url": "https://konyxai.com/knowledge/industries#refining"
    },
    {
      "id": "industries.chemicals",
      "domain": "industries",
      "slug": "chemicals",
      "name": "Chemicals and petrochemicals",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Who it's for"
      },
      "industries": [
        "chemicals"
      ],
      "summary": "Chemical plants carry long catalogs of material-specific parts — the same valve in three alloys, the same seal in three elastomers — where an ambiguous request means the wrong part. Ask Konyx asks the material and size question up front with the usual answers to tap, and matching checks the manufacturer on both sides before it claims a part number.",
      "fields": {
        "Typical requests": [
          "alloy and lined valves",
          "seals and gaskets by elastomer",
          "pump parts",
          "filtration",
          "PPE and consumables"
        ]
      },
      "related": [
        "capabilities.ask-konyx",
        "capabilities.catalog-matching",
        "use-cases.supplier-part-numbers"
      ],
      "url": "https://konyxai.com/knowledge/industries#chemicals"
    },
    {
      "id": "industries.lng-and-energy",
      "domain": "industries",
      "slug": "lng-and-energy",
      "name": "LNG and energy",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Who it's for"
      },
      "industries": [
        "LNG and energy"
      ],
      "summary": "Energy sites are often remote and vendor-poor for niche parts, and lead time is the cost that matters. When the company's own list has no vendor for the part, Konyx finds Konyxions — vendors who carry it, looked for worldwide and starting in the site's own country when the site has one in Konyx — and the quote grid shows lead time beside price so the buyer can trade one for the other on purpose.",
      "fields": {
        "What matters": [
          "lead time as a first-class figure",
          "finding a distributor for an unusual part",
          "one RFQ to several vendors at once"
        ]
      },
      "related": [
        "capabilities.vendor-discovery",
        "capabilities.quote-comparison"
      ],
      "url": "https://konyxai.com/knowledge/industries#lng-and-energy"
    },
    {
      "id": "industries.aerospace",
      "domain": "industries",
      "slug": "aerospace",
      "name": "Aerospace and precision manufacturing",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Who it's for"
      },
      "industries": [
        "aerospace"
      ],
      "summary": "Aerospace suppliers buy tooling, consumables and indirect materials under documentation discipline: who approved what, which vendor, which part number, when. Konyx separates drafting an RFQ from sending it, records every step in an append-only log, and puts each vendor's own part number on the RFQ that vendor receives.",
      "related": [
        "capabilities.roles-and-permissions",
        "capabilities.activity-log",
        "use-cases.supplier-part-numbers"
      ],
      "url": "https://konyxai.com/knowledge/industries#aerospace"
    },
    {
      "id": "industries.mills",
      "domain": "industries",
      "slug": "mills",
      "name": "Mills — pulp and paper, steel",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Who it's for"
      },
      "industries": [
        "mills"
      ],
      "summary": "Mills run continuous processes with heavy rotating equipment; bearings, couplings, belts and drives are bought again and again from a handful of distributors. Konyx turns that repetition into an advantage: the catalog match, the last price paid and the vendor ranking are all built from the mill's own history.",
      "fields": {
        "Typical requests": [
          "bearings and housings",
          "couplings",
          "belts and drives",
          "gearbox spares",
          "conveyor parts"
        ]
      },
      "related": [
        "capabilities.bought-before",
        "capabilities.vendor-ranking"
      ],
      "url": "https://konyxai.com/knowledge/industries#mills"
    },
    {
      "id": "industries.general-manufacturing",
      "domain": "industries",
      "slug": "general-manufacturing",
      "name": "General manufacturing and MRO",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — Purpose"
      },
      "industries": [
        "general manufacturing"
      ],
      "summary": "Any plant with a maintenance store, a vendor list and a buyer who chases quotes by email has the problem Konyx solves. The product needs no ERP connector to start: vendors and catalogs come in from one spreadsheet, the team from another, and purchase history from an export.",
      "related": [
        "capabilities.data-import",
        "pilot.shape",
        "integrations.erp"
      ],
      "url": "https://konyxai.com/knowledge/industries#general-manufacturing"
    },
    {
      "id": "faq.replace-erp",
      "domain": "faq",
      "slug": "replace-erp",
      "name": "Does Konyx replace our ERP?",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot defaults"
      },
      "audiences": [
        "finance",
        "IT and security"
      ],
      "summary": "No. The ERP stays the system of record for orders and money; Konyx owns the work before the order — the request, sourcing, the RFQ, the quotes and the decision. There are no live ERP connectors in the current version; data comes in by spreadsheet export.",
      "related": [
        "company.how-konyx-differs",
        "integrations.erp"
      ],
      "url": "https://konyxai.com/knowledge/faq#replace-erp"
    },
    {
      "id": "faq.auto-send",
      "domain": "faq",
      "slug": "auto-send",
      "name": "Does the AI send anything on its own?",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — decision log"
      },
      "audiences": [
        "finance",
        "IT and security"
      ],
      "summary": "No. Konyx never sends an RFQ or awards a quote automatically. The AI reads and drafts; a named person with the permission reviews the exact email and presses Send, and the buyer picks the winning quote.",
      "related": [
        "control.person-presses-send",
        "capabilities.autonomous-purchasing"
      ],
      "url": "https://konyxai.com/knowledge/faq#auto-send"
    },
    {
      "id": "faq.data-isolation",
      "domain": "faq",
      "slug": "data-isolation",
      "name": "How is our data kept separate from other companies'?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.1"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "Each company's rows are isolated by row-level security in the database itself, enforced below the application: every tenant-scoped table has a forced policy, the application connects as a role that cannot bypass it, and an automated check fails the build if a table is missing its policy. Konyx staff manage a company through the same permission wall its own people use — never through a database console.",
      "related": [
        "control.tenant-isolation",
        "control.architecture"
      ],
      "url": "https://konyxai.com/knowledge/faq#data-isolation"
    },
    {
      "id": "faq.hosting",
      "domain": "faq",
      "slug": "hosting",
      "name": "Where does Konyx run?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "DEPLOY.md"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "The API and the database run on Google Cloud in the United States; the web applications and the public site run on Cloudflare. The browser never talks to the API directly — only the web application's own backend does, with a key the browser never holds.",
      "related": [
        "control.architecture"
      ],
      "url": "https://konyxai.com/knowledge/faq#hosting"
    },
    {
      "id": "faq.ai-models",
      "domain": "faq",
      "slug": "ai-models",
      "name": "Which AI models does Konyx use, and what sees our data?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.8, §4"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "Konyx calls OpenAI models through their API for request extraction, clarifying questions, column mapping, filtering web search results and writing the audit narrative — behind an abstraction so the provider can change. Catalog matching, purchase history and vendor ranking are database queries and never leave Konyx. Every model call is recorded with who made it, which prompt version and what it cost.",
      "related": [
        "how-it-works.what-the-ai-does",
        "control.ai-provenance"
      ],
      "url": "https://konyxai.com/knowledge/faq#ai-models"
    },
    {
      "id": "faq.vendor-account",
      "domain": "faq",
      "slug": "vendor-account",
      "name": "Do our vendors need an account?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — vendor portal"
      },
      "audiences": [
        "vendors",
        "buyers"
      ],
      "summary": "No. A vendor answers an RFQ through the link in the email — no account, no password. They price each line, add lead time and terms, and can revise; every revision is kept.",
      "related": [
        "capabilities.vendor-quote-portal"
      ],
      "url": "https://konyxai.com/knowledge/faq#vendor-account"
    },
    {
      "id": "faq.own-email",
      "domain": "faq",
      "slug": "own-email",
      "name": "Can we send RFQs from our own email address?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — own-email sending"
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "summary": "Yes. A toggle on the send screen — and a per-company default — prepares each vendor's message for the buyer's own mail app. The buyer sends it and ticks the recipients; Konyx records it and the quotes still come back through the vendor's link.",
      "related": [
        "capabilities.own-email-sending"
      ],
      "url": "https://konyxai.com/knowledge/faq#own-email"
    },
    {
      "id": "faq.phones",
      "domain": "faq",
      "slug": "phones",
      "name": "Does it work on a phone?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — phone-first layout"
      },
      "audiences": [
        "technicians"
      ],
      "summary": "Yes, in the phone's browser, with nothing to install. Ask Konyx is built for a phone on the plant floor — voice, photos, the draft as a sheet — and every other screen, including the wide quote grid, stacks to fit a phone.",
      "related": [
        "capabilities.native-mobile-app",
        "capabilities.ask-konyx"
      ],
      "url": "https://konyxai.com/knowledge/faq#phones"
    },
    {
      "id": "faq.onboarding-time",
      "domain": "faq",
      "slug": "onboarding-time",
      "name": "How long does it take to get started?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot"
      },
      "audiences": [
        "buyers",
        "finance"
      ],
      "summary": "Vendors and catalogs come in from one spreadsheet and the team from another, with problems shown before anything is committed. A pilot runs ninety days on one facility, and the baseline — a savings audit of your own purchasing history — is done before it starts.",
      "related": [
        "pilot.shape",
        "capabilities.data-import"
      ],
      "url": "https://konyxai.com/knowledge/faq#onboarding-time"
    },
    {
      "id": "faq.pricing",
      "domain": "faq",
      "slug": "pricing",
      "name": "What does Konyx cost?",
      "verifiedAt": "2026-10-27",
      "version": 5,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pricing"
      },
      "audiences": [
        "finance"
      ],
      "summary": "Konyx is priced by RFQs per month — or, on the Search plan, searches per month — for the whole company, not per person. Search is $29 a month for 25 searches: Ask Konyx finds vendors, with their contact details, and the buyer contacts them directly — it drafts and sends no RFQs. Starter is $99 a month for 25 RFQs and drafts them; Growth, $249 for 50, also sends them to vendors; Professional, $499 for 250, adds the company's own vendor database — all bought online and billed monthly by card. Starter starts with 14 days free: the card is entered at sign-up, nothing is charged during the 14 days, and $99 a month is charged from day 15 unless the plan is cancelled before then. Search, Growth and Professional have no trial. Every plan searches for vendors; only Search limits searches. Enterprise, for multi-site or complex operations, is priced with Konyx, with its limits and features set for the company. A pilot with a savings audit of the company's own purchasing history is still a way in.",
      "fields": {
        "Search": "$29 a month — 25 searches per month — vendor search only: vendors found with their contact details and product links, no RFQs drafted or sent — finding vendors, nothing more",
        "Starter": "$99 a month — 25 RFQs per month — vendor search and RFQ drafts — small industrial business",
        "Growth": "$249 a month — 50 RFQs per month — adds RFQ sending — growing manufacturer",
        "Professional": "$499 a month — 250 RFQs per month — adds your own vendor database — high-volume purchasing team",
        "Enterprise": "custom — multi-site or complex operation — RFQs per month and features set with Konyx",
        "Free trial": "Starter only, 14 days, for a company that signs up online — card entered on Stripe's page, nothing charged until day 15; cancel before then from Settings → Plan and billing → Card and invoices; moving up to Growth or Professional ends the trial and that plan is charged straight away; not given again to a company that chooses a plan after one ended",
        "Counted": "every RFQ the company creates in its billing month, starting again on the day the plan renews; on Search, every new request asked of Ask Konyx instead — one search, whoever asks, with its follow-up answers and Konyxions part of it",
        "Billing": "US dollars, monthly, by card through Stripe"
      },
      "related": [
        "capabilities.online-signup",
        "capabilities.plan-limits",
        "pilot.baseline",
        "company.contact"
      ],
      "url": "https://konyxai.com/knowledge/faq#pricing"
    },
    {
      "id": "faq.find-new-vendors",
      "domain": "faq",
      "slug": "find-new-vendors",
      "name": "Can Konyx find vendors we do not already use?",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/discovery"
      },
      "audiences": [
        "buyers"
      ],
      "summary": "Yes — they are called Konyxions. After the company's own vendors and the Konyx network have answered, Konyx searches the web for vendors who carry the part, reads their contact pages and shows them with reasons, a score and a link to the matching product on the vendor's site. Konyxions are looked for worldwide, not in one country: nearby vendors come up first, and vendors elsewhere still appear. A Konyxion is only emailed once a person picks it and checks the address.",
      "related": [
        "capabilities.vendor-discovery",
        "control.discovered-vendors-reviewed"
      ],
      "url": "https://konyxai.com/knowledge/faq#find-new-vendors"
    },
    {
      "id": "faq.konyx-network",
      "domain": "faq",
      "slug": "konyx-network",
      "name": "What is the Konyx network?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — platform vendors"
      },
      "audiences": [
        "buyers"
      ],
      "summary": "Vendors and catalogs that Konyx maintains and suggests beneath a company's own vendors, only when a catalog line matches the request. They are Konyx's data, not another customer's; choosing one copies it into the company's own list.",
      "related": [
        "capabilities.konyx-network"
      ],
      "url": "https://konyxai.com/knowledge/faq#konyx-network"
    },
    {
      "id": "faq.marketplace",
      "domain": "faq",
      "slug": "marketplace",
      "name": "Is Konyx a marketplace?",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — What Konyx does"
      },
      "audiences": [
        "finance",
        "vendors"
      ],
      "summary": "No. Konyx is software the buying company uses. Vendors quote directly to the company through a link, the company chooses the vendor and deals with them directly, and Konyx does not stand between them.",
      "related": [
        "company.how-konyx-differs"
      ],
      "url": "https://konyxai.com/knowledge/faq#marketplace"
    },
    {
      "id": "faq.api-and-integrations",
      "domain": "faq",
      "slug": "api-and-integrations",
      "name": "Is there an API or an integration with our systems?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §5"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "Not yet. There is no public API and no ERP connector in the current version. Email (from Konyx or from the buyer's own mailbox) and spreadsheet import are the integrations today; sending through Microsoft 365 or Gmail by API is planned. The one public machine interface is this knowledge catalog.",
      "related": [
        "integrations.erp",
        "integrations.api"
      ],
      "url": "https://konyxai.com/knowledge/faq#api-and-integrations"
    },
    {
      "id": "faq.what-data-do-we-provide",
      "domain": "faq",
      "slug": "what-data-do-we-provide",
      "name": "What data do we need to give Konyx?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — imports"
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "summary": "To start: a vendor list with contacts and their catalogs (one spreadsheet), the team (a five-column CSV) and, for the savings audit and last-paid prices, an export of purchasing history. Contracts, inventory and open orders are optional and come later.",
      "related": [
        "capabilities.data-import",
        "integrations.spreadsheets"
      ],
      "url": "https://konyxai.com/knowledge/faq#what-data-do-we-provide"
    },
    {
      "id": "faq.wrong-extraction",
      "domain": "faq",
      "slug": "wrong-extraction",
      "name": "What if the AI reads a request wrongly?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — Ask Konyx draft"
      },
      "audiences": [
        "technicians",
        "buyers"
      ],
      "summary": "Nothing happens until a person confirms the draft. Every field shows whether it was confirmed, inferred or unknown, the person can change any of it or answer a question, and the buyer reviews every line again before an RFQ goes out. Where the extraction came from is stored with the request.",
      "related": [
        "capabilities.ask-konyx",
        "control.ai-provenance"
      ],
      "url": "https://konyxai.com/knowledge/faq#wrong-extraction"
    },
    {
      "id": "faq.audit-trail",
      "domain": "faq",
      "slug": "audit-trail",
      "name": "Can we see who did what?",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — activity log"
      },
      "audiences": [
        "finance",
        "IT and security"
      ],
      "summary": "Yes. Every action is written to an append-only log in the same transaction as the change — who, what, when — and shown in plain sentences on the request, the person and the company. Actions taken by Konyx staff are written as done by Konyx.",
      "related": [
        "capabilities.activity-log",
        "control.append-only-audit"
      ],
      "url": "https://konyxai.com/knowledge/faq#audit-trail"
    },
    {
      "id": "control.person-presses-send",
      "domain": "control",
      "slug": "person-presses-send",
      "name": "A person presses Send",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — decision log, 15 Sep 2026"
      },
      "audiences": [
        "finance",
        "IT and security"
      ],
      "summary": "AI reads and drafts; it never sends. Every RFQ waits for a named person who holds the permission to open it, review the exact email, acknowledge the review and press Send.",
      "related": [
        "capabilities.rfq",
        "capabilities.autonomous-purchasing"
      ],
      "url": "https://konyxai.com/knowledge/control#person-presses-send"
    },
    {
      "id": "control.permissions-on-every-call",
      "domain": "control",
      "slug": "permissions-on-every-call",
      "name": "Permissions on every call",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.1"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "Drafting an RFQ and sending it are separate permissions, checked in the API on every request — not in the screen. An employee who cannot send escalates by design, not by convention; calling the endpoint directly is refused.",
      "related": [
        "capabilities.roles-and-permissions",
        "use-cases.employee-cannot-send"
      ],
      "url": "https://konyxai.com/knowledge/control#permissions-on-every-call"
    },
    {
      "id": "control.append-only-audit",
      "domain": "control",
      "slug": "append-only-audit",
      "name": "An audit trail that cannot drift",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.7"
      },
      "audiences": [
        "IT and security",
        "finance"
      ],
      "summary": "Every state change is written in the same transaction as the change itself, by the one function allowed to change a status, and the log is append-only at the database level. The trail cannot disagree with what happened because nothing else can write either.",
      "related": [
        "capabilities.activity-log",
        "faq.audit-trail"
      ],
      "url": "https://konyxai.com/knowledge/control#append-only-audit"
    },
    {
      "id": "control.discovered-vendors-reviewed",
      "domain": "control",
      "slug": "discovered-vendors-reviewed",
      "name": "Konyxions are reviewed",
      "verifiedAt": "2026-10-07",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.4"
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "summary": "A Konyxion — a vendor Konyx found on the web — is never emailed until a person picks it and checks the address on the send screen. That one gate is the quality gate, the deliverability gate and the legal gate.",
      "related": [
        "capabilities.vendor-discovery"
      ],
      "url": "https://konyxai.com/knowledge/control#discovered-vendors-reviewed"
    },
    {
      "id": "control.tenant-isolation",
      "domain": "control",
      "slug": "tenant-isolation",
      "name": "Each company is isolated in the database",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.1"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "Row-level security is forced on every tenant-scoped table and the application connects as a role that cannot bypass it. Two automated checks fail the build if a table lacks its policy or a query bypasses the scoped accessor, and a live test proves a cross-company read is refused. Konyx staff use the same permission wall, never a database console.",
      "related": [
        "faq.data-isolation",
        "control.architecture"
      ],
      "url": "https://konyxai.com/knowledge/control#tenant-isolation"
    },
    {
      "id": "control.terms-and-privacy",
      "domain": "control",
      "slug": "terms-and-privacy",
      "name": "Terms of Service, Privacy Policy and Cookie Policy",
      "verifiedAt": "2026-10-15",
      "version": 3,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — /terms, /privacy and /cookies"
      },
      "audiences": [
        "IT and security",
        "buyers"
      ],
      "summary": "The Terms of Service and Privacy Policy are published at konyxai.com/terms and konyxai.com/privacy. Everyone creating a company or signing in to the company app ticks a box agreeing to both, and the version each person agreed to, and when, is recorded against them and in the activity log. The Terms set out how plans bought online are billed, renewed, changed and cancelled; card payments are taken by Stripe and card details never reach Konyx. The Cookie Policy at konyxai.com/cookies lists every cookie: one keeps a person signed in (7 days), one carries a sign-up to payment (up to a day), and Google Analytics' own only while analytics is switched on.",
      "body": [
        "The sign-up, sign-in, activation and password-reset forms refuse to go on without the box, and so does the API behind them. When the terms change, the next sign-in asks again.",
        "Konyx does not sell personal information or use it for advertising. Google Analytics runs on the site and the company app only when switched on, with advertising features off; it receives page paths with record numbers blanked, counts and choices, and the person and company as internal codes — never names, emails or what anyone typed. It never runs on the vendor quote link, or when the browser sends Global Privacy Control."
      ],
      "fields": {
        "Terms of Service": "https://konyxai.com/terms",
        "Privacy Policy": "https://konyxai.com/privacy",
        "Cookie Policy": "https://konyxai.com/cookies",
        "Recorded per person": [
          "terms version agreed to",
          "when"
        ]
      },
      "related": [
        "control.tenant-isolation",
        "faq.hosting",
        "faq.ai-models"
      ],
      "url": "https://konyxai.com/knowledge/control#terms-and-privacy"
    },
    {
      "id": "control.no-default-accounts",
      "domain": "control",
      "slug": "no-default-accounts",
      "name": "No default accounts, anywhere",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — decision log, 15 Sep 2026"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "A company and its owner come into being in one of two ways: Konyx staff create them from the console, which emails the owner a temporary password, or the buyer signs up online, confirms their email with a six-digit code and chooses their own password. Nothing can be signed into that a person did not deliberately create, and every credential has one auditable origin.",
      "related": [
        "control.architecture"
      ],
      "url": "https://konyxai.com/knowledge/control#no-default-accounts"
    },
    {
      "id": "control.architecture",
      "domain": "control",
      "slug": "architecture",
      "name": "The shape of the system",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — decision log, 16 Sep 2026"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "One backend owns the database, the sessions, the permissions, email and AI, and cannot be reached without a key the browser never holds. The web applications are database-free: the browser calls their own backend, which forwards to the API with that key and the person's session. Sessions live in an httpOnly cookie; the token never appears in a response body.",
      "body": [
        "Every route that can be abused is rate-limited in the database, so every instance sees the same count: sign-in, activation, RFQ sending, AI requests, web vendor search, the vendor quote link, imports and the rest. State changes are refused unless the request came from the application's own origin. Security headers are set on every response; secrets live in a managed secret store, not in code."
      ],
      "related": [
        "faq.hosting",
        "control.tenant-isolation"
      ],
      "url": "https://konyxai.com/knowledge/control#architecture"
    },
    {
      "id": "control.ai-provenance",
      "domain": "control",
      "slug": "ai-provenance",
      "name": "Every model call is recorded",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §3.8"
      },
      "audiences": [
        "IT and security",
        "finance"
      ],
      "summary": "Each call to a model is recorded with who made it, which task and prompt version, and what it cost, and is shown per company and platform-wide. Each extracted field keeps its state, its evidence and the call that produced it, so the answer to why did it say that is always on file.",
      "related": [
        "how-it-works.what-the-ai-does",
        "faq.ai-models"
      ],
      "url": "https://konyxai.com/knowledge/control#ai-provenance"
    },
    {
      "id": "control.outside-email",
      "domain": "control",
      "slug": "outside-email",
      "name": "Email from outside is treated as untrusted",
      "verifiedAt": "2026-10-02",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — email/inbound.ts, core/inbound-mail.ts, webhooks"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "A vendor's reply is written by someone outside the company, so nothing in it is trusted: every event from the mail provider is signature-checked and refused if it is old, mail is counted and capped before it is read, a message is only ever shown as text, unsafe file types are never kept, and the model that labels a reply can answer with one word from a fixed list and nothing else.",
      "body": [
        "Limits apply per reply address, per company, per sender and overall; past a limit a message is not fetched, kept or passed on, and the RFQ's log says so once. A duplicate delivery changes nothing.",
        "Files a vendor attaches are downloads, never opened in the page, and the browser is told not to guess their type. Programs, scripts, web pages and macro-enabled documents are refused, and so is the original of a message that carried one.",
        "The copy emailed to the buyer sets the vendor's words apart from Konyx's own, warns when the sender is not one Konyx holds for that vendor or failed its mail checks, and is marked so that it cannot loop back in or set off an automatic reply.",
        "A reply is stored in the company's own data like everything else: another company cannot see it, its files or its original."
      ],
      "fields": {
        "Daily limit per reply address": "25 emails",
        "Hourly limit per sender": "40 emails",
        "What a model may add": "one label from a fixed list"
      },
      "related": [
        "capabilities.email-replies",
        "control.tenant-isolation",
        "control.ai-provenance",
        "control.append-only-audit"
      ],
      "url": "https://konyxai.com/knowledge/control#outside-email"
    },
    {
      "id": "pilot.shape",
      "domain": "pilot",
      "slug": "shape",
      "name": "One facility, ninety days",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot"
      },
      "audiences": [
        "finance",
        "buyers"
      ],
      "summary": "A pilot runs ninety days on one plant or business unit. It starts with a savings audit of the company's own purchasing history, brings in its vendors and team from spreadsheets, and ends with a decision made on measured adoption, accuracy, cycle time and savings.",
      "fields": {
        "Duration": "90 days",
        "Scope": "one facility or business unit",
        "Baseline": "the company's purchasing history, audited first",
        "Decision": "validated savings and cycle time, reviewed together at day 90",
        "Your systems": "the ERP stays the system of record"
      },
      "body": [
        "These are process defaults, not customer results. The measurement plan is agreed with the company's team."
      ],
      "related": [
        "pilot.baseline",
        "pilot.adoption",
        "pilot.decision"
      ],
      "url": "https://konyxai.com/knowledge/pilot#shape"
    },
    {
      "id": "pilot.baseline",
      "domain": "pilot",
      "slug": "baseline",
      "name": "Baseline — before any contract",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot"
      },
      "audiences": [
        "finance"
      ],
      "summary": "The company sends one purchasing export. Konyx computes the price gaps, cycle times and buyer hours from that file and writes the findings up, so the baseline is the company's own number, not Konyx's.",
      "related": [
        "capabilities.savings-audit",
        "proof.savings-audit-method"
      ],
      "url": "https://konyxai.com/knowledge/pilot#baseline"
    },
    {
      "id": "pilot.adoption",
      "domain": "pilot",
      "slug": "adoption",
      "name": "Adoption — real requests from week one",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot"
      },
      "audiences": [
        "buyers",
        "technicians"
      ],
      "summary": "Vendors and catalogs come in from one spreadsheet, the team from another with invitation links, and people start with Ask Konyx on real requests. Roles are set by the company from the permission toggles.",
      "related": [
        "capabilities.data-import",
        "capabilities.roles-and-permissions"
      ],
      "url": "https://konyxai.com/knowledge/pilot#adoption"
    },
    {
      "id": "pilot.decision",
      "domain": "pilot",
      "slug": "decision",
      "name": "Decide with evidence at day 90",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot"
      },
      "audiences": [
        "finance"
      ],
      "summary": "Adoption, extraction accuracy, cycle time and savings are measured in the product and reviewed together at day ninety. The company decides on its own figures.",
      "related": [
        "proof.customer-results"
      ],
      "url": "https://konyxai.com/knowledge/pilot#decision"
    },
    {
      "id": "pilot.what-we-need",
      "domain": "pilot",
      "slug": "what-we-need",
      "name": "What Konyx needs from the company",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — imports; konyx-admin — Audit"
      },
      "audiences": [
        "buyers",
        "IT and security"
      ],
      "summary": "An export of purchasing history for the audit; a vendor list with contacts and catalogs; a team list with who reports to whom; and one person who can decide roles. No ERP access and no installation.",
      "related": [
        "faq.what-data-do-we-provide"
      ],
      "url": "https://konyxai.com/knowledge/pilot#what-we-need"
    },
    {
      "id": "integrations.email",
      "domain": "integrations",
      "slug": "email",
      "name": "Email",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 4,
      "source": {
        "kind": "product",
        "ref": "konyx-api — email; konyx-erp — send screen"
      },
      "summary": "RFQs, invitations and notifications go out from Konyx's own sending domain, or an RFQ can be sent from the buyer's own mailbox through their mail app. A vendor's emailed reply comes back onto the RFQ where Konyx's reply address is switched on, and otherwise goes to the team's own inbox or the person who sent it.",
      "body": [
        "Vendor mail and account mail use two addresses on the same domain: RFQs, each with the vendor's own quote link, come from an address of their own (rfq@ by default, shown as \"the company via Konyx\"), sign-in details and invitations from another, so a vendor's filter or reply never mixes with people's sign-in mail. Company Settings shows both."
      ],
      "fields": {
        "Konyx sends": [
          "RFQs with each vendor's link",
          "team invitations and credentials"
        ],
        "The buyer sends": [
          "RFQs from their own mail app, recorded in Konyx"
        ],
        "Konyx receives": [
          "vendors' emailed replies to an RFQ",
          "delivery and bounce reports for what it sent"
        ]
      },
      "related": [
        "capabilities.own-email-sending",
        "capabilities.rfq",
        "capabilities.email-replies",
        "control.outside-email"
      ],
      "url": "https://konyxai.com/knowledge/integrations#email"
    },
    {
      "id": "integrations.spreadsheets",
      "domain": "integrations",
      "slug": "spreadsheets",
      "name": "Spreadsheets and CSV",
      "status": "live",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "product",
        "ref": "konyx-erp — imports"
      },
      "summary": "Vendors and catalogs, the team and purchasing history come in as CSV exports from whatever the company runs today, mapped on screen. A spreadsheet can also be dropped into Ask Konyx to become one request.",
      "fields": {
        "Live today": [
          "vendors and catalogs, with contacts",
          "team",
          "purchasing history (for the audit and last-paid prices)"
        ],
        "Planned": [
          "inventory",
          "open orders from the company's ERP",
          "contracts and contract pricing"
        ]
      },
      "related": [
        "capabilities.data-import",
        "capabilities.savings-audit"
      ],
      "url": "https://konyxai.com/knowledge/integrations#spreadsheets"
    },
    {
      "id": "integrations.erp",
      "domain": "integrations",
      "slug": "erp",
      "name": "ERP systems",
      "status": "planned",
      "verifiedAt": "2026-10-26",
      "version": 2,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — §5, explicitly not in v1"
      },
      "summary": "There are no live ERP connectors in the current version. The ERP stays the system of record for orders and money; Konyx takes purchase history in by export. Connectors are on the list after the pilots, not before.",
      "related": [
        "faq.replace-erp",
        "faq.api-and-integrations"
      ],
      "url": "https://konyxai.com/knowledge/integrations#erp"
    },
    {
      "id": "integrations.mailbox-connectors",
      "domain": "integrations",
      "slug": "mailbox-connectors",
      "name": "Microsoft 365 and Gmail",
      "status": "planned",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — Next"
      },
      "summary": "Sending through the buyer's mailbox by API — so an RFQ appears in their Sent folder without the mail app — is planned. Today the same result is reached through the buyer's own mail app.",
      "related": [
        "capabilities.mailbox-connectors",
        "capabilities.own-email-sending"
      ],
      "url": "https://konyxai.com/knowledge/integrations#mailbox-connectors"
    },
    {
      "id": "integrations.api",
      "domain": "integrations",
      "slug": "api",
      "name": "A public API and machine access",
      "status": "planned",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com/knowledge"
      },
      "summary": "There is no public product API. The one public machine interface today is this knowledge catalog: the same records served as JSON at /api/knowledge, as Markdown at /llms.txt and /llms-full.txt, and as pages under /knowledge.",
      "fields": {
        "Knowledge, JSON": "https://konyxai.com/api/knowledge",
        "Knowledge, Markdown": "https://konyxai.com/llms-full.txt",
        "Index for assistants": "https://konyxai.com/llms.txt"
      },
      "related": [
        "faq.api-and-integrations"
      ],
      "url": "https://konyxai.com/knowledge/integrations#api"
    },
    {
      "id": "proof.customer-results",
      "domain": "proof",
      "slug": "customer-results",
      "name": "Customer results",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "website",
        "ref": "konyxai.com — Pilot"
      },
      "audiences": [
        "finance"
      ],
      "summary": "Konyx has no published customer results yet. The pilot defaults on the site are process defaults, not outcomes. Results from pilots will be published here with the customer's consent, with the measurement method beside them.",
      "related": [
        "pilot.decision",
        "proof.savings-audit-method"
      ],
      "url": "https://konyxai.com/knowledge/proof#customer-results"
    },
    {
      "id": "proof.savings-audit-method",
      "domain": "proof",
      "slug": "savings-audit-method",
      "name": "How savings are measured",
      "verifiedAt": "2026-09-26",
      "version": 1,
      "source": {
        "kind": "product",
        "ref": "konyx-api — core/savings-analysis.ts"
      },
      "audiences": [
        "finance"
      ],
      "summary": "Every figure in a savings audit is computed in code from the company's own file: the price gap against its own best price for the same item, against the Konyx network and, when linked to a company on the platform, its catalog; cycle time and late deliveries from dates; quote competition from vendor counts; rush and card spend from flags; buyer hours from the step count of the manual process against Konyx's two steps. The model writes the findings from those figures and cannot change them.",
      "fields": {
        "Computed in code": [
          "price gaps",
          "cycle time",
          "late deliveries",
          "quote competition",
          "rush and card spend",
          "buyer hours and calendar days"
        ],
        "Written by the model": [
          "the narrative of the findings, from the figures"
        ]
      },
      "related": [
        "capabilities.savings-audit",
        "pilot.baseline",
        "capabilities.time-saved"
      ],
      "url": "https://konyxai.com/knowledge/proof#savings-audit-method"
    },
    {
      "id": "proof.engineering-verification",
      "domain": "proof",
      "slug": "engineering-verification",
      "name": "How the product is verified",
      "verifiedAt": "2026-10-26",
      "version": 3,
      "source": {
        "kind": "plan",
        "ref": "Engineering Action Plan — Build status"
      },
      "audiences": [
        "IT and security"
      ],
      "summary": "Each release runs type checks and lint in every app, a coverage check that every tenant table carries its isolation policy, a live test that a cross-company read is refused, unit and integration tests in the API, and an end-to-end run through the live servers as a signed-in user — admin creating a company, an owner importing a team, a request extracted by the live model, an RFQ sent, a vendor quoting twice, isolation refused, and the test companies deleted.",
      "fields": {
        "End-to-end checks": "297 in the current run",
        "Phone audit": "84 page states at two phone widths, zero pages wider than the screen"
      },
      "related": [
        "control.tenant-isolation",
        "control.architecture"
      ],
      "url": "https://konyxai.com/knowledge/proof#engineering-verification"
    }
  ]
}