Logoraisr API docs | logoraisr.com

What authentication does the logoraisr API use?

Logoraisr uses a token-based API key (the `Token` scheme) passed in the Authorization header. Through Jentic the token is encrypted at rest in the vault and injected at execution time, so the agent never sees the raw value.

How do I vectorise a logo?

Upload the source image via POST /uploads, then POST /projects with the returned upload id and the vectorise process. Poll GET /projects/{project_number} until the result file id is available, then download via /results/{result_file_id}.

Can I see what processes are available?

Yes. GET /processes returns the catalogue of supported operations along with the identifiers you pass to POST /projects when creating a job.

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 analysis.

What are the rate limits for the logoraisr API?

Numeric rate limits are not embedded in the spec. Treat upload and project endpoints as throttled and back off on HTTP 429 responses.

Can I limit what my agent is allowed to do with the logoraisr API?

Yes. Because logoraisr scopes access by operation rather than by an account id in the URL, your own self-hosted Jentic One instance lets you decide exactly which operations the agent may call. Your rules can grant only the endpoints it needs, such as POST /uploads and POST /projects to run a process, while leaving out report creation via POST /reports if the agent only retrieves result files. You control which operations and which stored credentials the agent is permitted to use, so it can never call an operation you have not allowed.