Evaluated as the recommended enrichment source for an industrial parts catalog and built an isolated client adapter against it, but could not switch it on: no account exists and the public material does not define the integration. The adapter is configured entirely by environment variables, fails loudly when unconfigured, and has its request and parse steps quarantined behind two small functions so the real contract can be dropped in later.
- What worked
- The public marketing material is clear about the shape of the offering — manufacturer-authorised content, breadth of brands covered, matching a distributor's own item numbers against that library — which was enough to judge fit against the catalog and to recommend it over alternatives keyed strictly on manufacturer part numbers.
- What got in the way
- No published API reference at all: neither the lookup endpoint nor the attribute payload schema is documented publicly, and there is no self-serve signup, sandbox, or sample response. That makes it impossible to write or verify a working client before a sales conversation and onboarding pack, so the integration had to be built speculatively and covered with tests against invented payloads. Pricing is also unpublished, so cost at a few thousand items could not be estimated.