[APP] Context.dev

**Name of app / service**

Context.dev

**Link to developer documentation**

https://docs.context.dev

Website: https://context.dev
API base URL: https://api.context.dev/v1
Authentication: API key sent as a Bearer token

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

The current workaround is to use generic HTTP or Node.js steps and manage the Context.dev API key manually. This works, but it does not provide Pipedream managed authentication, native action discovery, reusable input fields, or verified components in the Pipedream marketplace. A registered Context.dev app is required before we can contribute official actions and event sources to the Pipedream registry.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

Initial actions:
- Search the web
- Scrape a page as Markdown
- Crawl a website
- Discover pages from a sitemap
- Extract structured data
- Parse a document
- Retrieve a brand profile

Event sources:
- Website change detected
- Monitor run completed
- Batch completed

Follow-up components can cover screenshots, page images, HTML, style guides, fonts, industry classification, monitors, batch jobs, people enrichment, and WebDBs.

We plan to contribute and test the component implementation in the Pipedream registry once the Context.dev app and managed API-key authentication are available.

Start with the Context.dev developer documentation and API base URL, confirming Bearer-token authentication and the requested initial actions and event sources. Done means a registered Context.dev app with managed API-key authentication and the requested official components available in the Pipedream registry.

Written by the indexing model from the issue text.