For Agents
Upload logo images, run processing operations such as vectorisation or cleanup, and download the resulting files via the logoraisr API.
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 available processing processes through GET /processes
Create a project that runs one of those processes on an uploaded image
GET STARTED
Use for: Upload a logo image for processing, List the available image-processing processes, Create a project to vectorise this logo, Retrieve the result file for a finished project
Not supported: Does not handle logo hosting, CDN delivery, or template-based marketing image generation — use for running processes on uploaded logos and retrieving the result 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 that takes uploaded logos and brand assets and runs them through configurable processes such as cleanup, vectorisation, and analysis. The API exposes ten operations covering image upload, process catalogue listing, project and report creation, and retrieval of preview and result files.
Poll project status and retrieve outputs with GET /projects/{project_number}
Generate analysis reports for an uploaded image via POST /reports
Download processed result files by id through /results/{result_file_id}
Patterns agents use API docs | logoraisr.com API for, with concrete tasks.
★ Logo Vectorisation
Convert raster logos to clean vectors by uploading the source via POST /uploads, creating a project on POST /projects with the vectorise process, and downloading the SVG result. The async project model lets large files process without keeping the HTTP connection open.
POST /uploads with the source PNG, then POST /projects referencing the upload id and the vectorise process.
Brand Asset Cleanup Batch
Run noise removal and background cleanup across a batch of uploaded brand assets by creating one project per asset. Each project runs independently so a failure on one asset does not block the rest of the batch from completing.
For each asset, POST /uploads, then POST /projects with process='cleanup', then GET /projects/{project_number} until complete.
Logo Quality Reporting
Audit logo quality by calling POST /reports with the upload id. Reports surface issues such as low resolution or wrong colour space and are retrieved via GET /reports/{report_number} for design-team review.
POST /reports with the upload id, then GET /reports/{report_number} to read the analysis.
AI Agent Logo Pipeline via Jentic
An agent that handles design-team requests can chain the upload, project, and result endpoints to clean and return logos automatically. Jentic exposes them as MCP tools so the agent invokes the right operation by intent.
Through Jentic, search 'vectorise a logo', load logoraisr POST /uploads, 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 an analysis report
/reports/{report_number}
Get report details
/results/{result_file_id}
Download a processed file
/previews/{file_id}
Get a preview of an uploaded file
/uploads
Upload a new image
/processes
List available processes
/projects
Create a new project
/projects/{project_number}
Get project details
/reports
Create an analysis report
Three things that make agents converge on Jentic-routed access.
Credential isolation
The logoraisr token is stored encrypted in the Jentic vault and injected at execution. Agents never see the raw token in their prompt or logs.
Intent-based discovery
Agents search by intent (e.g. 'vectorise a logo') and Jentic returns the matching logoraisr operation with the correct multipart upload schema and follow-up project endpoints.
Time to first call
Direct logoraisr integration: half a day to wire up 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 never enters the agent's prompt.
How do I run a vectorisation pipeline?
Upload the image via POST /uploads, then POST /projects with the upload id and the vectorise process. Poll GET /projects/{project_number} until the result file id appears, then download via /results/{result_file_id}.
Can I list the available image-processing processes?
Yes. GET /processes returns the catalogue of available operations along with the identifiers you pass to POST /projects.
How do I process a logo through Jentic?
Run `pip install jentic`, search Jentic for 'process a logo image', load the logoraisr POST /uploads operation, then chain POST /projects with the upload id and process selection.
What are the rate limits for the logoraisr API?
Numeric rate limits are not declared in the spec. Treat upload and project endpoints as throttled and back off on HTTP 429 responses.
/reports/{report_number}
Get report details
/results/{result_file_id}
Download a processed file
/previews/{file_id}
Get a preview of an uploaded file