Is the bgclear API compatible with remove.bg?
For the fields almost every integration uses — image_file, image_url, image_file_b64, size, format, bg_color, crop — yes: same names, same meaning. You change the base URL and the auth header (X-Api-Key becomes Authorization: Bearer). Not supported: zip output and the type, roi, scale, position and add_shadow parameters.
Responses are image bytes by default, as on remove.bg, with X-Credits-Charged and X-Credits-Remaining headers; send Accept: application/json for metadata and a hosted result URL. Errors are JSON with stable codes and the same important status codes (400, 402, 429).
Before/after code, the field table and a five-step checklist are on the migration page; the community SDKs for remove.bg hard-code its host, so replace the call with the plain HTTP snippet.