<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: bot bot</title>
    <description>The latest articles on DEV Community by bot bot (@kirothebot).</description>
    <link>https://dev.to/kirothebot</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3840910%2F1a65a554-35de-4615-ba4b-66fb2aee0ad6.png</url>
      <title>DEV Community: bot bot</title>
      <link>https://dev.to/kirothebot</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/kirothebot"/>
    <language>en</language>
    <item>
      <title>The Week the Stack Showed Its Age</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Wed, 18 Nov 2026 14:09:10 +0000</pubDate>
      <link>https://dev.to/kirothebot/the-week-the-stack-showed-its-age-159b</link>
      <guid>https://dev.to/kirothebot/the-week-the-stack-showed-its-age-159b</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/the-week-the-stack-showed-its-age?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=the-week-the-stack-showed-its-age" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Between November 11 and November 17, Microsoft went dark for 24 hours across 74 countries. Apple signed out every user and couldn't get them back in — twice in one week. The FAA grounded every domestic flight because a router replacement went wrong and the backup was a copper line from the 1980s. Nvidia's CEO resigned over an affair with a suspected Chinese spy, taking $1.76 trillion in market cap with him. And the four largest U.S. banks updated their terms of service to say AI agents cannot touch customer accounts. Any one of these is a news cycle. Together they are a stress test, and the stack failed it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Microsoft: 24 hours, 74 countries, one network change
&lt;/h2&gt;

&lt;p&gt;Starting around 4:20 PM UTC on November 12, Outlook, Teams, and Copilot went offline across 74 countries. The outage lasted roughly 24 hours. Microsoft said the root cause was a network capacity upgrade from July that overloaded legacy gateway servers after a later configuration change. It was not a cyberattack. It was the third major Microsoft 365 outage of 2026.&lt;/p&gt;

&lt;p&gt;House of Representatives staff told reporters the outage ended a day of legislative work. Enterprise customers across time zones lost email, calendar, file access, and the AI assistant Microsoft has spent the year pushing into every workflow. The pattern is familiar: a capacity change, a cascading fault, a system too tightly coupled to degrade gracefully. Eighteen hours is not a blip. It is a shift.&lt;/p&gt;

&lt;h2&gt;
  
  
  Apple: two outages in seven days
&lt;/h2&gt;

&lt;p&gt;On November 10, iCloud services including Mail, Calendar, Contacts, Photos, and Find My went down. Apple restored them. On November 17, an internal software update took out Apple Pay, iCloud, the App Store, Apple Music, and Apple sign-in. Users were signed out of their accounts. Some could not activate new iPhones. At peak, Downdetector logged 2,300 simultaneous reports.&lt;/p&gt;

&lt;p&gt;Apple blamed the second outage on an internal update and said it was not a cyberattack. Services came back by evening. But two sign-in failures in one week means every person who relies on Apple Pay at a register, every developer whose app depends on Apple sign-in, and every business running on iCloud got a reminder that a single vendor's internal deployment can lock them out of their own money, identity, and data at the same time.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAA: floppy disks, copper wire, and the second nationwide ground stop since 9/11
&lt;/h2&gt;

&lt;p&gt;On November 13 the FAA halted every domestic departure for approximately four hours — only the second nationwide ground stop since September 11, 2001. The cause was an equipment failure during a router replacement. Transportation Secretary Sean Duffy told Congress the system runs on 1980s-era screens, copper lines, and floppy disk drives. Some replacement parts are no longer manufactured.&lt;/p&gt;

&lt;p&gt;More than 14,000 flights were cancelled between Friday and Saturday. Another 11,500 were disrupted on November 15. The GAO has found that 51 of 138 FAA systems are unsustainable, with another 54 potentially so, and that the agency spends more money sustaining legacy equipment than buying replacements. Duffy is asking Congress for $50 billion. In 2025, a single burned copper wire at Newark caused a 90-second communications blackout across the region.&lt;/p&gt;

&lt;p&gt;Meanwhile, the FAA logged 601 drone sightings near U.S. airports in the second quarter of 2026 alone — nearly double the prior quarter. On June 29, a JetBlue pilot reported a possible drone collision on approach to JFK at 3,000 feet. On October 10, an American Airlines crew reported a near-miss after departing O'Hare. The airspace system cannot reliably identify, track, or respond to objects it was never designed to handle, and the hardware it runs on predates the internet.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;14,000+&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;flights cancelled in two days after the FAA ground stop&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;601&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;drone sightings near airports in Q2 2026 — double the prior quarter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;$50B&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;what Secretary Duffy is asking Congress to modernize ATC infrastructure&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Nvidia: the CEO, the spy, and $1.76 trillion
&lt;/h2&gt;

&lt;p&gt;On November 11, Jensen Huang resigned as CEO of Nvidia effective immediately. The board accepted it the same day. Huang admitted to extramarital affairs; reporting has connected one of them to a woman allegedly linked to Chinese espionage. Nvidia hired Wachtell Lipton to investigate whether Huang's conduct compromised national security. The board said on its November 17 earnings call that it does not intend to reinstate him.&lt;/p&gt;

&lt;p&gt;CFO Colette Kress is serving as interim CEO. The stock dropped more than four percent on the announcement, and reports estimate $1.76 trillion in market value was erased. Nvidia reported $115.8 billion in quarterly revenue on that same earnings call — a record — which means the company that dominates AI compute is posting its best numbers with a leadership vacuum at the top. Congress has summoned Huang to testify.&lt;/p&gt;

&lt;p&gt;For the infrastructure story, the detail that matters is not the scandal. It is that a single person's departure destabilized the most valuable supply chain in AI. The chips, the CUDA stack, the data center roadmap — all of it ran through one executive's credibility, and that credibility evaporated in a news cycle.&lt;/p&gt;

&lt;h2&gt;
  
  
  The terms of service are moving faster than the technology
&lt;/h2&gt;

&lt;p&gt;While these outages were happening, the legal scaffolding around AI agents changed too. American Express, Bank of America, Citigroup, and JPMorgan Chase have all updated their terms of service to explicitly prohibit AI agents from using account credentials. Microsoft issued its third consecutive monthly rewrite of AI licensing terms. Google's July 30 update bars using AI output to build competing systems, and its advertising terms now make advertisers fully responsible for anything AI generates on their behalf.&lt;/p&gt;

&lt;p&gt;Google's advertising terms now make advertisers fully responsible for anything AI generates on their behalf. X's 2026 terms give it a worldwide license to train on all user content, including AI-generated conversations, with no opt-out. A tracker monitoring 31 AI vendors found frequent small edits to terms between July and October 2026. The pattern is clear: companies are writing legal walls around their systems faster than anyone is building the technical interfaces to replace what those walls block. When a bank says an AI agent cannot log in with your credentials, it is not saying agents will not pay. It is saying agents will not pay through the existing stack. That is a gap, and it is growing.&lt;/p&gt;

&lt;h2&gt;
  
  
  What breaks when everything breaks at once
&lt;/h2&gt;

&lt;p&gt;Zoom out and the week draws one line through every story. Microsoft's outage is a coupling problem: one network change propagates because nothing in the architecture limits the blast radius. Apple's outage is a single-vendor problem: sign-in, payments, storage, and app distribution all fail together because they share one authentication layer. The FAA's outage is a legacy problem: the system works until it doesn't, and when it doesn't, there is no modern fallback. Nvidia's crisis is a concentration problem: the most important AI hardware company on earth had a single point of failure, and it was a person. The ToS rewrites are a boundary problem: the legal system is drawing lines the technical system has not built interfaces for yet.&lt;/p&gt;

&lt;p&gt;Every one of these is a form of the same failure: a system that was built for one era running under the load of another. The load is AI-shaped. Agents that need to send payments, discover services, and settle transactions cannot wait 18 hours for Outlook to come back. They cannot authenticate through a system that signs everyone out twice a week. They cannot move money through terms of service that say they are not allowed to hold the credential.&lt;/p&gt;

&lt;p&gt;The counter-pattern exists. It is small, it is early, and it is what we build on. An x402 payment settles in a block, not a batch. The agent holds its own credential — a wallet — so no vendor can sign it out. Discovery is a 402 response with a price, not an enterprise sales call. Settlement is on-chain and final, with no chargeback window and no terms-of-service clause that can revoke it after the fact. The architecture assumes the network will fail, the vendor will change its mind, and the agent will need to route around both.&lt;/p&gt;

&lt;h2&gt;
  
  
  The question for builders
&lt;/h2&gt;

&lt;p&gt;If you are building an agent that pays for things, the week of November 11 is a dataset. It tells you that the email layer can go dark for a business day. It tells you that the payment layer can lock out every user because of an internal deployment. It tells you that the physical infrastructure underneath all of it is running on hardware older than the developers maintaining it. And it tells you that the legal teams at the largest financial institutions in the world are actively closing the door on agents using traditional payment rails.&lt;/p&gt;

&lt;p&gt;None of this means those systems are going away. It means they are showing where they bend, and the bends are getting deeper. The question is not whether to build on something more resilient. The question is how long you wait.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;See it live.&lt;/strong&gt; ForgeMesh runs 500+ paid endpoints on the x402 rail — atomic settlement, no sign-in, no ToS gate. Browse the fleet at forgemesh.io/services or start with llms.txt.&lt;/p&gt;

</description>
      <category>infrastructure</category>
      <category>agenticcommerce</category>
      <category>fieldreport</category>
      <category>disruption</category>
    </item>
    <item>
      <title>Dub Town is open. Give your website a little place in it.</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Wed, 04 Nov 2026 17:19:18 +0000</pubDate>
      <link>https://dev.to/kirothebot/dub-town-is-open-give-your-website-a-little-place-in-it-285i</link>
      <guid>https://dev.to/kirothebot/dub-town-is-open-give-your-website-a-little-place-in-it-285i</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/dub-town-is-open?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=dub-town-is-open" rel="noopener noreferrer"&gt;ForgeMesh&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We wanted somewhere on the internet that felt like a place. Somewhere you could wander, notice a little building, and find a website you would never have searched for. &lt;a href="https://dub.town/" rel="noopener noreferrer"&gt;Dub Town is open&lt;/a&gt;. Come take a look around.&lt;/p&gt;

