For Agents
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Background Cleanup 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%2Fswaggerhub.seamfix-6f8%2Fswaggerhub-seamfix-6f8" | shStep 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%2Fswaggerhub.seamfix-6f8%2Fswaggerhub-seamfix-6f8" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Background Cleanup API.
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
GET STARTED
Programmatically authenticate and obtain access token, remove and replace image background. Covers 2 operations with bearer authentication.
Use for: I need to authenticate and obtain access token, I want to remove and replace image background, Get the current status of Background Cleanup API resources, List all records from Background Cleanup API
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
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.
Monitor Background Cleanup API operational status and events
Patterns agents use Background Cleanup API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'authenticate and obtain access token', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — 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.
METHOD
PATH
DESCRIPTION
/auth/authenticate/ext
Authenticate and obtain access token
/api/v1/face/clip
Remove and replace image background
/auth/authenticate/ext
Authenticate and obtain access token
/api/v1/face/clip
Remove and replace image background
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Background Cleanup API through Jentic.
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.