For Agents
Upload logos, run image-processing processes such as cleanup or vectorisation, and retrieve the processed result files programmatically.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API docs | logoraisr.com, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API docs | logoraisr.com API.
Upload an image for processing via POST /uploads
List the catalogue of available processes through GET /processes
Create a project that runs one or more processes on an upload via POST /projects
GET STARTED
Use for: Upload a logo file for processing, List the image-processing processes I can run, Create a project that vectorises this uploaded logo, Retrieve the result file for project 4567
Not supported: Does not handle logo hosting, CDN delivery, or template-based design generation — use for processing uploaded logos through configurable processes and retrieving the resulting files only.
Jentic publishes the only available OpenAPI specification for API docs | logoraisr.com, keeping it validated and agent-ready. Logoraisr is an image-processing service focused on logos and brand assets — it cleans, vectorises, and analyses uploaded images by running them through configurable processes. The API exposes endpoints to upload images, list available processes, create projects and reports, retrieve previews and result files, and inspect project or report details.
Retrieve project details and processed outputs via GET /projects/{project_number}
Generate analysis reports on uploaded images with POST /reports
Download preview images and result files by id
Patterns agents use API docs | logoraisr.com API for, with concrete tasks.
★ Logo Vectorisation Pipeline
Convert raster logo uploads into clean vector files by uploading the source via POST /uploads, then creating a project with the vectorisation process via POST /projects. Poll GET /projects/{project_number} until the result file is ready, then download it through /results/{result_file_id}.
POST /uploads with the PNG, then POST /projects with the upload id and process='vectorise', then GET /projects/{project_number}.
Brand Asset Cleanup
Run noise removal and background cleanup on a batch of brand assets by creating one project per asset with the relevant process selected. Each project is independent so failures or retries on one asset don't block the rest of the batch.
For each asset, POST /uploads then POST /projects with process='cleanup' and the upload id.
Logo Quality Reports
Audit the quality of an uploaded logo by calling POST /reports with the upload id. Reports return analysis metadata such as resolution adequacy and colour-space issues, retrieved via GET /reports/{report_number}, and feed brand-team review queues.
POST /reports with the upload id, then GET /reports/{report_number} to read the analysis.
AI Agent Logo Processing via Jentic
An agent that handles brand-team requests can upload, process, and return cleaned logos through Jentic without managing the API token. Jentic exposes the upload, project, and result endpoints as MCP tools so the agent runs the full pipeline by intent.
Through Jentic, search 'process a logo image', load the logoraisr POST /uploads operation, then chain POST /projects and GET /projects/{project_number}.
10 endpoints — jentic publishes the only available openapi specification for api docs | logoraisr.
METHOD
PATH
DESCRIPTION
/uploads
Upload a new image
/processes
List available processes
/projects
Create a new project
/projects/{project_number}
Get project details
/reports
Create a new analysis report
/reports/{report_number}
Get report details
/results/{result_file_id}
Download a result file
/previews/{file_id}
Get a preview image
/uploads
Upload a new image
/processes
List available processes
/projects
Create a new project
/projects/{project_number}
Get project details
/reports
Create a new analysis report
Three things that make agents converge on Jentic-routed access.
Credential isolation
The logoraisr API token is stored encrypted in the Jentic vault and injected at execution time. Agents run the upload-and-process flow without ever seeing the raw token.
Intent-based discovery
Agents search by intent (e.g. 'vectorise a logo') and Jentic returns the matching logoraisr operation with its multipart upload schema and the follow-up project endpoints.
Time to first call
Direct logoraisr integration: half a day to handle multipart upload, project creation, and result polling. Through Jentic: under 30 minutes.
Alternatives and complements available in the Jentic catalogue.
Specific to using API docs | logoraisr.com API through Jentic.
Why is there no official OpenAPI spec for API docs | logoraisr.com?
Logoraisr does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call API docs | logoraisr.com via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the logoraisr API use?
Logoraisr uses a token-based API key (the `Token` security scheme) passed in the Authorization header. Through Jentic the token is held in the encrypted vault and injected at execution, so it never appears in the agent's prompt or logs.
How do I vectorise a logo with the logoraisr API?
Upload the source image via POST /uploads to get a file id, then POST /projects with that id and the vectorise process selected. Poll GET /projects/{project_number} until completion, then download the SVG via GET /results/{result_file_id}.
Can I list the available image-processing processes?
Yes. Call GET /processes to retrieve the catalogue of supported operations such as cleanup, vectorisation, and analysis. Use the process identifiers in subsequent POST /projects calls.
How do I generate a logo quality report through Jentic?
Run `pip install jentic`, search Jentic for 'analyse a logo image', load the logoraisr POST /reports operation, and execute it with the upload id. Then load GET /reports/{report_number} to fetch the result.
What are the rate limits for the logoraisr API?
The spec does not declare numeric rate limits. Treat the API as throttled on uploads and projects; back off on HTTP 429 responses and avoid more than a few concurrent processing jobs per token.
/reports/{report_number}
Get report details
/results/{result_file_id}
Download a result file
/previews/{file_id}
Get a preview image