Sibi

Sibi is an AI-powered procurement platform built for appliance and equipment replacement, matching a failed unit to an install-ready replacement and placing the order through its own partner API. Polygrade treats Sibi as one supplier in a real-time sourcing decision, not a system to read a claim from, Sibi doesn’t hold claim data, it holds replacement inventory and installation logistics.

What Polygrade does with Sibi

When a claim calls for a full replacement rather than a repair, Polygrade identifies the exact unit needed from technician notes and homeowner symptom detail, then searches across suppliers including Sibi to compare replacement options, pricing, and installation timelines.

What Polygrade knows to search for at Sibi comes from the homeowner’s own SMS thread, model and serial numbers, photos, and symptom detail collected in a triage conversation with an 80 to 83 percent response rate, not a technician’s guess after the fact.

Polygrade validates fit against the specific appliance model before ordering, places the order with whichever supplier, Sibi or another in the comparison, offers the best combination of price, fit, and install timeline, then tracks it through delivery and installation.

How the Sibi connection works

Sibi exposes a documented API for offers, ordering, and webhook events, which is where Polygrade checks replacement availability and places orders.

Where Sibi’s API doesn’t cover a workflow specific to your program, a Forward Deployed Engineer builds the mapping during deployment so Sibi stays in the supplier comparison without manual lookup.

What stays with Sibi

Sibi’s own replacement catalog, pricing, and installation network stay exactly where Sibi manages them. Polygrade doesn’t change how Sibi sources or installs a replacement, it changes how often Sibi gets found as the best option for a given claim.

Across existing parts and replacement operations, Polygrade identifies roughly 12.6 percent procurement overspend against optimal supplier routing, comparisons that include Sibi alongside every other supplier in the network.

Throughput and data handling

Manual parts and replacement sourcing runs about 6 orders per agent hour; with Polygrade comparing suppliers including Sibi automatically, that reaches 60. Order cycle time drops from 9 to 20 days down to under 10.

The comparison against Sibi runs on a company-specific Polygrade instance, one client’s sourcing and pricing data are never accessible to another. Polygrade is SOC 2 compliant, with both Type I and Type II audits complete.

Deploying the integration

A dedicated Forward Deployed Engineer sets up the Sibi connection alongside your existing supplier relationships, so Sibi is compared on equal footing with every other distributor and replacement provider in your network from day one.

Frequently asked questions about Polygrade and Sibi

Does Polygrade replace Sibi?

No. Sibi continues to source, price, and install replacement units exactly as it does today; Polygrade decides when Sibi is the best option for a given claim and places the order.

How does Polygrade connect to Sibi?

Sibi exposes a documented API for offers, ordering, and webhook events, which is where Polygrade checks availability and places orders. Where a workflow isn’t covered, a Forward Deployed Engineer builds the connector during deployment.

Does Polygrade only use Sibi for replacements?

No. Sibi is one of multiple suppliers Polygrade compares in real time for every replacement decision, alongside price, fit, and installation timeline from the rest of your supplier network.