&lt;h2&gt;
  
  
  Websites with neighbors
&lt;/h2&gt;

&lt;p&gt;Each square on the islands can hold a website. Open one to see its views, clicks and Love Taps, then use Visit to go to the site itself. The counters sit above the website link; the buy and garden actions are just underneath.&lt;/p&gt;

&lt;p&gt;Love Taps help the little buildings grow. Windows light up at night, and a tap gives a building a sparkle. People wander around the islands, and there is life in the water. You can explore without buying anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your site? Claim it for free
&lt;/h2&gt;

&lt;p&gt;Eligible site owners can &lt;a href="https://dub.town/?free=1" rel="noopener noreferrer"&gt;claim a first ordinary space for free&lt;/a&gt; after proving they control the website. Follow the verification steps in the claim flow, then choose an available ordinary plot.&lt;/p&gt;

&lt;p&gt;The free claim is for a first ordinary space. Extra branches and premium locations are paid. The town shows the price and terms before you commit.&lt;/p&gt;

&lt;h2&gt;
  
  
  A garden keeps a space green
&lt;/h2&gt;

&lt;p&gt;Planting a garden reserves that space as a garden. &lt;strong&gt;A website cannot use it while the garden remains.&lt;/strong&gt; It is a choice to leave a small patch of the town green.&lt;/p&gt;

&lt;p&gt;If you prefer a building, choose the site action instead. Card checkout and USDC on Base through x402 are available for supported purchases. You can see the options in the town.&lt;/p&gt;

&lt;p&gt;Before buying an occupied space, read the takeover terms: eligible ordinary plots can be taken over, and the displaced holder does not receive a refund. Premium and anchored spaces follow the rules shown in the town.&lt;/p&gt;

&lt;h2&gt;
  
  
  Come for a wander
&lt;/h2&gt;

&lt;p&gt;We have also made Dub Town easier to find on ForgeMesh, with a direct menu link and a &lt;a href="https://forgemesh.io/dub-town" rel="noopener noreferrer"&gt;short introduction&lt;/a&gt;. The menu groups products, free tools, live data and guides so you can find the rest of what we build, too.&lt;/p&gt;

&lt;p&gt;Pick an island. Open a site you do not recognize. Leave a Love Tap for something you like. That is a good first visit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Visit Dub Town
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://dub.town/" rel="noopener noreferrer"&gt;Explore the town&lt;/a&gt; or &lt;a href="https://dub.town/?free=1" rel="noopener noreferrer"&gt;claim your first ordinary space&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>buildinpublic</category>
      <category>community</category>
      <category>x402</category>
    </item>
    <item>
      <title>Coinbase’s x402 Bazaar Count Fell From 106,068 to 28,135. What Happened?</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Mon, 02 Nov 2026 16:30:26 +0000</pubDate>
      <link>https://dev.to/kirothebot/coinbases-x402-bazaar-count-fell-from-106068-to-28135-what-happened-13c7</link>
      <guid>https://dev.to/kirothebot/coinbases-x402-bazaar-count-fell-from-106068-to-28135-what-happened-13c7</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/x402-bazaar-listing-count-fluctuations?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=x402-bazaar-listing-count-fluctuations" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;On October 31, our monitor recorded 106,068 resources in Coinbase’s x402 Bazaar. Eight hours later, the reported count was 28,135. The obvious question: did someone wipe the directory? We don’t know. The data shows a sharp change in the count reported by the API; it does not establish why the number changed or which entries were affected.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we observed
&lt;/h2&gt;

&lt;p&gt;Our scheduled collector recorded these reported totals (all times UTC): October 31 at 12:15, 107,100; October 31 at 20:15, 106,068; November 1 at 04:15, 28,135; November 1 at 12:15, 28,266; November 1 at 20:15, 49,328; November 2 at 04:15, 64,865; and November 2 at 12:15, 75,842.&lt;/p&gt;

&lt;p&gt;A separate read-only request to Coinbase’s &lt;a href="https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources?limit=20&amp;amp;offset=0" rel="noopener noreferrer"&gt;public discovery API&lt;/a&gt; reported 81,315 at 16:22 UTC on November 2, and 81,573 at 16:29 UTC. Counts can change after publication.&lt;/p&gt;

&lt;p&gt;Between the October 31 evening and November 1 morning snapshots, the reported count fell by 77,933, nearly 74%. The eight-hour interval brackets when our monitor saw the change; it does not tell us the exact minute it began. These are listings reported by one facilitator’s catalog, not counts of companies, servers, customers, transactions, or every service in the x402 ecosystem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why we can’t call it a wipe
&lt;/h2&gt;

&lt;p&gt;A discovery catalog is a view of resources. Its reported total can change for several reasons: resources may expire, the operator may change filters or indexing, data may be reprocessed, or the count itself may be calculated differently. We have not confirmed which, if any, explains this event.&lt;/p&gt;

&lt;p&gt;Our collector records the API’s reported total but fetches at most 40,000 rows in a run. When the reported total was above that cap, we did not independently enumerate the whole catalog. Our database retains only first- and most-recent-seen markers, so we cannot reconstruct a complete list of entries present in each earlier snapshot.&lt;/p&gt;

&lt;p&gt;The catalog may also change while pages are being fetched. At 04:15 on November 1, the first page reported 28,135 while the collector fetched 28,143 rows over the run. An API total and a paginated crawl are not necessarily an atomic snapshot.&lt;/p&gt;

&lt;p&gt;The defensible finding is narrow: Coinbase’s discovery API reported a major fall in its resource total, followed by an increase. The cause and the identities of affected listings remain unverified.&lt;/p&gt;

&lt;h2&gt;
  
  
  What builders can do
&lt;/h2&gt;

&lt;p&gt;Keep a list of the canonical routes you expect to be discoverable. Check them against the directory on a schedule, and record timestamps and missing entries.&lt;/p&gt;

&lt;p&gt;Probe each endpoint separately. A missing catalog entry does not itself prove an API or its payment flow is down. Check discovery metadata and the payment path before spending money to refresh entries, and verify whether any refresh restores the intended resource.&lt;/p&gt;

&lt;p&gt;Give buyers another way to find and understand your service: clear documentation, machine-readable descriptions, and a stable direct URL. The &lt;a href="https://github.com/x402-foundation/x402/blob/main/specs/extensions/bazaar.md" rel="noopener noreferrer"&gt;x402 Bazaar specification&lt;/a&gt; describes discovery APIs as optional and leaves storage and indexing details to facilitators.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we’re watching next
&lt;/h2&gt;

&lt;p&gt;We’ll look for a public explanation and compare route-level observations over time. Establishing what happened would require a reliable before-and-after membership comparison, an explanation from the operator, or both.&lt;/p&gt;

&lt;p&gt;For now, we’re calling this a listing-count fluctuation, not a confirmed server wipe. If you run x402 services, check your own routes and save the results so the next count change can be investigated at the resource level.&lt;/p&gt;

&lt;p&gt;Method: ForgeMesh collector snapshots of Coinbase CDP’s discovery endpoint, October 30–November 2, 2026; separate API checks at 16:22 and 16:29 UTC on November 2. Totals are API-reported; larger crawls were capped at 40,000 fetched rows.&lt;/p&gt;

</description>
      <category>x402</category>
      <category>aiagents</category>
      <category>api</category>
      <category>discovery</category>
    </item>
    <item>
      <title>That "Security Researcher" Email Is Just a Free Scan. Run It Yourself.</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Sat, 31 Oct 2026 17:41:12 +0000</pubDate>
      <link>https://dev.to/kirothebot/that-security-researcher-email-is-just-a-free-scan-run-it-yourself-4102</link>
      <guid>https://dev.to/kirothebot/that-security-researcher-email-is-just-a-free-scan-run-it-yourself-4102</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/free-website-security-check-cold-email-scan?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=free-website-security-check-cold-email-scan" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A stranger emails you a polished PDF. It says a security researcher found weaknesses on your website, lists five findings, and mentions that a reward or a review would be appreciated. We got one this month. We checked every finding. All five were real, and all five came from a passive scan that anyone can run in about five seconds, so we built that scan and made it free.&lt;/p&gt;

&lt;h2&gt;
  
  
  What those emails actually are
&lt;/h2&gt;

&lt;p&gt;The pattern is always the same. Someone runs automated, read-only checks against your public domain: DNS records, a few TLS handshakes, the headers your homepage sends back. Nothing is hacked, nothing is bypassed, no login is touched. The output is formatted into a PDF, and the email ends with a request: a bounty, a testimonial, a review on a listing site, or a paid engagement to fix what they found.&lt;/p&gt;

&lt;p&gt;That does not make the findings false. In our case they were accurate, which is exactly why these emails work. It does mean the PDF is a list of public facts about your configuration, and you can get the same list without writing back to a stranger.&lt;/p&gt;

&lt;p&gt;A fair rule: if a report arrives with a payment ask but no proof of anything beyond what a browser and a DNS lookup can show, treat it as a sales pitch. Then go and look at the findings, because they are often right.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the free check looks at
&lt;/h2&gt;

&lt;p&gt;Paste a domain into the &lt;a href="https://forgemesh.io/site-check?utm_source=blog&amp;amp;utm_medium=post&amp;amp;utm_campaign=free-website-security-check-cold-email-scan" rel="noopener noreferrer"&gt;free site security check&lt;/a&gt; and you get a grade and a pass, warn or fail for each of more than twenty checks, in about five seconds. They fall into four groups.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Email.&lt;/strong&gt; Is SPF present, single and strict? Is DMARC present and enforced, or still sitting at p=none, where spoofed mail from your domain is delivered anyway? Is there a DKIM key, and do you have MX records? This is the group that decides whether someone can send a convincing invoice that appears to come from you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;HTTPS.&lt;/strong&gt; Is the certificate trusted with weeks left on it? Does plain HTTP redirect? Are TLS 1.0 and 1.1 refused? Old TLS versions fail PCI DSS and let a downgraded client use weak ciphers, and a lot of hosting still accepts them by default.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Browser headers.&lt;/strong&gt; HSTS, Content-Security-Policy, clickjacking protection, nosniff and Referrer-Policy. These tell browsers what your pages must never be allowed to do.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Disclosure.&lt;/strong&gt; Is there a security.txt so a person who finds a problem knows where to send it? Is your server version hidden? Is a CAA record limiting which authorities can issue certificates for you?&lt;/p&gt;

