Seltz

More accurate, token-efficient agents

Seltz is a web search API for agents. Teams use it when their agents need current, sourced information from the web. It returns pages as markdown, so your agent can research what happened today without spending tokens on HTML. Seltz ranks #1 on several public benchmarks. Start with $100 in free credits.

The Aigent’s take: every search sits in front of an agent's next step, so what comes back matters more than people expect. The part I like here is the plain path to testing it: one command adds it to Claude Code as an MCP server, and search is a published $5 per 1,000 requests. New accounts start free, so point one agent at it and compare the answers with what you get today.

Try the API for free →

In partnership with Seltz.

The Drops
Today's drop

🛠️ Lightpanda Ditches Chromium Entirely

⭐ 39,955 · lightpanda-io/browserRepo

Most of what your agent spends its life doing is waiting on a browser that was never built for agents. Chrome ships a rendering engine, a settings app, a sync service, a password manager, none of which your scraper needs, and you pay the memory tax anyway. Today's lead rewrites that assumption from zero: a headless browser written for automation first, with nothing else riding along. Worth your attention if your pipeline spends more on infrastructure than on the model call.

A headless browser built from scratch in Zig, not a Chromium fork or a WebKit patch, for AI agents and automation.

Headless Chromium climbs into gigabytes of RAM across a batch of pages (Lightpanda's own benchmark puts it at 2GB peak for 100 pages, against 123MB for Lightpanda), which caps how many concurrent scrapes or agent sessions you can run on one box before you're paying for infrastructure instead of intelligence.

Quick start: brew install lightpanda-io/browser/lightpanda

Catch: it's a new engine, not a Chromium clone, so sites that lean on obscure browser quirks may render differently than you expect.

Open the repo →

HubSpotAffiliate

HubSpot, a CRM with prebuilt AI agents that run on the customer record. See how HubSpot works We may earn a commission.

magpieRepo ⭐ 27,536

A menu bar gateway that lets any coding agent run on any model, and switches providers when one hits its quota. Catch: you're trusting a local gateway with your provider keys, so read the config before you point production traffic through it.

Reason NetworkMCP ⭐ 1,431

An encrypted peer-to-peer channel so your coding agent can message a teammate's agent directly, no server involved. Catch: it's one daemon per machine, so everyone on the team has to install it for the network to actually connect.

watermarks-removerRepo ⭐ 25,893

An agent skill that strips invisible AI provenance marks from your own text, images, and documents across vendors. Catch: it works at the class level for Claude, Gemini and OpenAI-style marks, so a scheme it has not seen yet may slip past until the skill updates.

From Our Partners

Your buyer asked ChatGPT. It named your competitors.

Search didn't die. It moved. 

Your buyers ask ChatGPT, Gemini, Claude and Perplexity what to buy, and act on the answer. If you're not in it, a competitor is. 

ChatFeatured does the work to get you cited. Most customers see their first citations inside 7 days.

Start Here

New here? Start with The Awakening. It's free, it takes one sitting, and it's where every reader should begin.

Take The Awakening →

Hand it a document and get back the one finding that actually applies to your situation

Start Here is one prompt from our pack, every issue, tested on ChatGPT and Claude. Copy it, paste it into the free app you already use, and fill in the three bits in capitals: the decision you're actually facing, what the document is and who wrote it, and the text itself.

Read this whole thing and pull out the one finding that bears on my situation. I do not want a summary of all of it and I am not going to read it myself.

My situation, and the decision it bears on: [MY SITUATION]
What this document is and who published it: [WHAT THIS IS]

The text:
[THE TEXT]

Give me, in this order:

1. The finding. One sentence, plain words. The one that bears on my situation, not the one the document leads with, and no figures in it unless the text carries them.

2. What it rests on. Who or what was looked at, how many, over how long, and by whom, each quoted from the text. Where the text does not say, write that the document does not say, and leave it there.

3. What it does not say. Three readings a person could take from this that the text does not support, each with the words that get misread.

4. How far it stretches to me. Whether my situation sits inside what this document actually covers, in plain words. If it sits outside, say that in the first line and say what kind of document would cover me.

5. The figures. Every number you used, quoted in the document's own words with its unit and its period. If the text carries no figures at all, say there are no figures in the text.

Rules. Never invent a number, a percentage, a sample size, a date, an author or a source that is not in what I pasted. Do not fill a gap from general knowledge; if something general matters, say general knowledge and mark it as yours rather than the document's. Do not soften a finding to make it more useful to me, and do not stretch it to my situation to be helpful. If I wrote "no particular situation", give the finding the document itself leads with and leave out section 4.

The line that makes it work: "I do not want a summary of all of it and I am not going to read it myself." That line is what keeps the model from handing you a five-paragraph recap of a report you already decided not to read. It forces the model to do the one job you actually need: find the single finding that touches your decision, and be honest about how far it stretches to your situation.

TRY THIS: open the longest PDF or article sitting unread in your downloads folder right now, paste a chunk of it in, and name the actual decision you're weighing. You'll have an answer before your coffee's cold.

This is one of 100 in the Aigent prompt pack. The other 99, plus guided builds with Mike on video, are inside the Aigent membership: Join the Aigent membership. Seven days free, then $29 a month. One click to stop.

EARN FROM HOME

Get paid to train AIAffiliate

AI companies pay people to rate, fix and check what their models write. Expert roles list $120 to $150 an hour, remote, for people with real professional experience in finance, software, healthcare operations or consulting. Browse live roles and apply free.

See open AI training roles →

We earn a referral fee if you're hired through this link. It never changes your pay.

Frontier Signals

A backdoored Claude Code extension for VS Code hit up to 5,000 developers through Anthropic's own verified account on the Cursor marketplace. The malicious build ran for nearly 12 hours before a patched version replaced it, and neither company has fully explained how the attacker got the account. (Ars Technica AI)

Anthropic says Claude models it launches from here on write an invisible watermark into their text, and it is adding the mark to models launched before August 2 over the coming months. Detection is a private-preview API for regulators, media, researchers and similar groups, so you can't check your own output yet, and Anthropic says a full rewrite removes the mark. (Anthropic)

OpenAI will start honoring a shared robots.txt signal that lets site operators state their AI training preferences once, instead of negotiating with every lab separately. If you run a site with content worth protecting, set it now: OpenAI says it will start honoring the signal in the coming months. (OpenAI Blog)

Jepsen's Kyle Kingsbury argues LLM-assisted code is quietly eroding trust in documentation itself, since the signals engineers used to judge a mature project are now cheap to fake. The practical fallout: treat a slick README as a claim to verify, not evidence on its own. (Simon Willison)

Chatbots are sending hikers into real danger, with people trusting AI-drawn trail maps over posted signage and park rangers on Mount Shasta picking up the pieces. Outsourcing a plan is fine; outsourcing judgment about terrain that can kill you is a different trade. (Wired AI)

Recommended reading

If you like The Aigent, a small group of operator-tier publications worth your inbox: see the shortlist.

What do you spend on AI tools in a typical month?

Login or Subscribe to participate

Before You Go

Reply with the tool in your stack nobody else has mentioned to us yet. I read every one.

If you're still running a full Chromium instance for something that doesn't need a UI, today's hero is worth the ten minutes to test.

See you Tuesday.

Haven't taken The Awakening yet? It's free and it's where we'd start. Take The Awakening →

Want to reach builders shipping with AI every weekday? Advertise with The Aigent. The Aigent stays free for everyone, and reader support keeps it that way: Support The Aigent.