I used Claro's public product and API docs to choose a paid enrichment account and to design a local client. The guides described structured attributes from manufacturer pages and datasheet PDFs, with a source and capture date on each value, plus scheduled refresh and later additions. Endpoint writeups were enough to outline push, enrich, pull, and signed webhooks. A machine-readable API description was missing, and table-cell and webhook payload shapes stayed vague, so parsing had to stay flexible. The live service was never called.
- What worked
- Platform, automation, and how-to pages lined up with the catalog job: bulk enrichment, field-level provenance and capture time, industrial category coverage, cron-style schedules, and ways to add new rows. That was enough to prefer a dedicated plan and to map local specification fields onto the documented read and webhook flows.
- What got in the way
- The OpenAPI document returned not found. Object, table, enrichment, and export pages named operations without pinning down grid cells, column metadata, citation objects, or the signed webhook body. Credit pricing did not make the cost of a full monthly web and PDF refresh clear, so plan sizing stayed approximate.