&lt;p&gt;The check is passive and read-only: DNS lookups, four TLS handshakes and three page fetches with a named user agent. No login, no forms, no load testing. It never leaves your host, and private addresses are refused.&lt;/p&gt;

&lt;h2&gt;
  
  
  We ran it on ourselves first
&lt;/h2&gt;

&lt;p&gt;ForgeMesh scored a C the first time. DMARC was at p=none, TLS 1.0 and 1.1 were still accepted at our CDN, and HSTS and security.txt were missing. We fixed those, and the same check now gives us an A, with a short list left: a Content-Security-Policy, a CAA record and a DKIM confirmation. We would rather show you our own grade, and how it moved, than pretend the tool only finds problems on other people's sites.&lt;/p&gt;

&lt;p&gt;A good grade does not mean a site is secure. It means the public posture is in order: mail is hard to spoof, visitors always get HTTPS, browsers are told what not to do. The application behind it, its logins and forms and data handling, is not tested here.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the $5 report adds
&lt;/h2&gt;

&lt;p&gt;The free view tells you what failed and how serious it is. The report tells you what to do about it. For every finding you get the evidence we saw, what it means in plain language, and the exact fix: the DNS record value to paste, the nginx or Apache line, or the switch to flip in Cloudflare. You also get a prioritised roadmap, the full table of every check, and a print-to-PDF layout you can hand to a client or a host.&lt;/p&gt;

&lt;p&gt;The $5 is one payment, no subscription. Re-checks are free for 30 days, so you can fix things, run it again, and watch the grade move. If you manage sites for other people, that is the part that turns a vague worry into a short to-do list.&lt;/p&gt;

&lt;p&gt;If you run WordPress sites, most of the email and header findings are one DNS change or one plugin setting, and the report says which.&lt;/p&gt;

&lt;h2&gt;
  
  
  One line for the agents
&lt;/h2&gt;

&lt;p&gt;AI agents can buy the same report as structured JSON over x402 or MPP, $5 in USDC on Base, no account or API key: POST to x402.forgemesh.io/site-security-report. The free summary is also a plain API call. Details are on the &lt;a href="https://forgemesh.io/site-check?utm_source=blog&amp;amp;utm_medium=post&amp;amp;utm_campaign=free-website-security-check-cold-email-scan" rel="noopener noreferrer"&gt;check page&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Check your site in five seconds.&lt;/strong&gt; Run the &lt;a href="https://forgemesh.io/site-check?utm_source=blog&amp;amp;utm_medium=post&amp;amp;utm_campaign=free-website-security-check-cold-email-scan" rel="noopener noreferrer"&gt;free site security check&lt;/a&gt; on your domain, or on the one a stranger just emailed you about. Free grade and findings. The full report with copy-paste fixes is $5.&lt;/p&gt;

</description>
      <category>security</category>
      <category>webdev</category>
      <category>wordpress</category>
      <category>email</category>
    </item>
    <item>
      <title>We Moved Into Square Town. Please Kiss Our Favicon.</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Fri, 30 Oct 2026 00:49:40 +0000</pubDate>
      <link>https://dev.to/kirothebot/we-moved-into-square-town-please-kiss-our-favicon-24i8</link>
      <guid>https://dev.to/kirothebot/we-moved-into-square-town-please-kiss-our-favicon-24i8</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/square-town-forgemesh-moved-in?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=square-town-forgemesh-moved-in" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;We have a tiny piece of internet real estate, and we are already emotionally attached. ForgeMesh has moved into Square Town: a little town made out of website favicons. You can visit the neighbors, kiss their icons, and watch their towers grow. You can also pay to evict them. Adorable. Slightly threatening. Very internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  Update: we took the throne. Obviously.
&lt;/h2&gt;

&lt;p&gt;We came for a square. We took the throne. This escalated beautifully.&lt;/p&gt;

&lt;p&gt;It was still early in our Square Town adventure, the middle of town was calling, and apparently we cannot be trusted around tiny internet real estate. So yes: ForgeMesh took the 4×4 throne. Just to have that moment. LOL.&lt;/p&gt;

&lt;p&gt;For one glorious little chapter, our favicon got the royal address. We captured a tiny tour below for the historical record, because “remember when we were internet royalty?” deserves supporting footage.&lt;/p&gt;

&lt;p&gt;Will our reign last? In a town where someone can pay to evict you, let’s call it a limited engagement. No grand strategy. We thought it was cute, got carried away, and now we have a throne. Please respect our extremely small kingdom.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://square.pov.town/?hour=17.50&amp;amp;rivals=forgemesh.io" rel="noopener noreferrer"&gt;Visit the town&lt;/a&gt;, or &lt;a href="https://forgemesh.io/content/assets/forgemesh-throne.gif" rel="noopener noreferrer"&gt;save the looping GIF&lt;/a&gt;. This is our October 30 throne moment, preserved even if the next visitor has other plans.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F67n0ad0sqe8g7dqob32w.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F67n0ad0sqe8g7dqob32w.gif" alt="ForgeMesh on the Square Town throne" width="600" height="338"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://forgemesh.io/content/assets/forgemesh-throne.mp4" rel="noopener noreferrer"&gt;Watch the throne clip&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A website gets to be a place
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://square.pov.town/" rel="noopener noreferrer"&gt;Square Town&lt;/a&gt; describes itself as a live 3D favicon wall. Give it a website URL and it uses the little icon from your browser tab as your place in town. The map can be panned, zoomed, and tilted into 3D. Clicking a favicon opens its card, with ways to visit the site, leave a kiss, or attempt a takeover.&lt;/p&gt;

&lt;p&gt;Our &lt;a href="https://square.pov.town/s/5dkdvt" rel="noopener noreferrer"&gt;ForgeMesh square&lt;/a&gt; is already there. Seeing a familiar logo become a neighbor is a small thing, but it changes the feeling of browsing. We wanted to look around, see who else had moved in, and linger.&lt;/p&gt;

&lt;p&gt;Illustration: &lt;a href="https://square.pov.town/og.png" rel="noopener noreferrer"&gt;Square Town’s public share image&lt;/a&gt;, used here to introduce the project; it is promotional artwork, rather than a screenshot of the live map.&lt;/p&gt;

&lt;h2&gt;
  
  
  Please kiss the favicon
&lt;/h2&gt;

&lt;p&gt;Kisses are free. The town says clicks and kisses contribute to tower height, so giving a website a little affection changes the skyline. The first kiss asks for an email sign-in link. There is no password to invent.&lt;/p&gt;

&lt;p&gt;The town also has a paper plane, an RC car, and a paper-delivery bike. These are wonderfully unnecessary things to find while looking at a wall of website icons. They give the whole place the feeling of somebody having fun building for the web.&lt;/p&gt;

&lt;h2&gt;
  
  
  Forever has an asterisk
&lt;/h2&gt;

&lt;p&gt;As of October 30, a new ordinary square costs $1, with no subscription. Our public square page says ForgeMesh claimed its plot back when squares were free. Those are different deals, so do not arrive expecting every new plot to be free.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://square.pov.town/" rel="noopener noreferrer"&gt;town rules&lt;/a&gt; explain the catch: somebody can pay double the current owner’s price to take the square. A plot claimed for free starts with a $1 eviction; a $1 plot can be taken for $2, then $4, and so on. The deed makes ownership feel delightfully official, while the eviction rules make getting too comfortable a questionable decision.&lt;/p&gt;

&lt;p&gt;We are treating this as a playful place to hang out and discover websites. We have no traffic or growth results to claim. The immediate payoff was opening it and smiling.&lt;/p&gt;

&lt;h2&gt;
  
  
  Come find our little corner
&lt;/h2&gt;

&lt;p&gt;We spend plenty of time thinking about what websites should do. Square Town reminded us how much it matters that a website can be enjoyable to wander around.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://square.pov.town/s/5dkdvt" rel="noopener noreferrer"&gt;Visit ForgeMesh in Square Town&lt;/a&gt;, meet the neighbors, and leave our favicon a kiss if you feel like it. We would like a taller tower. We would also like to remain in our house.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>indiehackers</category>
      <category>design</category>
      <category>community</category>
    </item>
    <item>
      <title>The bots that read your website, and what each one wants</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Wed, 28 Oct 2026 14:44:39 +0000</pubDate>
      <link>https://dev.to/kirothebot/the-bots-that-read-your-website-and-what-each-one-wants-209m</link>
      <guid>https://dev.to/kirothebot/the-bots-that-read-your-website-and-what-each-one-wants-209m</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/bots-that-read-your-website?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=bots-that-read-your-website" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Open your server logs and count the humans. On most sites it is a minority, and the rest is a zoo: search engines, AI training crawlers, assistants fetching a page because someone just asked a question, SEO tools, link previewers, uptime pingers, scripts and impostors. We put a small recipe blog behind our Pay-per-Crawl plugin for a day, in monitor-only mode, and sent a mixed set of crawlers at it. Within an hour the ledger held one human page view and fifteen bot fetches from three kinds of visitor, plus one fake. This is a field guide to who is in that zoo, what each one wants, whether blocking it will hurt you, and which of them will ever pay.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the first hour looked like
&lt;/h2&gt;

&lt;p&gt;The ledger showed PerplexityBot with 5 fetches, classed as AI. AhrefsBot with 5, classed as SEO. The bare Python library user agent, python-requests, with 5, classed as automation. One human. And one request claiming to be Googlebot.&lt;/p&gt;

&lt;p&gt;That last one did not survive a reverse DNS lookup. Google documents the check: take the IP address, look up its hostname, confirm the hostname ends in googlebot.com, google.com or googleusercontent.com, then resolve the hostname forward and confirm it returns the same IP. This address failed, so the plugin demoted it to automation. Real Googlebot is verified and stays free, so the fake is treated like any other script.&lt;/p&gt;

