Install Jentic One Beta

Connect the BackgroundErase API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BackgroundErase API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbackgrounderase.com%2Fbackgrounderase" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbackgrounderase.com%2Fbackgrounderase" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with BackgroundErase API.

Remove an image's background and return a transparent cutout

Return an alpha mask instead of a cutout for compositing pipelines

Replace a removed background with a solid color

Replace a removed background with a supplied background image

Validate an API key and check service health before a batch

GET STARTED

Start building with BackgroundErase API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use BackgroundErase API for, with concrete tasks.

★ Agent Image Cutout

An AI agent connected through Jentic cleans up an image on demand: it submits the photo and receives a transparent cutout, or an alpha mask when it needs to composite the subject itself. The agent gets back the processed image in one call, so a background-removal step slots into a larger media workflow without a separate editor.

Submit a product photo and request a transparent cutout, then confirm the processed image was returned

E-Commerce Product Photos

An online store standardises its catalog by removing each product's background and replacing it with a clean white or branded backdrop. BackgroundErase does the removal and the replacement in a single request, so every listing image lands on a consistent background.

Remove a product photo's background and replace it with a solid white background

Batch Preflight Check

Before a large run, a pipeline validates its API key and checks service health so it fails fast rather than mid-batch. BackgroundErase exposes both an account validation and a health check, which an agent calls first and then proceeds to process images only when both pass.

Validate the API key and check service health, then process the first image only if both succeed

Key Endpoints

5 endpoints — the backgrounderase api removes the background from an image and returns either a transparent cutout or an alpha mask for compositing.

METHOD

PATH

DESCRIPTION

POST

/v2

Remove an image background

GET

/v2/account

Validate an API key

GET

/v2/health

Check service health

POST

/v2

Remove an image background

GET

/v2/account

Validate an API key

GET

/v2/health

Check service health

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the BackgroundErase API by hand means managing an `x-api-key` credential, validating it against the account endpoint, and handling the health check before a batch yourself. Through Jentic you install once, import the BackgroundErase API from the API Directory, store the key once, and your agent calls it.

Permission scoping

BackgroundErase carries the image in the request body, so a rule bounds which operations your agent may call, not which image. You choose the operations it may call, so a rule can allow just the background-removal operation and leave the account operation out.

Credential isolation

Your BackgroundErase API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'remove an image background' or 'replace a background with white', and Jentic returns the matching BackgroundErase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using BackgroundErase API through Jentic.

What authentication does the BackgroundErase API use?

The BackgroundErase API authenticates with an API key sent in the `x-api-key` header, per its OpenAPI spec. The background-removal and account operations take that key, while the health-check endpoints need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context.

Can I replace a background, not just remove it, with the BackgroundErase API?

Yes. The same request that removes a background can replace it with a solid color or a supplied background image, so you get the subject on a new backdrop in one call. If you prefer to composite yourself, request an alpha mask instead of a finished cutout.

What are the rate limits for the BackgroundErase API?

The OpenAPI spec does not specify numeric rate limits for the BackgroundErase API. Check https://backgrounderase.com for the current limits and any per-plan concurrency before running a large batch.

Is there a BackgroundErase MCP server?

You don't need an MCP server to give your agent the BackgroundErase API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it. Operations are discovered on demand, so your agent's context stays lean instead of loading a separate server's tool definitions.

Can I limit what my agent is allowed to do with the BackgroundErase API?

Yes. Because the image travels in the request body, you write a rule that allows just the background-removal operation and leaves the account operation out, or the reverse. The agent can then process images but touch nothing else, and every call it makes is logged.

How do I remove an image background through Jentic?

Import the BackgroundErase API from the Jentic API Directory, store your API key once, and have your agent search Jentic for 'remove an image background'. Jentic returns the process-image operation with its input schema so the agent submits the image and reads back the cutout. To run it on your own infrastructure, install Jentic One from its GitHub repo.

BackgroundErase API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaImage ProcessingapiKey5 EndpointsREST

For Agents

Remove image backgrounds and return a transparent cutout or alpha mask, optionally replacing the background with a solid color or a new image, with operations to validate the API key and check service health.

Use for: Remove the background from this product photo, Return an alpha mask for this image so I can composite it myself, Replace the background of this image with white, Drop this subject onto a new background image

Not supported: Does not handle image hosting, resizing, or format conversion. Use for background removal and replacement only.

The BackgroundErase API removes the background from an image and returns either a transparent cutout or an alpha mask for compositing. In the same request it can replace the removed background with a solid color or a supplied background image, so a subject can be dropped onto a new backdrop in one call. Supporting operations validate an API key and report service health, which lets a pipeline confirm its credential and the service before pushing a batch of images.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

14%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

45%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

50%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

69%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the BackgroundErase API to your agent

Capabilities

Start building with BackgroundErase API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

BackgroundErase API

Jentic AI Readiness Score

BackgroundErase API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness