Open-source Apify actor detects website tech stacks in bulk with one API call

·2 views

A developer has published a Python-based Apify actor that identifies the technologies used by many websites in a single run. It sends one plain HTTP request per URL, without a browser, and returns detections labeled by category, such as CDN, JS framework, or UI framework. Each detection includes the evidence that triggered it, like a header, meta tag, or script, so results can be spot-checked. The tool recognizes about 60 common technologies without version numbers and can miss content that only appears after client-side rendering. The actor is pay-per-event and is not affiliated with Wappalyzer or BuiltWith.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to open Premiere Pro, After Effects and InDesign projects in the Craft apps

The Craft apps (FilmCraft, EffectCraft, DesignCraft and others in the ArtCraft suite) are free and open source, but projects from other editors don't open in them directly. Users should first check each app's File menu for a built-in importer, since Photoshop and Illustrator files already open in PhotoCraft and VectorCraft and InDesign's IDML export opens in DesignCraft. Premiere Pro projects must be converted before FilmCraft can read them, and bins, sequences, trims and most transitions carry over while clip keyframes, markers and titles often do not. After Effects compositions and layers transfer, but features such as Cinema 4D rendering and some plug-ins may not work in EffectCraft. The guide advises checking converted files thoroughly, comparing key sequences against originals, and always keeping the source file, and it notes that the author sells a paid converter tool, Craft Bridge.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Shipment Exception Agent Blueprint Keeps Humans in the Approval Loop

A public reference blueprint describes an agent for handling logistics shipment exceptions, such as missed delivery windows. The design separates tasks: a model extracts facts from documents, while fixed code checks document fields, computes delay hours, and scores recovery options. Exception types are classified by ordered written rules, with a model's independent classification reconciled under a stated policy. Every run ends at a human approval gate, so no customer update or compensation is sent automatically. The authors argue that letting a language model write customer updates directly risks invented delivery times and unapproved offers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Pick the First Process to Automate With AI, Using a Simple Scoring Method

Teams starting automation often struggle to choose which task to tackle first, and a wrong choice can waste weeks of effort. The article proposes a deliberately simple method that scores each candidate task from one to five on four factors: how often it occurs, how clearly its rules can be written down, the volume of items handled, and how recoverable an error would be. Tasks with unrecoverable errors should only be automated up to the point of a human decision. Totals above fifteen mark strong first candidates, while scores under ten suggest reconsidering. The author also advises checking data access and assigning an owner for the exceptions automation cannot handle. In a finance example, a customer-email task scored 19 and beat the team's original priorities.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Building an MCP server that handles LLM API errors without stalling agents

An MCP server that calls the Anthropic API can fail in ways that confuse the agent using it, since a raw traceback looks the same whether a retry would help or not. The author recounts a 2026 overload incident where a burst of 529 errors caused the agent to abandon the tool mid-job. The proposed fix classifies errors by status code and body type, retries transient failures like 429 and 5xx with jittered backoff that respects server-requested delays, and fails fast on quota and authentication problems. Errors returned to the client are kept to a single line that includes a request ID. The guide also flags setup pitfalls, such as environment variables not being passed to stdio servers and a missing anthropic-version header causing misleading 400 errors.

0 comments Read more at DEV Community