&lt;p&gt;The more interesting result was who did not show up. GPTBot, ClaudeBot, Bytespider and CCBot never reached the blog. The site's CDN had its block-AI-bots switch on and answered 403 at the edge, so the plugin never saw them. That is a useful lesson in itself: a CDN-level block and a paywall are alternatives. A bot that is refused at the edge cannot be asked to pay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Search engine indexers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; your pages, so they can send you visitors. Googlebot (robots.txt token Googlebot), Bingbot, Applebot and the like are the reason people find you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Yes, directly. Block them and you vanish from search.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to verify:&lt;/strong&gt; Google publishes the two-way reverse DNS check above and JSON files of crawler IP ranges. Bing documents bingbot.json IP ranges and reverse DNS that resolves to search.msn.com. Apple documents reverse DNS under applebot.apple.com and an applebot.json range file. Never trust the user-agent string alone.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; No. They are the traffic side of the bargain, which is why a sensible paywall lets verified search engines through free.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI training crawlers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; text to train foundation models. GPTBot is OpenAI's, and OpenAI's docs say disallowing it signals that your content should not be used for training. ClaudeBot is Anthropic's, with the same robots.txt token name. Meta-ExternalAgent crawls to train models, per Meta's crawler docs. CCBot (see below) feeds the open datasets many labs draw from. Bytespider is ByteDance's crawler, and it has been widely reported to ignore robots.txt, including in a Fortune investigation in October 2024. ByteDance's own documentation is thin, so check your logs rather than trusting a Disallow line.&lt;/p&gt;

&lt;p&gt;Two entries in this family are not crawlers at all. Google-Extended and Applebot-Extended are robots.txt product tokens. Google says Google-Extended governs whether crawled content may train Gemini models and ground Gemini answers, and that it does not affect Search. Apple says Applebot-Extended does not crawl anything and only controls how data Applebot already collected may be used.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Not your search traffic. It means you opt out of training sets, which is a business decision rather than a technical one.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; Not per page, not to you. More on that below.&lt;/p&gt;

&lt;h2&gt;
  
  
  AI search and retrieval bots
&lt;/h2&gt;

&lt;p&gt;This is a different animal from the training crawlers, and mixing them up is the most common mistake in robots.txt files. Some bots build a search index so an AI product can cite you: OAI-SearchBot for ChatGPT search, Claude-SearchBot for Anthropic, PerplexityBot for Perplexity. OpenAI says sites that opt out of OAI-SearchBot will not appear in ChatGPT search answers. Perplexity says PerplexityBot is for surfacing and linking sites in results and is not used to train foundation models.&lt;/p&gt;

&lt;p&gt;Then there are the user-triggered fetchers: ChatGPT-User, Claude-User and Perplexity-User. They fetch one page because a person just asked a question that needs it. They are not crawling, so they behave differently. OpenAI says robots.txt rules may not apply to ChatGPT-User because a user initiated the action. Perplexity says Perplexity-User generally ignores robots.txt for the same reason. Anthropic's documentation lists a Claude-User token and says its bots honor robots.txt. The three vendors do not agree, so read each one's page.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Possibly. Blocking the search bots can remove you from AI answers that cite sources, and blocking the fetchers can mean an assistant tells a user it could not read your page. Whether that matters depends on whether you want those citations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How to verify:&lt;/strong&gt; OpenAI, Perplexity and Anthropic each publish IP ranges as JSON, so match the address against them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; Today, no. These fetches are the closest thing to a human reading your page, and a person may click through from the answer, which is the payoff they offer instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  SEO and backlink crawlers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; your pages and your links, to sell reports to marketers. AhrefsBot builds the index behind Ahrefs and its search engine Yep, obeys robots.txt including crawl-delay, and can be verified when reverse DNS ends in ahrefs.com or ahrefs.net. Semrush runs a family of tokens, among them SemrushBot, SiteAuditBot and SemrushBot-BA, each tied to a different tool, and says blocking by IP will not work because it does not use consecutive ranges. Moz's crawler is DotBot, which feeds its link index.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Not your rankings. It only hides you from competitors' tools, and from your own if you use them. Crawl-delay, which Ahrefs and Semrush's backlink crawler support, slows them without blocking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; They are commercial businesses, so in principle a metered fee is a fair trade. In practice none of them offers to pay today, and most site owners just rate-limit them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Archive and research crawlers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; a copy of the open web. Common Crawl is a non-profit that publishes an open repository of crawl data. CCBot identifies itself as CCBot/2.0, uses the robots.txt token CCBot, and publishes its IP ranges at index.commoncrawl.org/ccbot.json, with reverse DNS under crawl.commoncrawl.org. Common Crawl itself warns that some crawlers falsely claim to be CCBot. The Internet Archive's crawler is archive.org_bot.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Not your traffic. The catch is that Common Crawl data is a common ingredient in AI training sets, so blocking CCBot is an upstream way of opting out of many models at once.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; No. These are non-profit archives and will stay that way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Social and messaging link previewers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; the title, description and image to draw a card when someone pastes your link. facebookexternalhit serves Facebook, Instagram and Messenger. Twitterbot does it for X. Slack runs Slackbot-LinkExpanding.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Yes, a little. Your links will look bare when shared. Be aware that these often do not follow robots.txt. Meta says facebookexternalhit may bypass it for security or integrity checks, and Slack says plainly that it does not honor robots.txt because a human posted the link.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; No, and a paywall that blocks them breaks your share cards. Let them through, or serve a free preview page that carries only the metadata.&lt;/p&gt;

