Are there limits on what Lyro can send to the Improvement program?

Yes. Submit Improvement is capped at 100 files per day, 22MB per file, and 50 megapixels, and submitting an image accepts the Improvement Program Conditions. Lyro stays inside those limits and reports anything oversized rather than retrying it.

Whose remove.bg credits get spent when Lyro removes a background?

The account whose credentials you connect. Get Account returns that account's current credit balance and usage, so Lyro can check what is left before calling Remove Background instead of discovering an empty balance mid-request.

Can Lyro do any other image editing through this integration?

No. The connected toolkit is Remove Background, Get Account, and Submit Improvement, so cutting out or replacing a background is the extent of it. Cropping, retouching, and resizing need a different tool in the chain.

What happens to the cut-out image after Lyro produces it?

It comes back into the conversation, so Lyro can send it to the person who asked or pass it to a human agent along with the full thread. Anything further, like filing it against a product record, depends on the other integrations you have connected.

Remove bg MCP integration

Cuts the background out of an image sent in a conversation, checks remaining credits first, and flags shots the model could not handle.

Connect Remove bg See all integrations

3actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Remove background
Lyro removes the background from an image automatically. Customers get clean product photos or portraits instantly.
Get account
Lyro retrieves account credit balance. Support confirms the customer has remaining credits before processing images.
Submit improvement
Lyro submits an image to the remove.bg improvement program. Support helps refine the algorithm on edge cases and difficult backgrounds.

See all 3 actions

How businesses use Remove bg + Lyro

Each card is one request a support team gets, and the Remove bg actions Lyro runs to close it.

Cut out a photo the moment it arrives
A customer or teammate sends a product or profile shot and Lyro returns it with the background removed, so the image is usable before the conversation has moved on.
Remove BackgroundGet Account
Put a listing photo on the background it needs
Lyro runs the image with a custom background instead of a transparent one, so a seller gets a shot that already matches the marketplace or catalogue style guide.
Remove BackgroundGet Account
Check the credit balance before a bulk run
Lyro reads the account's credit and usage details first, so a request to process a batch either goes ahead or comes back with the real number left rather than failing partway through.
Get AccountRemove Background
Feed the images that fail back to remove.bg
When a shot comes back wrong, Lyro submits it to the remove.bg Improvement program so the same category of image is handled better later instead of being quietly retried by hand.
Submit ImprovementGet Account

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Remove bg actions it has and picks the ones a request needs.

01
Connect Remove bg
Authorize the Remove bg account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Remove bg actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Remove bg · Lyro

Everything else about Remove bg

Setup, permissions, and the limits of what Lyro can do inside Remove bg.

Yes. Submit Improvement is capped at 100 files per day, 22MB per file, and 50 megapixels, and submitting an image accepts the Improvement Program Conditions. Lyro stays inside those limits and reports anything oversized rather than retrying it.