API Documentation

EnConvert: the web reading API that scores every page it returns#

EnConvert reads any URL or file for AI agents. /v2/perceive renders a live page and returns clean Markdown, JSON, or a screenshot, and every web read carries a render_quality score from 0 to 1 plus the named deductions that lowered it, such as anti_bot_challenge, login_wall, soft_404, and unhydrated_shell. Challenge pages, login walls, and empty app shells come back flagged instead of as a 200 your agent believes. For files, /v1/convert/anything-to-markdown turns PDF, Word, PowerPoint, Excel, and other documents into heading-aware Markdown.

File conversion is the second capability, on the same API key and base URL: 51 conversion endpoints turn documents, images, data formats, and web pages into other formats, for example a URL into a PDF via /v1/convert/url-to-pdf. Requests run in synchronous or asynchronous mode, and batch processing converts multiple files or URLs in a single request.

Beta: The EnConvert API is currently in beta. Endpoints, parameters, and response formats may change as we refine the platform based on developer feedback. We recommend pinning to specific behavior rather than relying on undocumented fields.

Base URL:

https://api.enconvert.com

All API requests should be made to this base URL, followed by the appropriate endpoint path (e.g., https://api.enconvert.com/v1/convert/url-to-pdf).

Key Features#

  • 51 conversion endpoints covering documents, data formats, images, and web pages
  • Web intelligence (V2, beta): perceive, discover, search, extract, ingest, and monitor web pages through six /v2 endpoints, all callable today
  • Two authentication methods: private keys for server-to-server integration and public keys with JWT for client-side usage
  • Batch processing: convert multiple files or URLs in a single request
  • Synchronous and asynchronous modes: get results immediately or poll for completion on long-running jobs
  • Job notifications: receive webhook callbacks when async conversions complete
  • Web widgets: embed conversion functionality directly into your web application
  • No SDK required: use standard HTTP requests from any language or platform

Supported Conversions#

Web Pages#

Conversion Endpoint
URL to PDF /v1/convert/url-to-pdf
URL to Screenshot /v1/convert/url-to-screenshot
URL to Markdown /v1/convert/url-to-markdown
Website to PDF /v1/convert/website-to-pdf
Website to Screenshot /v1/convert/website-to-screenshot

Data Formats#

Conversion Endpoint
JSON to XML /v1/convert/json-to-xml
XML to JSON /v1/convert/xml-to-json
JSON to YAML /v1/convert/json-to-yaml
YAML to JSON /v1/convert/yaml-to-json
JSON to CSV /v1/convert/json-to-csv
CSV to JSON /v1/convert/csv-to-json
JSON to TOML /v1/convert/json-to-toml
TOML to JSON /v1/convert/toml-to-json
CSV to XML /v1/convert/csv-to-xml
XML to CSV /v1/convert/xml-to-csv
Markdown to HTML /v1/convert/markdown-to-html

Documents to PDF#

Conversion Endpoint
HTML to PDF /v1/convert/html-to-pdf
Markdown to PDF /v1/convert/markdown-to-pdf
Word to PDF /v1/convert/doc-to-pdf
Excel to PDF /v1/convert/excel-to-pdf
PowerPoint to PDF /v1/convert/ppt-to-pdf
Pages to PDF /v1/convert/pages-to-pdf
Numbers to PDF /v1/convert/numbers-to-pdf
ODT to PDF /v1/convert/odt-to-pdf
ODS to PDF /v1/convert/ods-to-pdf
ODP to PDF /v1/convert/odp-to-pdf
OTS to PDF /v1/convert/ots-to-pdf
Any document to PDF /v1/convert/anything-to-pdf
Any document to Markdown /v1/convert/anything-to-markdown

Image Conversions#

Conversion Endpoint
JPEG to PNG /v1/convert/jpeg-to-png
PNG to JPEG /v1/convert/png-to-jpeg
JPEG to SVG /v1/convert/jpeg-to-svg
SVG to JPEG /v1/convert/svg-to-jpeg
JPEG to HEIC /v1/convert/jpeg-to-heic
HEIC to JPEG /v1/convert/heic-to-jpeg
JPEG to WebP /v1/convert/jpeg-to-webp
WebP to JPEG /v1/convert/webp-to-jpeg
PNG to SVG /v1/convert/png-to-svg
SVG to PNG /v1/convert/svg-to-png
PNG to HEIC /v1/convert/png-to-heic
HEIC to PNG /v1/convert/heic-to-png
PNG to WebP /v1/convert/png-to-webp
WebP to PNG /v1/convert/webp-to-png
SVG to HEIC /v1/convert/svg-to-heic
HEIC to SVG /v1/convert/heic-to-svg
SVG to WebP /v1/convert/svg-to-webp
WebP to SVG /v1/convert/webp-to-svg
HEIC to WebP /v1/convert/heic-to-webp
WebP to HEIC /v1/convert/webp-to-heic
PDF to JPEG /v1/convert/pdf-to-jpeg
Compress an image /v1/convert/compress-image

Web intelligence (V2)#

The V2 endpoints turn a URL into something an application can use: clean Markdown, structured data, a search result set, RAG-ready chunks, or a change alert. They run on the same headless Chrome engine and the same API keys as the conversion endpoints, draw from the same unified monthly ops allowance, and have their own beta status.

Endpoint What it does
/v2/perceive Render a URL once and return Markdown, HTML, a screenshot, a PDF, links, and structured data from that single render.
/v2/discover Enumerate a site's URLs from its sitemap and an HTTP crawl, without rendering each page.
/v2/lookup Run a web, news, scholar, or maps search and optionally perceive the top results.
/v2/distill Extract data matching a JSON schema, with a free CSS pass and an LLM-assisted fallback.
/v2/ingest Crawl a site into RAG-ready chunks and one JSONL file, delivered asynchronously.
/v2/watch Monitor a URL for changes and notify you by webhook or email when it changes.

All six are callable today with the same key. Perceive, Ingest and Distill are generally available; Distill needs a paid plan. Lookup, Watch and Discover are in private beta, so their request and response shapes can change without notice and their pages stay under Coming Soon.

One unified quota: V1 conversions and V2 operations draw from a single monthly ops allowance. Every unit of work costs one op: one file conversion, one URL perceived or distilled, one page ingested, one lookup query, one discover call. There are no credit multipliers and no per-endpoint counters. Tier allowances: Founding 500, Indie 3,000, Studio 15,000, Production 50,000 ops per month (Enterprise custom). Watchers are a separate cap, and LLM-powered extraction draws on monthly AI credits rather than ops. See the V2 overview and the pricing page.

Frequently asked questions#

What file formats can I convert with EnConvert?#

The API exposes 51 conversion endpoints across four categories: web pages (URL to PDF, screenshot, or Markdown), data formats (JSON, XML, YAML, CSV, TOML, Markdown, HTML), documents to PDF (Word, Excel, PowerPoint, Pages, Numbers, and OpenDocument formats), and image conversions (JPEG, PNG, SVG, HEIC, WebP).

Do I need an SDK to use the EnConvert API?#

No. EnConvert requires no SDK. You make standard HTTP requests from any language or platform to the base URL https://api.enconvert.com, followed by the endpoint path such as /v1/convert/url-to-pdf.

Does the API support asynchronous file conversion?#

Yes. The API offers synchronous and asynchronous modes (get results immediately, or poll for completion on long-running jobs), and job notifications deliver webhook callbacks when async conversions complete.

How do I authenticate with the EnConvert API?#

Two authentication methods are supported: private keys for server-to-server integration and public keys with JWT for client-side usage.

Where to go next#

  • Quickstart gets a first conversion running with cURL, Python, or Node.js.
  • Concepts explains the access surfaces, sync and async jobs, signed output URLs, and how V1 and V2 differ.
  • Endpoints is the reference for Perceive, Ingest, and every conversion route, plus the request parameters they share.
  • Guides covers file ingestion, webhooks, batch processing, and the integrations: MCP, n8n, the CLI, and the SDKs.
Quickstart →