Loading page…
Loading page…
Diakrio is the product and platform name. The first-version package family uses the Diakrio names below. Old-name forwarding packages are no longer part of the candidate.
| Previous name | Current name |
|---|---|
@convert-buddy/errors | @diakrio/errors |
@convert-buddy/converter | @diakrio/converter |
convert-buddy-js | @diakrio/converter |
@convert-buddy/importer-contracts | @diakrio/importer-contracts |
@convert-buddy/importer-core | @diakrio/importer-core |
@convert-buddy/importer-worker | @diakrio/importer-worker |
@convert-buddy/importer-react | @diakrio/importer-react |
@convert-buddy/cloud-client | @diakrio/cloud-client |
@convert-buddy/ocr | @diakrio/ocr |
@convert-buddy/anonymizer | @diakrio/anonymizer |
Update dependencies and imports directly. Schema and record-processing APIs belong to @diakrio/converter/schema and @diakrio/converter/processing. Importer provides the interface over that SDK; Cloud integrations use Cloud client.
https://convert-buddy.app → https://diakrio.comhttps://app.convert-buddy.app → https://app.diakrio.comhttps://api.convert-buddy.app → https://api.diakrio.comWebsite and dashboard requests redirect to the matching Diakrio path. The legacy API host remains available without an HTTP redirect so authenticated requests, request bodies and strict clients continue to work.
Existing cb_* credentials, X-Convert-Buddy-* headers, webhook signature version 1 and public JavaScript type names are protocol identifiers. They remain valid in this major version and must not be rewritten in stored configuration.
The brand migration does not change Cloud API behavior. Review the separate packages and Cloud v2 guide for behavioral and authentication changes.