Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Slazzer Background Removal 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%2Fslazzer.com%2Fslazzer" | 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%2Fslazzer.com%2Fslazzer" | 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 Slazzer Background Removal API.
Remove background from an image
Get credit information
AI Automobile processing
Query and filter Slazzer Background Removal API records by parameters
Monitor Slazzer Background Removal API operational status and events
GET STARTED
Patterns agents use Slazzer Background Removal API for, with concrete tasks.
★ CRM Operations
Use the Slazzer Background Removal API to perform crm operations programmatically. The API provides 12 endpoints covering core functionality including remove background from an image, get credit information, ai automobile processing.
Call POST /remove_image_background to remove background from an image
Automated Background Removal Management
Automate background removal operations by combining multiple Slazzer Background Removal API endpoints. Agents can get credit information and then ai automobile processing in a single workflow.
Call GET /credit to get credit information, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Slazzer Background Removal 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 apiKey tokens manually.
Search Jentic for 'remove background from an image', load the operation schema, and execute with Jentic-managed credentials
12 endpoints — ai-powered background removal api.
METHOD
PATH
DESCRIPTION
/remove_image_background
Remove background from an image
/credit
Get credit information
/ai-automobile
AI Automobile processing
/ai-upscale
AI Image Upscale
/ai-enhance
AI Image Enhance
/ai-de-oldify
AI De-oldify
/ai-relighting
AI ReLighting
/ai-shadow
AI Shadow
/remove_image_background
Remove background from an image
/credit
Get credit information
/ai-automobile
AI Automobile processing
/ai-upscale
AI Image Upscale
/ai-enhance
AI Image Enhance
/ai-de-oldify
AI De-oldify
/ai-relighting
AI ReLighting
/ai-shadow
AI Shadow
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Slazzer Background Removal API by hand means sending your key in the API-KEY header to api.slazzer.com/v2.0 and handling image upload and processing responses yourself. Through Jentic you install once, import Slazzer from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Slazzer passes image input in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as removing an image background or checking credit. Other processing operations like upscale or relighting are not included unless you add them to the allowed set.
Credential isolation
Your Slazzer 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 'check remaining credit', and Jentic returns the matching Slazzer 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 Slazzer Background Removal API through Jentic.
What authentication does the Slazzer Background Removal API use?
The Slazzer Background Removal API uses an API key passed in the `API-KEY` 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 remove background from an image with the Slazzer Background Removal API?
Yes. Use the POST /remove_image_background endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Slazzer Background Removal 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 remove background from an image through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'remove background from an image'. Jentic returns the matching Slazzer Background Removal API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Slazzer Background Removal API have?
The Slazzer Background Removal API exposes 12 endpoints covering background removal, credits, ai processing operations.
Can I limit what my agent is allowed to do with the Slazzer Background Removal API?
Yes. Jentic One is self-hosted, so you set the rules that decide which Slazzer operations and credentials your agent may use. Because Slazzer passes image data in the request body rather than a resource id in the path, you scope access at the operation level, for example allowing only POST /remove_image_background and GET /credit while leaving other processing operations such as ai-upscale or ai-relighting out of the allowed set. The stored API key is injected only for the operations you have approved, so the agent cannot call anything you did not grant.
For Agents
Programmatically remove background from an image, get credit information. Covers 12 operations with apiKey authentication.
Use for: I need to remove background from an image, I want to credit information, Search for ai automobile processing, Find all ai image upscale
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
AI-powered background removal API. Supports image upload, URL, and base64 input. Returns transparent PNG, custom background, or alpha mask. The API exposes 12 endpoints secured with apiKey authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>