Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Doc Converter, 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%2Fpresalytics.io%2Fpresalytics-converter" | 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%2Fpresalytics.io%2Fpresalytics-converter" | 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 Doc Converter API.
Convert OpenXml documents (DOCX, PPTX, XLSX) to scalable SVG output
Transform OpenOffice format files into web-ready vector graphics
Produce resolution-independent SVG from slide and document content
Accept file uploads and return converted vector output in a single request
Patterns agents use Doc Converter API for, with concrete tasks.
GET STARTED
★ Document-to-SVG for Web Embedding
Convert office documents to SVG format for embedding directly in web applications without requiring browser plugins or document viewers. The Doc Converter API accepts common office file formats and returns SVG output that renders at any resolution, making it suitable for responsive web layouts, documentation portals, and content management systems that need to display document previews inline.
Upload a PPTX file to the /svgconvert endpoint and retrieve the SVG output for embedding in a web page
Design Pipeline Preprocessing
Preprocess office documents into SVG vector format as an input step for design automation pipelines. By converting source documents to SVG first, downstream tools can manipulate individual elements, apply transformations, and composite outputs without rasterization losses. This is useful for report generation systems that combine document content with custom branding or layout templates.
Convert an XLSX spreadsheet to SVG via the /svgconvert endpoint and pass the result to a downstream image composition step
AI Agent Document Conversion
AI agents use the Doc Converter through Jentic to transform office documents into SVG as part of automated content processing pipelines. The agent searches for document conversion operations, loads the endpoint schema with supported input formats, and executes the conversion without manual integration. This enables agents to handle format transformation as an intermediate step in larger document workflows.
Search Jentic for 'convert office document to SVG', load the svgconvert operation schema, and execute with a sample DOCX file
1 endpoints — jentic publishes the only available openapi specification for doc converter, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/svgconvert
Convert an office document to SVG format
/svgconvert
Convert an office document to SVG format
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Doc Converter by hand means posting your office file to the /svgconvert endpoint at api.presalytics.io/doc-converter and handling the multipart upload and SVG response yourself. Through Jentic you install once, import the Doc Converter from the API Directory, and your agent calls it, with no credential to store since this spec declares no authentication.
Permission scoping
The Doc Converter exposes a single operation, /svgconvert, with the document passed in the request body, so scoping is by operation: the agent is limited to that one conversion call and nothing else. There is no resource id to pin, so the operation itself is the scope.
Credential isolation
This spec declares no authentication, so there is no credential to store. If Presalytics later adds access controls, any credential would be stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'convert an office document to SVG', and Jentic returns the Doc Converter svgconvert operation with its input schema showing the supported file formats so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Doc Converter
Identical conversion service available under a different API slug
This is the same service under a different slug - use either interchangeably.
Specific to using Doc Converter API through Jentic.
Why is there no official OpenAPI spec for Doc Converter?
Presalytics does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Doc Converter via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Doc Converter API use?
The Doc Converter API does not require authentication for the SVG conversion endpoint based on the current specification. If access controls are added, Jentic will handle credential management through your Jentic One instance automatically.
What input file formats does the Doc Converter support?
The API supports OpenXml formats (DOCX, PPTX, XLSX) and OpenOffice document formats (ODT, ODP, ODS). Files are uploaded to the /svgconvert endpoint and the response contains the converted SVG output.
What are the rate limits for the Doc Converter API?
The specification does not document explicit rate limits. For production workloads, implement request throttling on the client side and monitor response times to detect any server-side throttling.
How do I convert a document to SVG through Jentic?
Install the SDK with pip install jentic, set your JENTIC_AGENT_API_KEY, then search for 'convert document to SVG'. Jentic returns the svgconvert operation with its schema showing the required file upload format. Execute the operation with your document file to receive SVG output.
Can I limit what my agent is allowed to do with the Doc Converter API?
Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, and the Doc Converter API exposes only a single operation, /svgconvert, which accepts a document in the request body. You can scope the agent to that one conversion call and nothing else, since there is no resource id to pin and the operation itself is the scope. This keeps the agent restricted to converting OpenXml and OpenOffice files to SVG, with no other actions available.
Know of an official OpenAPI document? Contribute it →
For Agents
Convert OpenXml and OpenOffice documents to SVG vector format through a single API call.
Use for: I need to convert a PowerPoint file to SVG, I want to transform a DOCX document into a vector format, Convert an OpenOffice presentation to SVG for web display, Get an SVG rendering of a spreadsheet file
Not supported: Does not handle PDF generation, OCR text extraction, or image format conversion - use for office-to-SVG vector conversion only.
Jentic publishes the only available OpenAPI specification for Doc Converter, keeping it validated and agent-ready. The Presalytics Doc Converter API transforms OpenXml and OpenOffice document formats into vector SVG files through a single conversion endpoint. It accepts document uploads and returns high-fidelity SVG output suitable for web rendering, embedding in applications, or further processing in design pipelines.