canonical: https://jentic.com/apis/swaggerhub.seamfix-6f8/swaggerhub-seamfix-6f8

# Seamfix 6f8 Background Cleanup API

This API provides **background cleanup capabilities** by automatically detecting and isolating the subject in an image, then removing or replacing the background with a standardized color (white) or format. It ensures all images meet visual and regulatory standards for **identity verification**, **biometric enrollment**, or **document processing**, improving consistency and accuracy across workflo. The API exposes 2 endpoints secured with bearer authentication.

## For AI agents

Programmatically authenticate and obtain access token, remove and replace image background. Covers 2 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Authenticate and obtain access token
- Remove and replace image background
- Integrate Background Cleanup API into automated workflows
- Query and filter Background Cleanup API records by parameters
- Monitor Background Cleanup API operational status and events

## Use cases

### Identity and Authentication Operations

Use the Background Cleanup API to perform identity auth operations programmatically. The API provides 2 endpoints covering core functionality including authenticate and obtain access token, remove and replace image background.

Example prompt: Call POST `/auth/authenticate/ext` to authenticate and obtain access token

### Data Retrieval and Monitoring

Query Background Cleanup API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Background Cleanup API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Background Cleanup API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'authenticate and obtain access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/authenticate/ext` | Authenticate and obtain access token |
| POST | `/api/v1/face/clip` | Remove and replace image background |

## Key resources

- **Authorization** — Authentication endpoints for obtaining access tokens
- **Background Cleanup** — Image background removal and standardization endpoints

## Why Jentic

- **Setup:** Wiring Background Cleanup API by hand means learning its bearer auth, wiring the token on every call, and handling requests and retries yourself across its tenant and platform hosts. Through Jentic you install once, import Background Cleanup API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The inputs for these operations travel in the request body rather than the URL path, so scope the agent by operation: limit it to the operations it needs, such as authenticating or clipping a face image. Any other operation stays out of the allowed set unless you add it.
- **Credential handling:** Your Background Cleanup API token 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.
- **Discovery method:** Agents search Jentic by intent such as 'authenticate and obtain an access token' or 'clip a face image', and Jentic returns the matching Background Cleanup API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Background Cleanup API use?

The Background Cleanup API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I authenticate and obtain access token with the Background Cleanup API?

Yes. Use the POST `/auth/authenticate/ext` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Background Cleanup API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I authenticate and obtain access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate and obtain access token'. Jentic returns the matching Background Cleanup API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Background Cleanup API have?

The Background Cleanup API exposes 2 endpoints covering authorization, background cleanup operations.

### Can I limit what my agent is allowed to do with the Background Cleanup API?

Yes. Because you run Jentic One yourself, your own rules decide which Background Cleanup API operations and credentials the agent may use, and you scope it operation by operation. This API has just two operations, authenticating for an access token via POST `/auth/authenticate/ext` and clipping or replacing an image background via POST `/api/v1/face/clip`, so you can allow only the ones the agent needs. Any operation you do not add stays outside the allowed set, and the stored bearer token is injected at execution time rather than exposed to the agent.