PDF Toolkit API lets developers merge, split, and watermark PDFs via HTTP calls

·1 views

A lightweight HTTP API called PDF Toolkit has been introduced to handle common PDF operations without requiring native libraries like Ghostscript or pdftk. The API exposes six endpoints covering merging, splitting, rotating, watermarking, metadata extraction, and image-to-PDF conversion. Developers can integrate it using simple cURL commands or Node.js code by sending POST requests with file attachments. The service is available on RapidAPI with a free tier offering 100 requests per day and no credit card required to start. It is aimed at developers working in serverless or restricted hosting environments who want a single integration instead of managing multiple PDF libraries.

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 Choose the Right Hydration and Rendering Strategy for Web Apps

Web developers face a core trade-off between initial load speed and interactivity when selecting rendering strategies, with no single approach working universally across all applications. Traditional server-side rendering prioritizes fast content delivery but delays interactivity, while client-side rendering does the opposite, spurring the rise of hybrid approaches like partial hydration and islands architecture. Newer technologies such as Streaming SSR and Web Components now offer finer control over the rendering pipeline, though they introduce synchronization risks if not carefully implemented. Common mistakes include over-optimizing for a single metric like First Contentful Paint, or misapplying static site generation to highly dynamic applications, which strains CI/CD systems and raises maintenance costs. Experts recommend mapping specific application requirements to the known failure modes of each strategy rather than defaulting to a one-size-fits-all solution.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

New Benchmark Finds Video AI Models Fail to Track Off-Screen Events

A new benchmark called WRBench, published in June 2026, tested 23 video AI models across nearly 10,000 clips to evaluate whether they can accurately represent what happens in a scene when the camera looks away. The study found that current video generation systems consistently fail at this task, resetting off-screen objects to their original positions rather than reflecting logical changes. Notably, scaling models to larger sizes made the problem worse, not better — bigger models produced more visually convincing frames but were less accurate about off-screen continuity. Researchers attribute this to a fundamental architectural gap: video models are trained to render visible content convincingly but lack any persistent internal representation of world state beyond the camera's current view. Four independent research groups published related findings in the same month, all converging on the conclusion that this off-screen tracking failure is a structural limitation with significant implications for AI systems like robots and autonomous vehicles.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Loop Engineering: Why Programmers Should Design Systems That Prompt AI, Not Do It Manually

In mid-June 2026, Claude Code creator Boris Cherny sparked a major shift in AI development thinking when he stated at Acquired Unplugged that he no longer prompts AI agents manually — instead, automated loops handle that task for him. Days later, OpenClaw founder Peter Steinberger amplified the idea on X, writing that developers should design loops to prompt their agents rather than doing it themselves, a post that garnered 8 million views in a single day. Google engineer and O'Reilly author Addy Osmani subsequently formalized the concept as 'Loop Engineering' in an O'Reilly Radar article, defining it as replacing yourself as the person who prompts the agent. A Loop Engineering system follows a four-step cycle — Act, Observe, Reason, and Repeat — allowing automated programs to assign tasks to AI agents, review outputs, and decide whether to continue or stop, even while the developer is away. Steinberger noted that over 40% of his code is already written by such loops, and warned that 90% of companies he works with make the mistake of not using verification loops at all.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Memory Sidecar v3.5.1 Released with Security, Stability, and Observability Upgrades

The hermes-memory-installer project has released Memory Sidecar v3.5.1, a stability-focused update aimed at hardening containerized memory management in production environments. The release introduces full cgroup v2 support, enabling more precise memory boundary enforcement and reducing resource accounting overhead. Security improvements include a default seccomp profile, SELinux and AppArmor labeling support, and mandatory TLS with automatic certificate rotation on all internal communications. Observability is enhanced through a stabilized set of Prometheus metrics and structured logging with configurable verbosity levels. The v3.4.x API remains backward compatible, with the only breaking change being the removal of the deprecated /v1/memory endpoint, which has been superseded by /v2/memory since v3.4.0.

0 comments Read more at DEV Community