[APP] Webhound

**Name of app / service**

Webhound

Requested app slug: `webhound`

Website: https://www.webhound.ai

**Link to developer documentation**

https://www.webhound.ai/docs/api

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

The generic HTTP action is only a partial workaround. It does not give users a managed Webhound connection, an explicit dollar-budget start step, honest asynchronous completion semantics, or a first-class evidence-pack handoff. We have prepared and tested native Pipedream components, but Pipedream requires the app/auth integration before we can submit them for review.

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

1. **Start Report** — start a private report with a user-set dollar budget.
2. **Start Dataset** — start a private dataset with a user-set dollar budget and optional schema.
3. **Check Research Status** — check once or poll briefly; return `done: true` only when Webhound reports an explicit terminal status.
4. **Retrieve Evidence Pack** — after terminal completion, return the report or dataset with its available provenance and work log.

No trigger is needed initially. Long research runs should be checked in later workflow steps instead of holding one action invocation open.

**Authentication details**

- Type: API key
- App auth field key expected by the prepared components: `api_key`
- Field label: `Webhound API Key`
- Field type: secret / password
- Header: `Authorization: Bearer {{api_key}}`
- API base URL: `https://api.webhound.ai/api/v2`
- Connection test: `GET /account/credits`
- Each user creates and supplies their own key from their Webhound Account page; keys begin with `wh_`.
- Please do not configure a Webhound-owned shared key, team key, proxy credential, or fallback secret.

The prepared package uses only the connected user's `$auth.api_key`. Its 13 tests, ESLint, package validator, component build, component-key validation, app-prop validation, duplicate-key validation, and frozen-lockfile check all pass. We will run a real connected-account smoke and submit the component PR as soon as the native app exists.

Review the Webhound API documentation and the prepared native Pipedream components, starting with GET /account/credits and the stated Bearer-token auth fields. Confirm the app connection uses the user's api_key, then run the connected-account smoke test. Done means the native app exists so the prepared components can be submitted for review.

Written by the indexing model from the issue text.