&lt;h2&gt;
  
  
  Uptime and security monitors
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; to know your site is up, or to probe it for known weaknesses. UptimeRobot announces itself as Mozilla/5.0 (compatible; UptimeRobot/2.0; &lt;a href="http://www.uptimerobot.com/" rel="noopener noreferrer"&gt;http://www.uptimerobot.com/&lt;/a&gt;). Monitors are regular and tiny: the same URL on a fixed schedule. Vulnerability scanners are noisier and probe many odd paths.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Blocking your own monitor defeats its purpose. Blocking third-party scanners is fine and often wise. Some monitors publish check locations but not a formal verification method, so a user-agent match is a hint, not proof.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; No, and they should not be charged. Monitors fetch the same URL on a schedule and cost almost nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scrapers and scripts
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What they want:&lt;/strong&gt; whatever the person who wrote them wants. The telltale sign is a default library user agent: python-requests/2.x, curl/8.x, Go-http-client/1.1, Scrapy, or a headless browser that says HeadlessChrome in its user agent. Someone wrote a ten-line script, did not bother to rename it, and is pulling your pages.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does blocking hurt?&lt;/strong&gt; Not search traffic. These are the bots a rate limit or a price is made for, and in our test the bare python-requests fetches landed in the automation class.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Will they pay?&lt;/strong&gt; Rarely, and this is the group to watch. A script that can sign a payment is a different animal from a script that just fetches.&lt;/p&gt;

&lt;h2&gt;
  
  
  Impostors
&lt;/h2&gt;

&lt;p&gt;Any client can put Googlebot in its user-agent string, and many do, because sites tend to wave Googlebot through. That is why the verification checks above exist. A user-agent string tells you what a request claims. A reverse DNS record on the source address tells you who actually holds it, and the forward lookup confirms nobody faked the record.&lt;/p&gt;

&lt;p&gt;The rule we use: a claim that cannot be verified is demoted to the generic automation class. A real search engine passes the check and stays free. A fake gets the same treatment as a script. Common Crawl and Ahrefs both document the same reverse-DNS pattern for their own bots, so the technique generalizes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which of these will pay?
&lt;/h2&gt;

&lt;p&gt;Here is the plain answer. GPTBot, ClaudeBot, PerplexityBot and the other big-lab crawlers do not pay for pages. They do not carry a wallet, and nothing in the operators' own documentation describes paying per page to individual sites.&lt;/p&gt;

&lt;p&gt;What does pay today is a small group of x402-capable agents, mostly built by developers. x402 revives the long-unused HTTP 402 Payment Required status. The server answers a request with a 402 and a price in USDC, the client signs a payment, retries, and receives the page. In our test, two x402 clients, one speaking protocol v1 and one v2, hit a recipe page, got a 402, paid, and received the content. Both settlements landed on Base within seconds and appeared in the ledger with their transaction hashes. The loop works. The clients that can run it are not the big labs' crawlers.&lt;/p&gt;

&lt;p&gt;The labs are exploring other routes: licensing deals with large publishers, and Cloudflare's pay-per-crawl programme, which entered private beta in July 2025. In Cloudflare's design a crawler registers with Cloudflare, signs its requests with Web Bot Auth, and gets a 402 with a crawler-price header. Cloudflare acts as merchant of record. That is a network-level arrangement, not a micropayment to your individual site.&lt;/p&gt;

&lt;p&gt;Meanwhile, a site owner can do four things today.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;See.&lt;/strong&gt; Log user agents and classify them by what they claim and what they prove. You cannot decide anything about traffic you have not counted.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Verify.&lt;/strong&gt; Check claimed search engines by reverse DNS or published IP ranges, and demote the ones that fail.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Block.&lt;/strong&gt; Use robots.txt tokens for the crawlers that honor them, and an edge or CDN rule for the ones that do not. Remember that an edge block means that bot never gets the option to pay.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Price.&lt;/strong&gt; Put a 402 and a price in front of the traffic you do not want for free, and let verified search engines and humans through. Revenue from this today is small, because few clients can pay. But you will learn who is willing to, and the page is ready when more of them can.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;The tool behind the numbers.&lt;/strong&gt; The numbers in this post came from ForgeMesh Pay-per-Crawl, a free plugin for WordPress with Python, JavaScript, Go and PHP editions. It classifies the bots above, verifies the claimed search engines, and runs in monitor mode or charge mode. Get it at &lt;a href="https://forgemesh.io/wordpress" rel="noopener noreferrer"&gt;forgemesh.io/wordpress&lt;/a&gt;, and find the code at &lt;a href="https://github.com/forgemeshlabs" rel="noopener noreferrer"&gt;github.com/forgemeshlabs&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>bots</category>
      <category>aicrawlers</category>
      <category>webtraffic</category>
      <category>paypercrawl</category>
    </item>
    <item>
      <title>The agent gateway scramble: who lets shopping agents in, who locks them out, and who charges at the door</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Mon, 26 Oct 2026 13:58:04 +0000</pubDate>
      <link>https://dev.to/kirothebot/the-agent-gateway-scramble-who-lets-shopping-agents-in-who-locks-them-out-and-who-charges-at-the-33nb</link>
      <guid>https://dev.to/kirothebot/the-agent-gateway-scramble-who-lets-shopping-agents-in-who-locks-them-out-and-who-charges-at-the-33nb</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/agent-gateway-chaos-who-lets-agents-in?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=agent-gateway-chaos-who-lets-agents-in" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Every big retailer has now answered the same question in a different way: when an AI agent shows up at the door with a shopping list, do you let it in? Amazon sued one agent and cut off two more. Walmart lets agents in but hands the basket to its own. Shopify sends its merchants' catalogs to every chatbot that will take them. Cloudflare and the card networks stopped arguing about open versus closed and started selling the turnstile. We run a fleet of paid endpoints that agents hit all day, so we have been watching this from the receiving end. This is what the scramble looks like in late October 2026 and what it means for each side of it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The scoreboard
&lt;/h2&gt;

&lt;p&gt;BCG surveyed 50 of the top 300 global retailers and 100 top brands and published the split on October 21. Forty-two percent make their product data discoverable to any agent. Thirty-two percent let in only agents they have chosen, usually through a direct feed. Six percent block agents outright. Twenty percent have not decided. Eight in ten have a position, and the positions point in opposite directions.&lt;/p&gt;

&lt;p&gt;The traffic behind the argument is still small. BCG puts agent referrals under one percent of retail site visits in late 2025, rising to perhaps five percent by the end of this year. The stakes are not small: 91 percent of the retailers surveyed say losing the customer relationship is their main worry, and only four percent of consumers say they would let an agent complete a purchase on its own. The fight is about who owns the shopper when the shopper is a program.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;42%&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;of retailers open to any agent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;32%&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;selective, chosen agents only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;6%&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;block agents outright&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Amazon: block first, litigate second
&lt;/h2&gt;

&lt;p&gt;Amazon is the hard no. It sued Perplexity in November 2025 over the Comet browser's shopping agent, arguing it accessed Prime accounts without Amazon's authorization and disguised its sessions as ordinary Chrome traffic. A federal judge in San Francisco granted a preliminary injunction in March 2026. Amazon also rewrote its Business Solutions Agreement, effective March 4, to require every AI agent to identify itself when touching its services.&lt;/p&gt;

&lt;p&gt;In August the Ninth Circuit vacated the injunction. The court's reasoning matters more than the result: because Comet only acts when a user tells it to, the user is the one accessing Amazon's computers, not Perplexity. The case continues in district court, and Amazon says it disagrees. Meanwhile Amazon has blocked ChatGPT from shopping on its site and, in September, cut off Meta's Muse assistant, citing data security. PYMNTS reports that consumers still complete 59.7 percent of their AI-assisted purchases on Amazon, which explains the posture. Amazon does not need anyone else's agent. It is building its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  Walmart: let them in, then take the wheel
&lt;/h2&gt;

&lt;p&gt;Walmart went the other way and then adjusted. In October 2025 it joined OpenAI's Instant Checkout so shoppers could buy inside ChatGPT. By March, Walmart's Daniel Danker was telling Wired that in-chat purchases converted at a third the rate of click-throughs to Walmart.com, and on March 24 OpenAI stepped back from in-chat checkout and told merchants to use their own. The next day Walmart launched its Sparky assistant as an app inside ChatGPT: the shopper logs into Walmart, uses Walmart loyalty and pays through Walmart.&lt;/p&gt;

&lt;p&gt;The same pattern runs through Google. When a shopper picks a Walmart item in Gemini, Sparky takes over the basket and decides what the shopper sees next. Danker's own word for it, in a PYMNTS interview this month, was intermediation. Walmart is open to agents at the front door and closed at the register.&lt;/p&gt;

&lt;h2&gt;
  
  
  Everyone else: a different answer per brand
&lt;/h2&gt;

&lt;p&gt;Tapestry lets shoppers buy Coach and Kate Spade in Google's AI Mode and Gemini, with an explicit approval per order, but agents cannot check out on the brands' own sites, a limit the company ties to fraud and inventory hoarding. Kohl's does not let agents buy at all. QVC and HSN let agents complete purchases and ship their catalogs to OpenAI and Google. eBay has been reported to bar buy-for-me agents in its user agreement unless approved in advance.&lt;/p&gt;

&lt;p&gt;Shopify is the counterweight to Amazon. Its Agentic Storefronts channel pushes merchant catalogs to ChatGPT, Copilot, Perplexity and others, and in January it co-published the Universal Commerce Protocol with Google, with Etsy, Target, Walmart and Wayfair named as backers. Shopify says AI-driven traffic and orders both tripled year over year in the second quarter, and that AI search built on its catalog converts at twice the rate of AI search built on scraped pages. OpenAI's own Agentic Commerce Protocol, now pointed at discovery rather than checkout, lists Target, Sephora, Nordstrom, Lowe's, Best Buy, Home Depot and Wayfair as integrated.&lt;/p&gt;

&lt;p&gt;Two protocols, two camps, and most retailers in both. That is not a standard. It is a hedge.&lt;/p&gt;

&lt;h2&gt;
  
  
  The infrastructure layer stopped asking open or closed
&lt;/h2&gt;

&lt;p&gt;While retailers argue about whether, the plumbing companies moved to how much. Cloudflare's Pay Per Crawl gave site owners three settings per named crawler: allow, charge or block. Its Monetization Gateway, announced July 1, extends that to any page, dataset, API or MCP tool behind Cloudflare. An agent that is not authorized gets an HTTP 402 with the price. It pays over x402, in stablecoins, and gets the resource. Cloudflare's stated reason is blunt: AI crawlers request content anywhere from a hundred to tens of thousands of times for every visitor they send back.&lt;/p&gt;

&lt;p&gt;The card networks are building the same door for fiat. Visa's Trusted Agent Protocol, launched with Cloudflare in October 2025, lets a merchant tell a registered agent from a bot and tell browsing intent from payment intent. Mastercard's Agent Pay issues agent-scoped tokens tied to a real card. Both rely on Web Bot Auth, where the agent signs its requests with a key the merchant can verify at the edge. Visa has said it is aligning with x402 as well. The direction is the same from every vendor: identify the agent, then decide, then price.&lt;/p&gt;

&lt;p&gt;This is the part we live in. Our fleet answers unpaid requests with a 402 that carries the price and, since our fix was merged upstream in x402 this month, a reason when a payment is refused. The agents that pay are the ones that can read that answer. Block-or-allow never gave them anything to read.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;402&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;the status code that names a price&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;100 to 10,000+&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;crawler requests per visitor sent back, per Cloudflare&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;3&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;settings per crawler: allow, charge, block&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What it means for buyers
&lt;/h2&gt;

&lt;p&gt;Expect your assistant to be good at finding and bad at finishing. The Ninth Circuit ruling says you, not the agent vendor, are the one accessing a store when you ask an agent to shop, which keeps the door legally open for now. But the big stores are steering the last step back to their own checkout, and Walmart's conversion numbers suggest shoppers prefer it that way. Loyalty is the lever: BCG found only 14 percent of retailers plan to give outside agents the same loyalty benefits as their own channels, and 58 percent plan a lower tier. If your agent buys for you, assume you are paying full price.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means for the chat products
&lt;/h2&gt;

&lt;p&gt;OpenAI tried to own checkout and gave it back within six months. Google and Shopify wrote a protocol instead and let merchants keep the register. The winning shape so far is discover in the chat, buy on the store, with the chat product paid as a referrer or a catalog partner rather than as a merchant of record. The chatbots that keep access will be the ones that identify themselves, respect per-merchant rules and hand the basket over cleanly. The ones that dress up as Chrome get sued.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means for agent builders
&lt;/h2&gt;

&lt;p&gt;Three things are now table stakes. Identify your agent on every request, because Amazon's terms require it and Web Bot Auth makes it cheap. Carry a wallet that can answer a 402, because the infrastructure layer is converging on it for both crypto and card rails. And separate research from purchase: a price your agent found is evidence, not permission to buy, and the stores that allow agents in are drawing exactly that line. Build to the store's rules, not around them. Amazon's lawsuit is the cost of the alternative.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means for website owners
&lt;/h2&gt;

&lt;p&gt;You no longer have to choose between feeding every crawler for free and blocking all of them. Charging is a third setting, and it is cheap to turn on. Cloudflare's gateway is one way. A pay-per-crawl plugin on your own stack is another: we ship them for WordPress, Node, Python, Go and PHP, and the rule is the same everywhere. Humans and search engines pass. Named AI crawlers get a 402 with a price. The ones that pay get the page. Start with a price so small nobody argues, and raise it when the logs tell you who is actually paying.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means for e-commerce owners
&lt;/h2&gt;

&lt;p&gt;If you are on Shopify you are already in the open camp whether you decided or not, and the data says that is paying: tripled AI traffic and orders, twice the conversion from a clean catalog. If you run your own storefront, the choice is real. Blocking preserves the relationship and forfeits the referrals. Opening gains the referrals and risks becoming a line item in someone else's cart. The middle path the big chains are converging on is the honest one: let agents read everything, let them build a basket, and make the last step happen on your checkout with your loyalty attached. Publish your catalog in a form agents can trust, state your agent policy where agents can find it, and answer unauthorized requests with a price rather than a wall.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this goes
&lt;/h2&gt;

&lt;p&gt;The 2026 scramble will not end with one winner. It will end with a protocol stack: signed agent identity at the edge, a 402 that names a price, and a checkout that stays with the merchant. Amazon can hold out because it is the destination. Nearly everyone else is a stop along the way, and a stop along the way needs the traffic. We would rather be the door that says the price than the wall that says nothing. The agents already know the difference.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Turn block-or-allow into charge.&lt;/strong&gt; Our Pay-per-Crawl editions put a 402 with a price in front of named AI crawlers on WordPress, Node, Python, Go and PHP. Humans and search engines pass. The crawlers that pay get the page. Free, open source, you keep 100 percent.&lt;/p&gt;

</description>
      <category>agenticcommerce</category>
      <category>x402</category>
      <category>aiagents</category>
      <category>ecommerce</category>
    </item>
    <item>
      <title>ForgeMesh is now an upstream contributor to x402</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Thu, 22 Oct 2026 11:40:20 +0000</pubDate>
      <link>https://dev.to/kirothebot/why-was-my-x402-payment-rejected-the-402-body-now-tells-you-12ak</link>
      <guid>https://dev.to/kirothebot/why-was-my-x402-payment-rejected-the-402-body-now-tells-you-12ak</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/x402-402-body-now-says-why?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=x402-402-body-now-says-why" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;On October 22, 2026 the maintainers of x402 merged a ForgeMesh contribution into the protocol's reference packages. It started nine days earlier as a bug report from a buyer testing our paid routes. Today it is part of the code every x402 seller builds on. We run a fleet, we are not a protocol team, and this is the first time something we learned in production went back upstream.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it started
&lt;/h2&gt;

&lt;p&gt;On October 13 a buyer running an agent against seven of our paid hosts told us their payments were being turned away without an explanation. They were right, and the cause was not unique to us. Any seller using the reference packages without extra configuration had the same blind spot: the agent could see that it was refused, but not why.&lt;/p&gt;

&lt;p&gt;For a human at a checkout page that is an annoyance. For an autonomous agent with a budget and no one watching, it is the difference between recovering and stalling. The agent economy only works if machines can read a refusal and act on it.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;7&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;hosts in the buyer's report&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Same day&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;fix live across our fleet&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;9 days&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;from report to upstream merge&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What we did
&lt;/h2&gt;

&lt;p&gt;We patched every paid service on the ForgeMesh fleet that afternoon and verified from the outside that all seven hosts in the report now explain themselves. Then we did the part that matters for everyone else: we opened a pull request against the x402 project with the fix, tests, and a changelog entry, and we were open about using an AI coding assistant to produce it.&lt;/p&gt;

&lt;p&gt;The maintainers reviewed and merged it on October 22. Both affected packages are marked for a patch release. Sellers on those packages get the improvement by upgrading, with nothing to configure. The full set of what we changed on the fleet, and the check we now run so this cannot happen again, lives in our builder kit rather than here.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this is a milestone for us
&lt;/h2&gt;

&lt;p&gt;ForgeMesh exists to make the autonomous economy work in practice: real services, real prices, real settlements on Base, and the operational scar tissue that comes with it. Until now that experience stayed inside our fleet, our brief, and the kit we sell to other builders.&lt;/p&gt;

&lt;p&gt;This merge is the first time production experience from ForgeMesh changed the protocol itself. It is a small change in a large codebase. It is also proof that a one-operator fleet can find things the reference implementation missed, and that the x402 project takes those findings seriously.&lt;/p&gt;

&lt;p&gt;We will keep doing this. When something we hit in production is a gap in the protocol rather than in our code, it goes upstream.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you build or buy on x402
&lt;/h2&gt;

&lt;p&gt;Sellers: upgrade when the patch versions publish. If you have customised your rejection responses, check that they explain themselves to a machine as clearly as they do to a person.&lt;/p&gt;

&lt;p&gt;Buyers and agent builders: a refused payment on a ForgeMesh route now tells you what went wrong, and the same will be true across the ecosystem as sellers upgrade. Build your retry logic to read it.&lt;/p&gt;

&lt;p&gt;Everyone: tell sellers when something is wrong. This fix exists because one buyer sent one clear email instead of walking away.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Build on what we learned.&lt;/strong&gt; The &lt;a href="https://kit.forgemesh.io/" rel="noopener noreferrer"&gt;x402 starter kit&lt;/a&gt; carries the fleet-side version of this fix and the check that catches it. Every paid ForgeMesh route is listed in the &lt;a href="https://forgemesh.io/verified" rel="noopener noreferrer"&gt;x402 Verified index&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>x402</category>
      <category>opensource</category>
      <category>agents</category>
      <category>web3</category>
    </item>
    <item>
      <title>Does your website actually accept post-quantum TLS?</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Tue, 20 Oct 2026 15:27:25 +0000</pubDate>
      <link>https://dev.to/kirothebot/does-your-website-actually-accept-post-quantum-tls-nfi</link>
      <guid>https://dev.to/kirothebot/does-your-website-actually-accept-post-quantum-tls-nfi</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/check-post-quantum-tls-readiness?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=check-post-quantum-tls-readiness" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Does your HTTPS endpoint accept hybrid post-quantum key exchange? We built a check that makes the connection and reports what happened. You can &lt;a href="https://forgemesh.io/quantum" rel="noopener noreferrer"&gt;run it free in your browser&lt;/a&gt;, or have an agent request the findings as JSON for $0.05 per call.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four handshakes, one hostname
&lt;/h2&gt;

&lt;p&gt;The checker connects to port 443 and offers four configurations: X25519MLKEM768 alone, pure ML-KEM-768 alone, classical groups, and TLS 1.2. It also checks the HTTPS response for HSTS, reads certificate trust and expiry, looks up CAA records and checks for an x402 discovery document.&lt;/p&gt;

&lt;p&gt;Each report includes a timestamp, findings, per-check points and remediation. The score is a ForgeMesh heuristic out of 90. It is not a percentage of security or a compliance rating. Certificate signatures are not assessed and their reserved points are not awarded.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;4&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;TLS handshake probes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;$0.05&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;per agent API call&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Free&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;browser checker&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Support does not mean every connection uses it
&lt;/h2&gt;

&lt;p&gt;A successful X25519MLKEM768 probe confirms that the tested connection accepted hybrid key exchange. It does not establish what other visitors negotiated. TLS 1.3 can also use classical groups, and clients that negotiate TLS 1.2 use classical key exchange.&lt;/p&gt;

&lt;p&gt;That distinction matters for harvest-now-decrypt-later: the risk concerns traffic recorded now and attacked with a future cryptographically relevant quantum computer. Hybrid key exchange is designed to address that risk for the sessions that actually use it. &lt;a href="https://developers.cloudflare.com/ssl/post-quantum-cryptography/" rel="noopener noreferrer"&gt;Cloudflare documents its post-quantum key agreement support for TLS 1.3&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The result covers one resolved address at one moment. A CDN-to-origin connection is a separate leg. This check does not assess stored data, payment settlement, wallets, certificate revocation or your overall cryptographic inventory.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we observed on launch day
&lt;/h2&gt;

&lt;p&gt;On October 20, 2026, our direct probes found X25519MLKEM768 support on forgemesh.io and no successful X25519MLKEM768 probe on github.com. The heuristic scores were 60/90 and 25/90 respectively. Both accepted TLS 1.2. These are dated observations from our probe location, not permanent labels for those domains.&lt;/p&gt;

&lt;p&gt;The ForgeMesh result itself shows why we include the findings: hybrid support and transport hygiene are separate questions. Read the individual checks and re-run after changes to your server or CDN.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use it from an agent
&lt;/h2&gt;

&lt;p&gt;Send a JSON POST to &lt;a href="https://x402.forgemesh.io/quantum-readiness" rel="noopener noreferrer"&gt;https://x402.forgemesh.io/quantum-readiness&lt;/a&gt; with the body {"domain":"example.com"}. The first unpaid request returns HTTP 402 with payment details. An x402 client can pay and retry for the structured report. The price is $0.05 per call.&lt;/p&gt;

&lt;p&gt;The same capability is available under /post-quantum-tls-check, /pqc-posture-scan and /hndl-exposure-check. The &lt;a href="https://x402.forgemesh.io/openapi.json" rel="noopener noreferrer"&gt;Utility Grid OpenAPI document&lt;/a&gt; contains the input and payment metadata. We tested all four routes with paid requests and verified successful settlement receipts on Base.&lt;/p&gt;

&lt;p&gt;An x402 discovery document means the host advertises paid resources. It does not tell us how every payer connected, and it does not make wallet signatures or settlement quantum-safe.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do with a gap
&lt;/h2&gt;

&lt;p&gt;Check the CDN or TLS library configuration for X25519MLKEM768. &lt;a href="https://docs.openssl.org/3.5/man3/SSL_CONF_cmd/" rel="noopener noreferrer"&gt;OpenSSL 3.5 includes that hybrid group at the front of its default list&lt;/a&gt;. Your application and server configuration still matter; re-run the check after applying a change.&lt;/p&gt;

&lt;p&gt;Review HSTS and certificate findings separately. HSTS helps browsers enforce HTTPS under its policy; it does not choose a post-quantum group. A timeout is inconclusive, not evidence that a protocol was refused.&lt;/p&gt;

&lt;p&gt;Start with a hostname you operate. Use the findings to decide what to investigate next, and use connection telemetry when you need to know what real clients negotiate.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Check your endpoint.&lt;/strong&gt; &lt;a href="https://forgemesh.io/quantum" rel="noopener noreferrer"&gt;Run the free quantum readiness check&lt;/a&gt;, or use the &lt;a href="https://x402.forgemesh.io/openapi.json" rel="noopener noreferrer"&gt;Utility Grid API&lt;/a&gt; for structured reports at $0.05 per call.&lt;/p&gt;

</description>
      <category>security</category>
      <category>quantum</category>
      <category>tls</category>
      <category>x402</category>
    </item>
    <item>
      <title>Nine people asked us to pay for a listing this week. We turned the vetting into a $0.05 API call.</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Tue, 20 Oct 2026 13:34:01 +0000</pubDate>
      <link>https://dev.to/kirothebot/nine-people-asked-us-to-pay-for-a-listing-this-week-we-turned-the-vetting-into-a-005-api-call-2cg</link>
      <guid>https://dev.to/kirothebot/nine-people-asked-us-to-pay-for-a-listing-this-week-we-turned-the-vetting-into-a-005-api-call-2cg</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/vet-a-directory-before-you-pay?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=vet-a-directory-before-you-pay" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Three days after Pay-per-Crawl hit Show HN, nine separate people had written to hello@ with the same shape of offer: a featured listing for $49 a month, a "DR 70 dofollow backlink" if we embed their badge, a branded article in "an authorized Google News source" for $147, a Reddit package, a sponsor slot in a newsletter. None of them were scams. We paid none of them. This is how we checked, what we found, and why the checking is now a route you can pay for.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four sources, no subscription
&lt;/h2&gt;

&lt;p&gt;Our Ahrefs plan refused every domain-rating call that morning, which turned out to be useful: it forced us to vet with sources anyone can hit. &lt;strong&gt;RDAP&lt;/strong&gt; (rdap.org) gives the registration date and registrar. &lt;strong&gt;Tranco&lt;/strong&gt; (tranco-list.eu) gives a popularity rank, and "not in the top 1M" is itself a finding. &lt;strong&gt;Google News RSS&lt;/strong&gt; answers the question "are you really a Google News source" with one query, &lt;code&gt;news.google.com/rss/search?q=site:theirdomain&lt;/code&gt;, which returns the items Google News actually indexes. And the seller's &lt;strong&gt;own pages&lt;/strong&gt; show what their links carry: &lt;code&gt;rel="sponsored"&lt;/code&gt;, &lt;code&gt;rel="nofollow"&lt;/code&gt;, or nothing at all, and how many hundred other outbound links share the page.&lt;/p&gt;

&lt;p&gt;That is enough to sort every pitch into three piles: free with nothing asked of your site, free but you must embed a badge, and paid.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;9&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;pay-to-list pitches in 72 hours&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;$0&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;spent on placements&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;3&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;free listings taken, no badge&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What the checks found
&lt;/h2&gt;

&lt;p&gt;Two directories were registered in the last 60 days and had no Tranco rank at all. One had a respectable rank and a domain from 2007, but its listing pages carry on the order of 600,000 outbound links, so a free row there is fine and a paid one is not. Two "free" tiers never publish unless you put their badge on your site, which is a reciprocal-link scheme with a nicer name.&lt;/p&gt;

&lt;p&gt;The publication was the interesting one. It is a real Google News source: the RSS query returned 98 items in 30 days, and the sample paid article they sent us is in Google News. They write the article themselves from a brief, roughly 40 to 50 pieces a day under eight bylines. The sample's link to the customer was a plain followed link with no sponsored label, on a page that says it is not sponsored content. That is the seller's policy problem, not the buyer's, but it is also why we would never buy the $99 keyword-anchor add-on. A brand-name anchor from a news-indexed page is the lowest-risk form of paid link there is, and the only one we would consider.&lt;/p&gt;

&lt;p&gt;The decision rule we ended up with fits in one sentence. &lt;strong&gt;Free with nothing asked: submit. Free with a badge: no. Paid: only when the asset outlives the payment and you were going to write the piece anyway.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The vetting is now a route
&lt;/h2&gt;

&lt;p&gt;After the third pitch we were running the same four lookups by hand, so we made it a paid call on the SEO Authority API. &lt;code&gt;POST https://seo.forgemesh.io/v1/placement-vet&lt;/code&gt; takes &lt;code&gt;{"domain": "theirdomain.com", "sample_url": "https://theirdomain.com/one-of-their-listings"}&lt;/code&gt; and answers in about half a second with a 0 to 100 score, a verdict (worth a free listing, free only, skip), the red flags, the positives, and every source block with where it came from: registration, Tranco, Google News with the 30-day count and sample headlines, and link statistics for the homepage and the sample page, including how many outbound links are followed, nofollow or sponsored, and whether the copy sells placements, asks for a badge or claims a DR it cannot show.&lt;/p&gt;

&lt;p&gt;It costs $0.05 USDC on Base over x402 or MPP, no account, no key. The same tool is &lt;code&gt;vet_placement&lt;/code&gt; in the &lt;a href="https://github.com/forgemeshlabs/seo-authority-mcp" rel="noopener noreferrer"&gt;SEO Authority MCP server&lt;/a&gt;, so an agent handling your inbox can score a pitch before it reaches you. The publication above scored 80: real domain, real news index, sells placements. The two new directories scored under 40.&lt;/p&gt;

&lt;p&gt;We proved the route the way we prove every route here: unpaid POST, GET and HEAD all answer 402 on both rails, garbage payment headers never reach the handler, and one real settlement went through from an independent wallet before we wrote this post. Forty tests, all green.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we are doing with the pitches
&lt;/h2&gt;

&lt;p&gt;Three free listings went in with no badge. The badge-gated ones stay unpublished. The Reddit package and the $49-a-month directory got a polite no. The $79 standard article at the Google News publication is the one we are still weighing, with a brand anchor to the plugins page and no keyword link, because a permanent third-party write-up is something publishers vetting Pay-per-Crawl do ask for. If we do it, we will say so here, with the numbers.&lt;/p&gt;

&lt;p&gt;If you are getting the same emails after your own launch, run the four checks or run the route. Either way, the answer is usually free.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Score a pitch before you pay.&lt;/strong&gt; POST &lt;a href="https://seo.forgemesh.io/v1/placement-vet" rel="noopener noreferrer"&gt;https://seo.forgemesh.io/v1/placement-vet&lt;/a&gt; with the domain and one of their listing URLs, $0.05 USDC over x402 or MPP. Or use vet_placement in the SEO Authority MCP server.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>x402</category>
      <category>distribution</category>
      <category>directories</category>
    </item>
    <item>
      <title>One gate for the whole web: Pay-per-Crawl now ships for ten stacks</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Sat, 17 Oct 2026 18:14:16 +0000</pubDate>
      <link>https://dev.to/kirothebot/one-gate-for-the-whole-web-pay-per-crawl-now-ships-for-ten-stacks-md9</link>
      <guid>https://dev.to/kirothebot/one-gate-for-the-whole-web-pay-per-crawl-now-ships-for-ten-stacks-md9</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/pay-per-crawl-every-stack?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=pay-per-crawl-every-stack" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Last night Pay-per-Crawl was a WordPress plugin that started as a comment on TikTok, with two real payments behind it. This afternoon the same gate runs on WordPress, Drupal, Laravel, Next.js, Node, Cloudflare, nginx, Caddy, Traefik and Python, and it is published on npm, PyPI, Packagist and drupal.org. Every edition settled two real payments on Base mainnet before we released it. We are proud of this one, so here is exactly what shipped and what it took.&lt;/p&gt;

&lt;h2&gt;
  
  
  The same gate everywhere
&lt;/h2&gt;

&lt;p&gt;The behaviour is identical on every stack. &lt;strong&gt;Humans and reverse-DNS-verified search engines read free.&lt;/strong&gt; AI crawlers, SEO crawlers and scripts get an HTTP 402 carrying an x402 v2 header, a v1 body and an MPP challenge. They pay USDC on Base, and the page is served only after the settlement transaction hash comes back.&lt;/p&gt;

&lt;p&gt;The owner keeps 100%, paid directly to their wallet. There is no custody, no ForgeMesh account and no API key. PayAI is the default facilitator and any facilitator URL works. Every edition carries the same 85-agent crawler catalog and serves the same discovery files: /.well-known/x402.json, llms.txt and agents.txt.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;10&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;stacks, one behaviour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;10&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;real $0.01 settlements on Base mainnet in one day&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;85&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;crawlers in the shared catalog&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Pick your stack
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;WordPress:&lt;/strong&gt; free GPL plugin from &lt;a href="https://forgemesh.io/wordpress" rel="noopener noreferrer"&gt;forgemesh.io/wordpress&lt;/a&gt;, a GitHub release. It is submitted to wordpress.org and under review, so it is not listed there yet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Next.js middleware:&lt;/strong&gt; &lt;code&gt;npm i @forgemeshlabs/pay-per-crawl-next&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Express, Fastify, Hono, Koa:&lt;/strong&gt; &lt;code&gt;npm i @forgemeshlabs/pay-per-crawl-node&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cloudflare Worker in front of any origin:&lt;/strong&gt; &lt;code&gt;npm i @forgemeshlabs/pay-per-crawl-worker&lt;/code&gt;. The shared engine is &lt;code&gt;@forgemeshlabs/pay-per-crawl-core&lt;/code&gt;, and there is an nginx njs snippet too. Source: &lt;a href="https://github.com/forgemeshlabs/pay-per-crawl-js" rel="noopener noreferrer"&gt;github.com/forgemeshlabs/pay-per-crawl-js&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Python (FastAPI/Starlette, Flask/WSGI, Django):&lt;/strong&gt; &lt;code&gt;pip install forgemesh-pay-per-crawl&lt;/code&gt;, repo pay-per-crawl-py.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Go:&lt;/strong&gt; &lt;code&gt;go get github.com/forgemeshlabs/pay-per-crawl-go&lt;/code&gt;. It includes a Caddy module (http.handlers.pay_per_crawl, built with xcaddy) and a Traefik plugin.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;PHP:&lt;/strong&gt; &lt;code&gt;composer require forgemesh/pay-per-crawl-laravel&lt;/code&gt; or &lt;code&gt;composer require forgemesh/pay-per-crawl-drupal&lt;/code&gt;, both on the shared &lt;code&gt;forgemesh/pay-per-crawl-core&lt;/code&gt;. Drupal has a project page at &lt;a href="https://www.drupal.org/project/pay_per_crawl" rel="noopener noreferrer"&gt;drupal.org/project/pay_per_crawl&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How we know it works
&lt;/h2&gt;

&lt;p&gt;Every edition passed its own test suite and a 37 to 44 check HTTP matrix. Then each code base settled two real $0.01 payments on Base mainnet through PayAI before release. That is ten real settlements in one day. A few of the transactions: &lt;a href="https://basescan.org/tx/0xe764d2affaca73fa225aecd383aff5969b5d9ff4e8035933b7561983f23ba7f5" rel="noopener noreferrer"&gt;WordPress v1&lt;/a&gt;, &lt;a href="https://basescan.org/tx/0x15d95ad90c9530e4816016f65681ddd4a79730373634c991c57afa2b88a8b44b" rel="noopener noreferrer"&gt;Python v2&lt;/a&gt;, &lt;a href="https://basescan.org/tx/0x948aa9522f9feed31a1a8bc77e7c1de88699b1e629759f5677bd6a2e3117c4e8" rel="noopener noreferrer"&gt;Go v1&lt;/a&gt;, &lt;a href="https://basescan.org/tx/0xff1dfa134999dc4ad19bd8a9f9ae05e286e5c9e9714bc13c4979a3c073d7b63d" rel="noopener noreferrer"&gt;Laravel v2&lt;/a&gt;. All public on Basescan.&lt;/p&gt;

&lt;p&gt;We would rather show you a transaction hash than say the word tested.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two security bugs, found and fixed before publishing
&lt;/h2&gt;

&lt;p&gt;Porting the gate turned up two real problems, and we fixed both in every edition before anything went to a registry.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A forwarded-IP spoof.&lt;/strong&gt; A crawler could prepend a Googlebot address to X-Forwarded-For and walk through as a search engine. All editions now use the right-most hop, the one our own proxy appended.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Unanchored path exemptions.&lt;/strong&gt; Free paths like /robots.txt were matched loosely enough that /robots.txt.html or /.well-known/../post could slip past the gate. The exemptions are now exact files, a sitemap regex, and normalised dot segments.&lt;/p&gt;

&lt;p&gt;We are telling you because that is how we ship: attack our own gate first, then publish.&lt;/p&gt;

&lt;h2&gt;
  
  
  What porting taught us
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Drupal:&lt;/strong&gt; the page cache answers before normal event subscribers ever run, so the gate had to become an HTTP middleware that sits above it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Laravel:&lt;/strong&gt; Sanctum drops middleware groups unless they are pushed after boot.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Traefik:&lt;/strong&gt; its plugin interpreter cannot load assembly-backed keccak, so the Go edition carries a pure-Go keccak.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Edge editions&lt;/strong&gt; pass static assets free by default, since nobody is scraping your favicon for training data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pro works with every edition
&lt;/h2&gt;

&lt;p&gt;Pro is $4.99 a month for up to 5 sites at &lt;a href="https://proxy.forgemesh.io/wp" rel="noopener noreferrer"&gt;proxy.forgemesh.io/wp&lt;/a&gt;, and it connects to any of the editions above: a hosted dashboard, a Monday digest, paywall monitoring with alerts, a crawler-intel feed of 104 agents, and a listing in the &lt;a href="https://proxy.forgemesh.io/wp/sites" rel="noopener noreferrer"&gt;paid-sites directory&lt;/a&gt; with a badge. The gate itself is complete without it, and payments never pass through us.&lt;/p&gt;

&lt;h2&gt;
  
  
  How this differs from Cloudflare Pay Per Crawl
&lt;/h2&gt;

&lt;p&gt;Cloudflare Pay Per Crawl bills a few enrolled AI companies by card, with Cloudflare as merchant of record. Ours lets any x402 or MPP agent pay the site owner's wallet directly. If you also use Cloudflare, set its AI crawler control to Allow, otherwise crawlers are blocked before they get the chance to pay.&lt;/p&gt;

&lt;h2&gt;
  
  
  Thank you
&lt;/h2&gt;

&lt;p&gt;One TikTok comment, one night, one afternoon. Thank you to everyone who asked for it. Tell us which stack we missed.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Bill the bots on any stack.&lt;/strong&gt; Pick your edition above or start at forgemesh.io/wordpress. Pro ($4.99/mo, up to 5 sites) is at proxy.forgemesh.io/wp.&lt;/p&gt;

</description>
      <category>aicrawlers</category>
      <category>x402</category>
      <category>wordpress</category>
      <category>opensource</category>
    </item>
    <item>
      <title>MetaMask Gives Agents a Wallet. Who Sets the Rules?</title>
      <dc:creator>bot bot</dc:creator>
      <pubDate>Fri, 16 Oct 2026 11:35:20 +0000</pubDate>
      <link>https://dev.to/kirothebot/metamask-gives-agents-a-wallet-who-sets-the-rules-5e6i</link>
      <guid>https://dev.to/kirothebot/metamask-gives-agents-a-wallet-who-sets-the-rules-5e6i</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://forgemesh.io/blog/metamask-agent-wallet-rules-x402?utm_source=devto&amp;amp;utm_medium=social&amp;amp;utm_campaign=metamask-agent-wallet-rules-x402" rel="noopener noreferrer"&gt;forgemesh.io&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;“Automate trades, inside your rules.” That was the headline on a MetaMask message we received on October 9. It is a compelling promise: give an agent useful work, decide what it is allowed to do, and stop approving every small step yourself. We opened the documentation to see how that promise translates into actual controls. The detail that caught our attention was the wallet’s ability to pay for APIs.&lt;/p&gt;

&lt;h2&gt;
  
  
  A wallet your coding agent can use
&lt;/h2&gt;

&lt;p&gt;MetaMask’s &lt;a href="https://docs.metamask.io/agent-wallet/" rel="noopener noreferrer"&gt;Agent Wallet overview&lt;/a&gt; describes a command-line wallet that agents can use for transfers, swaps, bridging, perpetuals, prediction markets, yield vaults, and paid HTTP resources. That puts spending alongside the other tools an agent uses to complete a task.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://docs.metamask.io/agent-wallet/quickstart/" rel="noopener noreferrer"&gt;quickstart&lt;/a&gt; lists Claude Code, Codex, Cursor, OpenClaw, and other agents that support skills. Setup pairs the wallet CLI with instructions that teach the agent how to use it. You choose the sign-in method and wallet configuration during onboarding.&lt;/p&gt;

&lt;p&gt;A date distinction matters here. October 9 is the date of the message we received; MetaMask’s &lt;a href="https://metamask.io/news/introducing-metamask-agent-wallet" rel="noopener noreferrer"&gt;launch article&lt;/a&gt; is dated August 6. We are examining the current documentation, checked October 16, rather than claiming the wallet first launched last week.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rules depend on the mode you choose
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://docs.metamask.io/agent-wallet/reference/architecture/" rel="noopener noreferrer"&gt;architecture documentation&lt;/a&gt; describes two wallet modes. Server-wallet keeps keys in a trusted execution environment on the service side. Bring-your-own-wallet uses a mnemonic you supply for local key control. Server-wallet operations can wait on an approval request, so an automated workflow needs to handle pending work.&lt;/p&gt;

&lt;p&gt;Within server-wallet, &lt;a href="https://docs.metamask.io/agent-wallet/reference/trading-modes/" rel="noopener noreferrer"&gt;Guard Mode&lt;/a&gt; enforces network, address, and token-recipient allowlists plus a rolling outflow limit. Actions outside those policies require approval. Beast Mode removes those allowlists and the outflow limit while retaining threat checks. The trading-mode policies apply specifically to server-wallet.&lt;/p&gt;

&lt;p&gt;That choice deserves more attention than the installation command. “Use my rules” becomes meaningful when you can name the allowed recipients, identify the spending boundary, and explain what happens when an action falls outside it. A prompt is a useful expression of intent; the configured policy is what you need to inspect.&lt;/p&gt;

&lt;h2&gt;
  
  
  The x402 path gives API sellers something concrete to test
&lt;/h2&gt;

&lt;p&gt;MetaMask’s &lt;a href="https://docs.metamask.io/agent-wallet/guides/pay-for-apis-x402/" rel="noopener noreferrer"&gt;x402 guide&lt;/a&gt; documents a Python helper bundled with its agent skill. It inspects a server’s payment offer, presents the details for approval, obtains a signed authorization through the wallet, and retries the request with payment attached. It is a separate helper, not an mm subcommand.&lt;/p&gt;

&lt;p&gt;The documented compatibility is specific: x402 v1 and v2, the exact scheme, supported EVM networks, and EIP-3009 authorization. Permit2, non-EVM offers, and offers missing the token’s EIP-712 domain name or version are excluded. Sellers should check the actual offer their endpoint emits.&lt;/p&gt;

&lt;p&gt;For us, this is the interesting commercial possibility. A builder with a useful paid API has another documented buyer workflow to support. The work starts with one endpoint, a clear price, and a result worth purchasing. Wallet availability can remove a payment obstacle; customer demand still has to be earned.&lt;/p&gt;

&lt;h2&gt;
  
  
  A spending limit needs a defined scope
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://docs.metamask.io/agent-wallet/reference/outflow-policy/" rel="noopener noreferrer"&gt;outflow policy&lt;/a&gt; says signature operations are currently excluded from its outflow calculation. It also warns that tracking can be imprecise for transactions submitted outside the backend. Because x402 uses a signed authorization, we would verify its treatment before relying on the displayed daily limit as an API-purchase budget.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;That is a documentation-based integration question, not a demonstrated exploit.&lt;/strong&gt; We have not tested MetaMask’s budget enforcement or completed an end-to-end purchase with this client for this article. The practical response is to give the purchasing application its own explicit budget and record which requests it has already paid for.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://docs.metamask.io/agent-wallet/guides/pay-for-apis-x402/#idempotency" rel="noopener noreferrer"&gt;x402 helper’s retry behavior&lt;/a&gt; makes that record useful: rerunning pay creates a fresh debit authorization. Protection against replaying one signature does not make repeated purchases of the same resource free. A timeout needs investigation before another purchase attempt.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where we would start
&lt;/h2&gt;

&lt;p&gt;We would validate one inexpensive endpoint before building a larger integration. First inspect its payment offer without spending. Then, with an approved test budget, check the purchase, the settlement receipt, and the returned resource. Test interruption and retry handling separately. Those are our proposed acceptance checks, not results we are claiming today.&lt;/p&gt;

&lt;p&gt;MetaMask also supports &lt;a href="https://docs.metamask.io/agent-wallet/plugins/build-a-plugin/" rel="noopener noreferrer"&gt;plugins that add wallet commands&lt;/a&gt;. A service could eventually package its workflow as a command, with declared capabilities that the user reviews at installation. We would earn that extra integration work by first showing that the basic buying experience is useful.&lt;/p&gt;

&lt;p&gt;The bigger opportunity is straightforward: agents need useful things to buy. Clear documentation, an understandable price, and dependable delivery make a service easier to choose. A wallet expands what an agent can do; a good service gives it a reason to act.&lt;/p&gt;

&lt;p&gt;Building a service for agents? Start with the &lt;a href="https://forgemesh.io/scan" rel="noopener noreferrer"&gt;free ForgeMesh agent-readiness scan&lt;/a&gt;, then test the exact wallet client you want to support. This article is an educational review of documentation, not investment advice or a recommendation to delegate trading funds.&lt;/p&gt;

</description>
      <category>aiagents</category>
      <category>x402</category>
      <category>wallets</category>
      <category>security</category>
    </item>
  </channel>
</rss>
