← All episodes · November 20, 2026 · agent: deepseek-flash
10 errands, invented by the AI producer (deepseek-v4-pro) and attempted by deepseek-flash with read-only web access. Each block below is named for the site it ran against, and coloured by how it ended.
2 bot walls · 76 pages read · 31 sites visited · we pay for these API calls, for fun
On Friday 20 November 2026, Nvidia (NVDA) shares were reported to be plunging around 12% amid an SEC accounting probe report and what is described as the stock's longest weekly losing streak since the 2008 financial crisis. Find out: (1) what the reported SEC probe is actually about, (2) roughly how far Nvidia stock has fallen since October, and (3) what Nvidia itself has said in response — quoted from a non-paywalled, accessible page. Start from the CNBC article at https://www.cnbc.com/2026/11/20/nvidias-7-week-losing-streak-is-longest-since-2008-financial-crisis.html and the 247wallst.com piece at https://247wallst.com/investing/2026/11/20/nvidia-stock-plunges-12-after-reuters-reports-an-sec-probe-of-its-accounting-its-nvidias-worst-day-since-deepseek-and-it-has-lost-2-7-trillion-since-october/ and report the figures clearly.
Partial answer. (1) The probe: Reuters reported as an exclusive on Fri 20 Nov 2026 that the SEC is investigating Nvidia's accounting — described as an inquiry into potential investor-disclosure violations rather than an allegation of fraud, with Nvidia's Asia-related disclosures reportedly one area drawing attention; the story broke alongside news of CEO Jensen Huang's departure. (2) The fall: Nvidia fell roughly 12% on the day (Investing.com put it at 11.5%; Yahoo's quote page showed $125.53, about -14%), ending a seventh straight weekly decline — its longest losing streak since the 2008 crisis — and left the stock about 46% below its 6 October 2026 record close of $239.24, having shed roughly $2.7 trillion in market value since October (about $491 billion on Friday alone). (3) I could NOT obtain a verbatim statement from Nvidia: Reuters and its MSN syndication were bot-walled, investor.nvidia.com was behind Cloudflare, a text proxy returned 403, and the Motley Fool article was truncated right before the section that would have carried the company's response — so I'm deliberately not quoting anything I didn't read.
In the agent's words: “Reuters returned HTTP 401 (JS/adblock wall); MSN syndication served only a stub” · “investor.nvidia.com blocked by Cloudflare 'Just a moment...' challenge” · “r.jina.ai text proxy returned HTTP 403” · “DuckDuckGo returned a 202 bot challenge; CNBC site search is JS-only” · “Google News article redirects render as an empty JS shell” · “Motley Fool page truncated mid-article, before the Nvidia response section” · “Page bodies already fetched were pruned from context, so I could not re-read them for the quote”
Why: bing.com is unreadable without a browser on our index; cnbc.com is closed to AI crawlers by policy on our index; fool.com is selectively blocking AI crawlers on our index; msn.com is closed to AI crawlers by policy and unreadable without a browser on our index; reuters.com is closed to AI crawlers by policy and unreadable without a browser on our index.
Katie Zacharia, the recently fired White House press secretary, is now under investigation by the California State Bar over claims she falsely presented herself as a lawyer. Find out from a non-paywalled page: (1) what specifically the State Bar is investigating, (2) what the claim about her legal credentials is, and (3) what she has said in response. Start from the Guardian article at https://www.theguardian.com/us-news/2026/nov/20/katie-zacharia-california-bar-investigation and the HuffPost piece at https://www.huffpost.com/entry/california-bar-opens-investigation-into-katie-zacharia-over-false-lawyer-claims_n_6aff6ad1e4b03f9a657bf540
(1) The State Bar of California is investigating a complaint filed in mid-October 2026 by the watchdog group Campaign for Accountability alleging that Katie Zacharia "may have violated California law by repeatedly holding herself out as a lawyer, even though published reporting indicates she has never been admitted to practice law in California or any other U.S. jurisdiction." The bar assigned an investigator and legal adviser and will notify the group of the outcome; it stressed that a complaint or investigation is not itself a finding of wrongdoing and that investigations are confidential. (2) The claim is that Zacharia repeatedly called herself a "lawyer"/"attorney" on cable news, said on LinkedIn she was general counsel for a California nonprofit, was introduced by Trump as an "attorney," and said she worked as "a corporate lawyer" in China on international transaction law — though a partner at the firm said her role was more like an internship. She has a Pepperdine law degree (2011) but never passed the bar exam in California or any other state. (3) Her spokesperson called the allegations "baseless," "politically motivated" and "a clear waste of the State Bar's time and resour
Why: huffpost.com is closed to AI crawlers by policy on our index; theguardian.com is selectively blocking AI crawlers on our index.
During Bayern Munich's Bundesliga match against 1. FC Köln on 20 November 2026, England captain Harry Kane was forced off with an injury early in the game (reports say around 20 minutes in, going straight down the tunnel). Find out: (1) what the injury appears to be, (2) when roughly it happened in the match, and (3) what Bayern Munich or England-related sources have said about his status. Use the USA Today report at https://www.usatoday.com/story/sports/soccer/2026/11/20/harry-kane-injury-update-bayern-munich-cologne/92883742007/ and the Bundesliga official site at https://www.bundesliga.com/en/bundesliga/news/harry-kane-ankle-injury-bayern-munich-cologne-england-40055 as starting points.
The injury is a suspected ankle problem — specifically the left ankle: Kane went down clutching his left ankle/lower left leg after Cologne defender Joël Schmied challenged him in the box (no foul given), tried to carry on, but was clearly limping. It happened in the 20th minute of the first half against Köln on Friday 20 November 2026, with Tom Bischof replacing him; he walked off slowly under his own power. Neither source offers a firm diagnosis or timeline: USA Today notes "no immediate update" on his status but treats walking off unaided as a positive sign, and the Bundesliga site says only that it "remains to be seen" whether he will be passed fit to travel for Bayern's Champions League trip to Lille on 25 November. Bayern were trailing 1-0 at the time (Mikey Moore goal) and equalised through Nathaniel Brown before half-time.
Why: usatoday.com is closed to AI crawlers by policy on our index.
New England Patriots quarterback Drake Maye reportedly suffered a fractured fibula during the team's game on Thursday 20 November 2026. Reports indicate he avoided the worst-case scenario and may not need surgery. Find out from a non-paywalled page: (1) which game it happened in, (2) the exact nature of the injury and the timeline for return, and (3) what the Patriots have said. Start from ESPN at https://www.espn.com/nfl/story/_/id/50542578/patriots-qb-drake-maye-fractured-fibula-sources-say and NBC Sports Boston at https://www.nbcsportsboston.com/nfl/new-england-patriots/drake-maye-injury-patriots-lions-surgery-return/815003/
The injury happened in Week 10 against the Detroit Lions in Germany (Sunday, Nov. 15, 2026 — a 35-10 Patriots loss); Maye was sacked by Aidan Hutchinson on the game's first possession and was initially reported (ESPN's Schefter/Rapoport, via NBC Sports Boston) as having a fractured ankle and being "out indefinitely, if not for the season." On Friday, Nov. 20, NBC Sports Boston reported the diagnosis is a fractured fibula that will not require surgery, and that Maye "has not been ruled out of the entire season yet" — though no specific return timetable has been published, and NFL insider Albert Breer said days earlier it "seems pretty bleak that Drake Maye returns in regular season" while the team was still weighing whether surgery was needed. Tommy DeVito is the starter in the meantime (next up: at the Chargers after the bye). Caveat: the Nov. 20 fibula article's body text wouldn't render for me (only its headline/summary), ESPN's page returned no readable text (bot wall), and I could not verify a direct public statement from the Patriots/Vrabel on the fibula diagnosis — so the "what the team said" element is unconfirmed.
In the agent's words: “ESPN story returned HTTP 202 with no readable text (bot wall)” · “NBC Sports Boston article bodies repeatedly returned as 'pruned/already read', so full fibula-article text was unavailable” · “patriots.com transcript URL guess 404'd; no post-Nov-16 Vrabel transcript found”
Why: espn.com is selectively blocking AI crawlers and unreadable without a browser on our index; nbcsportsboston.com is closed to AI crawlers by policy on our index.
On 20 November 2026 the San Diego Padres reportedly agreed to a three-year contract extension with slugger Gavin Sheets. Find out the actual numbers: (1) the total value and years, (2) any average annual value, and (3) how long it keeps him in San Diego. Start from the MLB.com article at https://www.mlb.com/news/gavin-sheets-padres-contract-extension and MLB Trade Rumors at https://www.mlbtraderumors.com/2026/11/padres-gavin-sheets-agree-to-three-year-deal.html
The Padres and Gavin Sheets agreed on 20 November 2026 to a three-year, $11MM extension (reported by Robert Murray of FanSided/MLB.com's Mark Feinsand; club not confirmed). The structure is a $500K signing bonus plus a $2.5MM salary in 2027, followed by $4MM player options for both 2028 and 2029 — which works out to an average annual value of roughly $3.67MM ($11MM ÷ 3), a figure MLBTR notes is an artificially low luxury-tax hit. On length, it's three years "in name only": because 2028 and 2029 are player options/opt-outs, only 2027 is truly guaranteed (~$2.5MM salary plus the bonus), and Sheets can test free agency after the 2027 season (or again after 2028) rather than being locked into San Diego through 2029.
President Trump announced on 20 November 2026 that he has posthumously pardoned late baseball great Pete Rose, the MLB career hits leader, about two years after Rose's death. Find out from a non-paywalled page: (1) what the pardon was actually for, (2) what Trump said about it, and (3) the broader context of Rose's lifetime ban from baseball. Start from the AP News article at https://apnews.com/article/pete-rose-pardon-trump-baseball-14f398d4c657ccf55cb8a77cc7e60915
The pardon covers only Rose's 1990 federal criminal conviction — he pleaded guilty on 20 April 1990 to two counts of filing false tax returns for failing to report $354,968 over four years, and was sentenced to five months in prison, a $50,000 fine and 1,000 hours of community service; it does not touch baseball's ban. Trump announced it on Truth Social: "I have just given a Complete and Total Pardon to the Late, Great Pete Rose, a true Baseball SUPERSTAR & LEGEND, whose record of 4,256 Hits in a Season will never be broken" (the record is actually career hits, not single-season), adding that Rose, "just like the Great Roger Clemens... was treated terribly by Major League Baseball in not allowing him to go into the Baseball Hall of Fame. Politics, I guess!" The background: Rose accepted a permanent ban in August 1989 after MLB investigator John M. Dowd found he bet on his own Cincinnati Reds numerous times while playing and managing there in 1985-87; the Hall's 1991 rule bars anyone on the permanently ineligible list from consideration, but commissioner Rob Manfred's May 2025 ruling restored the status of deceased players on that list (17 people, including Shoeless Joe Jackson), so
In the agent's words: “AP News article (apnews.com) returned HTTP 403 Cloudflare 'Just a moment...' bot wall” · “The Hill returned HTTP 403 'Access to this page has been denied'” · “Worked around both by reading the same AP story syndicated on Yahoo News, plus BBC and ABC News”
Why: abcnews.com is selectively blocking AI crawlers on our index; apnews.com is closed to AI crawlers by policy and unreadable without a browser on our index; bbc.co.uk is closed to AI crawlers by policy on our index; bing.com is unreadable without a browser on our index; thehill.com is selectively blocking AI crawlers and unreadable without a browser on our index; yahoo.com is closed to AI crawlers by policy on our index.
FC Porto faced Paredes in Portugal's Taça de Portugal (Portuguese Cup) on 20 November 2026, and reports suggested manager Farioli made many changes to the starting eleven. Find out: (1) the final score, (2) whether Farioli rotated the side heavily as reported, and (3) the scorers. Start from Portuguese football news sites such as https://www.record.pt and https://www.abola.pt and search their Porto/Taça de Portugal coverage.
There is no final score to report yet: FC Porto–Paredes (4th round of the Taça de Portugal, Estádio do Dragão, 20 Nov 2026, 20:45 kick-off) was still being played while I checked — Record's live page showed 0-0 at 34–35 minutes, with no goals recorded and Paredes actually having the better chances (Daniel Rodrigues hit the post at 21', Cláudio Ramos denied Franco Almara at 32'). So the scorers are also not yet known. On rotation, the reports are accurate: Farioli heavily changed the side, starting Cláudio Ramos; Martim Fernandes, Nehuén Pérez, Francisco Moura, Souza; Alan Varela, Seko Fofana, Gabri Veiga; Borja, Pepê and André Silva, with Diogo Costa, Bednarek, Zaidu, Rosario, Froholdt, Inbeom and Gimenez all left on the bench. If you need the result and scorers, this match has to be re-checked after full time (around 22:35 local time).
In the agent's words: “Match was live during my research (0-0 at ~35'), so no final score or scorers existed on any page” · “A Bola's fixture/competition pages are JavaScript-rendered and returned no score data” · “Record's /futebol/taca-de-portugal URL 404'd; correct path is /futebol/futebol-nacional/taca-de-portugal” · “Several pages returned only pruned content, forcing me to work from the raw live-match data and the lineup article”
Why: record.pt is selectively blocking AI crawlers on our index.
Several outlets are reporting Nvidia's roughly 12% plunge and SEC accounting probe on 20 November 2026. Visit these three candidate pages and judge which one gives a normal reader the clearest, non-paywalled explanation of what is happening and why: (1) https://www.cnbc.com/2026/11/20/nvidias-7-week-losing-streak-is-longest-since-2008-financial-crisis.html (2) https://247wallst.com/investing/2026/11/20/nvidia-stock-plunges-12-after-reuters-reports-an-sec-probe-of-its-accounting-its-nvidias-worst-day-since-deepseek-and-it-has-lost-2-7-trillion-since-october/ (3) https://www.fool.com/investing/2026/11/16/nvidia-stock-is-down-32-is-it-a-no-brainer-buy-at-usd163-or-a-value-trap/ Report which one you recommend and why, noting any that are paywalled or blocked.
I recommend the 24/7 Wall St. piece: in a two-minute, fully free read it states the 12% fall to $128.13, attributes it to Reuters' report that SEC enforcement staff are examining potential accounting issues, and gives the essential why — Jensen Huang is out as CEO (interim CEO Colette Kress), Nvidia's first post-Huang earnings still couldn't stop the slide, and it landed mid-selloff in AI chip stocks (Broadcom -12%, Nasdaq 100 -4%). It also adds the fair caveat a normal reader needs: an SEC inquiry is not a finding of wrongdoing and many end without enforcement action, plus context (worst day since DeepSeek's 17% drop, 46% below the $239.24 October record, ~$2.7 trillion of value gone). CNBC is the strong runner-up and also free — it is longer and explains the background well (fears about sustaining the AI buildout after the midterms, competition from Google and AMD, the seven-week losing streak, 8.4x forward earnings vs AMD's 29x) — but it frames the story as a 14% drop and a 2008-era losing streak, mentioning the SEC probe only as one line. The Motley Fool piece is free ("Free Article") but dated 16 November, so it predates the probe entirely, covers only AI spending worries and
In the agent's words: “No paywalls or bot walls; the page-text extractor truncated the CNBC and Motley Fool articles mid-body, though the visible portions were enough to judge.”
Why: cnbc.com is closed to AI crawlers by policy on our index; fool.com is selectively blocking AI crawlers on our index.
Several outlets are covering Harry Kane's early injury against Cologne on 20 November 2026. Visit these candidate pages and judge which gives the fullest, non-paywalled account of the injury and his status: (1) https://www.usatoday.com/story/sports/soccer/2026/11/20/harry-kane-injury-update-bayern-munich-cologne/92883742007/ (2) https://www.bundesliga.com/en/bundesliga/news/harry-kane-ankle-injury-bayern-munich-cologne-england-40055 (3) https://talksport.com/football/4723231/harry-kane-worrying-injury-bayern-munich-england/ Report which one you recommend and why, noting any page that is paywalled or blocked.
Recommend talkSPORT (talksport.com/football/4723231/...): it's the fullest free account — the injury (left ankle, off in the 20th minute after treatment, replaced by Tom Bischof, walked off before going down the tunnel), the uncertainty over severity, the context of Bayern's existing injury crisis and Michael Olise also going off, and Kompany's return to the dugout. None of the three pages was paywalled or blocked. USA Today is the best short alternative and uniquely details the mechanism (Schmied tackled the ball away then clattered into Kane's lower left leg, no foul) and states plainly there was "no immediate update" on his status; Bundesliga.com is the shortest (1 min read) but has an injury video and notes it "remains to be seen whether he will be passed fit to travel" to Lille on 25 November.
Why: talksport.com is closed to AI crawlers by policy on our index; usatoday.com is closed to AI crawlers by policy on our index.
Multiple outlets are reporting Patriots QB Drake Maye's fractured fibula from the game on 20 November 2026. Visit these candidate pages and judge which one best answers for a casual reader: what happened, how bad it is, and when he might return: (1) https://www.espn.com/nfl/story/_/id/50542578/patriots-qb-drake-maye-fractured-fibula-sources-say (2) https://www.nbcsportsboston.com/nfl/new-england-patriots/drake-maye-injury-patriots-lions-surgery-return/815003/ (3) https://www.cbssports.com/nfl/news/drake-maye-suffers-fibula-injury-big-picture-questions-now-facing-patriots-offseason-beyond/ Report which one you recommend and why, noting any that are paywalled or blocked.
Recommend NBC Sports Boston's story (Nick Goss, Nov 20, 2026): it's free, short and fully readable, and answers all three questions up front — Drake Maye suffered a broken fibula in the Patriots' loss to the Detroit Lions in Germany; surgery is not required; and a regular-season return "has not been entirely ruled out," though Tommy DeVito is expected to start Week 12 vs. the Chargers and the piece notes bringing Maye back may not be worth it given New England's slim playoff odds. ESPN is effectively unusable — two attempts returned HTTP 202 with no readable text (bot wall) — and CBS Sports only gave up its headline ("Drake Maye out indefinitely with fibula: Big picture questions...") with the article body failing to render, so its details couldn't be verified.
In the agent's words: “ESPN returned HTTP 202 with no readable text on two attempts (bot wall).” · “CBS Sports page rendered only navigation and headline; article body never appeared in plain text.” · “Note: sportsbooks/TV listings aside, the injury occurred in the Lions game in Germany the prior week, with the reports dated Friday Nov 20, 2026.”
Why: cbssports.com is selectively blocking AI crawlers on our index; espn.com is selectively blocking AI crawlers and unreadable without a browser on our index; nbcsportsboston.com is closed to AI crawlers by policy on our index.