[APP] EnConvert

**Name of app / service**

EnConvert — https://www.enconvert.com — an API that renders web pages into agent-ready data (markdown, cleaned/raw HTML, screenshot, PDF, links, images, or schema-driven structured data) and returns a `render_quality` honesty score on every read.

**Link to developer documentation**

- API docs: https://www.enconvert.com/docs
- Perceive endpoint: https://www.enconvert.com/docs/endpoints/perceive
- Base URL: `https://api.enconvert.com`

**Auth**

Custom API key. Every request sends the header `X-API-Key: `, where the key is a **private** key (prefix `sk_`) from the EnConvert dashboard → API keys. Public `pk_` keys are rejected. Please set the app up with API-key auth exposing the key to components (e.g. as `$auth.api_key`).

**Is lack of support preventing you from moving forward, or do you have a workaround?**

The component code is already written and pushed (fork branch, ready to PR): an `enconvert` app file plus a **Perceive URL** action (`POST /v2/perceive`). Per the PR template, a new-app PR is only reviewed after the app is integrated, so this request is the blocker — there is no workaround for the managed-auth registry version until the `enconvert` app record + auth exist on the platform.

**Are there specific actions or triggers you'd like to see for this app?**

First action, ready now:
- **Perceive URL** — `POST /v2/perceive` — render a page into markdown / HTML / screenshot / PDF / links / images / structured data, with a `render_quality` score.

Planned follow-ups (same API key):
- **Discover URLs** — enumerate a site's links.
- **Convert to PDF / Markdown / Image**, **Compress Image** — file/URL conversions.
- **Start Ingest** + **Ingest Job** — build a RAG corpus from a site.
- **Create / Read Watcher** — change-detection snapshots.

App icon available at https://www.enconvert.com (mark: `enconvert-mark-solid-512.png`) — happy to send the exact file you need.

Start with the existing enconvert app file and the platform's app-record and managed-auth patterns. Verify the Perceive URL action against the EnConvert API docs, including POST /v2/perceive and the X-API-Key private-key requirement. Done means the enconvert app and authentication are integrated so the action is available through the managed-auth registry.

Written by the indexing model from the issue text.