Product Marketing Engineer Intern – Intern

Cloudflare gives AI agents wallets that pay for what they access. * Cloudflare announced Wallets and cloudflare.pay identity handles on August 4, 2026. Handle reservation opened that day; funding, spending and merchant support are future tense in Cloudflare's own copy. * Paid access is not new. Pay per crawl launched in private beta on July 1, 2025 with three options per crawler: allow, charge, block. What changed is that charging extends beyond crawlers to any caller and any resource. * An Account Wallet held by a human delegates capped spend to agent-operated Virtual Wallets, with an allowance, an allow list and a maximum transaction size. * Declaring identity is optional for the agent. Cloudflare says merchants can enforce identification requirements, so declaration can still be made a condition of service. * Settlement is peer-to-peer into the seller's wallet. Cloudflare has named no custodian for wallet balances. Cloudflare announced wallets and optional identity for AI agents on August 4. Paid access is not new, but now extends past crawlers to any caller and resource. Cloudflare announced two products on August 4, 2026, during its Agents Week: Cloudflare Wallets, which will let AI agents hold stablecoins and pay for what they use, and cloudflare.pay, an optional identity handle that tells a merchant which account an agent acts for. Handle reservation opened the same day, and the payment features are future tense in Cloudflare's own copy. Charging for access is not the new part. Cloudflare launched pay per crawl, still in private beta, on July 1, 2025, and opened the Monetization Gateway waitlist on July 1, 2026 to extend charging past crawlers to any caller and any resource. What Wallets add is the side that pays. What cloudflare announced. Wallets come in two kinds. An Account Wallet belongs to a human and holds the funds. It delegates capped spending to Virtual Wallets, which agents operate through API keys. The balance is held in stablecoins, not card credit. Cloudflare says it will start with onramps and offramps in supported geographies, with self-funding via stablecoins as an alternative for eligible users. It has not named the supported stablecoins, the networks, or a custody partner. Cloudflare gives the limits as examples rather than a fixed set: "an allowance, an allow list, and a maximum transaction size." Its worked example is a company giving every employee a $100 per week budget for AI inference. That structure is what makes identity answerable, because every agent traces back to an account. The selling side is the Monetization Gateway, waitlisted since July 1, 2026. It will charge for "any asset protected by Cloudflare: web pages, datasets, APIs, or MCP tools." Payment clears at Cloudflare's edge before a request reaches the origin server. Compare that with pay per crawl, which in July 2025 offered three choices per crawler: "Allow: Grant the crawler free access to content. Charge: Require payment at the configured, domain-wide price. Block: Deny access entirely, with no option to pay." The mechanism is the same HTTP status code, but the scope is wider. Payments settle over x402, which uses status 402, Payment Required. x402 now sits under a Linux Foundation body whose members include Visa, Mastercard, American Express, Google, Shopify and Stripe. Almost none of the new capability works yet. "Soon, you will be able to set up and use your Cloudflare Wallet to pay for APIs and content," is what the announcement says. The press release puts full access in "coming months." How agent identity works. An agent that declares itself gets a readable name. A research agent might run at research.example.cloudflare.pay, which shows a merchant the organization behind it. The name sits on top of Web Bot Auth, which "already allows agents to register their identity via a keypair." Cloudflare presents the readable layer as a proposal rather than a settled standard, and says it is "not trying to define a particular schema or other verification system." Declaring is the agent's choice, in Cloudflare's words: "It will be completely optional for agents to choose to declare their identity or not, and it will be up to businesses to decide whether they want to prioritize transacting with known agents." That optionality sits on the agent's side. It does not remove a site's ability to make declaration a condition of service. Cloudflare says identity will let merchants "communicate with buyers who identify themselves or enforce identification requirements." Cloudflare's model for agents that decline is VPN traffic: "If someone is unidentified, they are not inherently untrustworthy, but they need to prove themselves more." Subscribe for daily search insights. AI, PPC, and digital marketing news distilled to fuel success. Join the other 75k marketers! What it means for businesses. Most requests for webpages are already automated. Cloudflare Radar put bots at 60.6% of requests to HTML content over the seven days to August 10, 2026, against 39.4% human. The category counts search crawlers and scanners alongside agents, so it is an outer bound rather than a count of agent traffic, and Radar is live, so the number moves. Optional declaration decides how much of that majority a site can put a name to. The consequences show up first in promotions, and Cloudflare even names the problem itself: "This lack of attribution challenges many traditional web business models. It's easy to give a one-week free trial or sign-up credits to a human or an organization. It's hard to give these same perks to an agent that lacks a stable identity and when one human can spin up dozens of agents under their control." Each of those mechanics assumes one human per account. Free trials and signup credits are the obvious cases. Referral bonuses, first-order discounts and usage tiers rest on the same assumption. The design goes further than that. "Stablecoin micropayments via x402 will make it simple to try an API without an account, allowing agents to test new options with little friction," the announcement says. No account means no signup, and no signup means no record of which company evaluated the product. Existing rules about who gets served were written for crawlers that identify themselves by convention, and for people who arrive one at a time. An agent that declines to declare fits neither category. Because a declaration cannot be assumed, a rule about these agents has to rest on what they do rather than what they say they are, which puts it in a site's terms of service and leaves its bot controls to enforce it. That leaves four cases to cover: | An agent that... A defensible response today | | Declares who it acts for and behaves like a user | Serve it, and prefer it once declaration is available | | Declares nothing but behaves like one person browsing | Serve it under existing limits | | Declines to declare and requests at machine scale | Throttle it with existing bot controls | | Claims a trial, credit, or discount | Require the same identity a person would need, and say so in the terms | The last row is the one with money attached, because that is where an undeclared agent costs a business something rather than merely consuming bandwidth. What it does not cover. Settlement happens peer-to-peer, directly into the seller's wallet. Under pay per crawl Cloudflare was Merchant of Record. Under the Monetization Gateway, it is not in the settlement path at all, though it still runs the wallet, the handle, and the onramp. Beyond a waitlist, there is no general availability, no published pricing, and no AI company named as a paying counterparty. What to do now. Audit the terms of service for the identity gap on trials and credits. The mechanics that assume one human per account are the ones an undeclared agent reaches first, and that audit depends on no vendor releasing anything. Hold off on making any AI crawler block permanent. Paid access already exists for crawlers and is extending to everything else behind Cloudflare, so a block written into a contract or a content policy now is one that may need unpicking.

Cathie Wood's ARK Invest buys Rocket Lab and Cloudflare, sits out crypto stocks. ARK Invest added Rocket Lab across three ETFs and Cloudflare across two funds on August 11, while its disclosed trades showed no transactions in several major crypto-linked holdings. Published 2 hours ago · Updated 1 hour ago AI Summary ARK Invest's August 11 trades added $23.4 million in Rocket Lab shares, amid a share price decline after the company's Q2 results Cathie Wood's ARK Invest focused its August 11 buying on Rocket Lab and Cloudflare, adding shares as Rocket Lab shares fell following its second-quarter results, while making no disclosed trades in several of its major crypto-linked holdings. According to ARK's daily trade disclosures, the firm bought Rocket Lab across three exchange-traded funds and added Cloudflare to its ARK Innovation ETF (ARKK) and ARK Fintech Innovation ETF (ARKF). For investors tracking ARK's crypto exposure, the notable detail was what did not appear in the day's disclosed trades: no transactions in Coinbase, Circle, BitMine, Robinhood, or Bullish. The trades do not by themselves establish a change in ARK's view of crypto equities. ARK does not trade every holding every day, so the absence of transactions should be treated as a data point rather than evidence of a deliberate decision to avoid the sector. Rocket Lab leads ARK's buying. Rocket Lab was the largest disclosed purchase by share count. ARK bought 200,987 shares through ARKK, 64,785 shares through the ARK Autonomous Technology & Robotics ETF (ARKQ), and 27,101 shares through the ARK Space Exploration & Innovation ETF (ARKX). The three purchases total 292,873 shares. Rocket Lab closed at $80.01 on August 11 as per Nasdaq data. At that closing price, ARK's combined purchase represented approximately $23.4 million in market value. The figure is a calculation based on the closing share price and the disclosed share count, rather than a statement of ARK's actual execution price. The purchase came as Rocket Lab shares declined following the company's second-quarter results on August 10. Rocket Lab reported record quarterly revenue of about $234 million, up 62% year over year, while its quarterly loss per share was wider than expected. The company also highlighted a record backlog of about $2.36 billion. ARK's decision to add shares during a sharp post-earnings decline is consistent with a pattern of the firm increasing positions during periods of significant price weakness. However, the trade notification does not establish the specific reason for the purchase, so the timing is better viewed as an observable portfolio action rather than evidence of a particular investment rationale. Cloudflare adds a crypto-linked element. Cloudflare was the other notable name in ARK's August 11 buying activity. ARK purchased 6,090 Cloudflare shares through ARKK and 1,471 shares through ARKF. Cloudflare closed at $306.97 on August 11 as per Nasdaq data. The purchases were considerably smaller than the Rocket Lab position by share count, but Cloudflare has a direct connection to blockchain-based payments through its work on the x402 protocol. Cloudflare and Coinbase have worked together on x402, an open payment standard designed to support automated payments between applications, websites and AI agents. Cloudflare has also been developing programmable wallets for the agentic internet. The company said its wallets are designed to provide AI agents with native payments and verifiable identity, using x402 to facilitate transactions. That gives Cloudflare a clear crypto-adjacent element within ARK's August 11 trades. It does not, however, make the company a crypto-focused business. Cloudflare remains primarily an internet infrastructure and cybersecurity company, and the ARK purchase was a relatively small portfolio adjustment compared with the Rocket Lab buying. Crypto stocks go untraded. ARK's August 11 disclosures did not show transactions in several of the crypto-linked companies that have featured prominently in its recent trading activity, including Coinbase, Circle, BitMine, Robinhood, and Bullish. The lack of trades is notable because ARK has been active in digital-asset-related equities, including buying and selling shares of companies tied to crypto trading, stablecoins and Bitcoin treasury strategies. But the disclosure should not be interpreted as evidence that ARK has changed its position on those companies. A daily trade report records transactions rather than investment intentions. A holding that does not appear in a day's trades may simply have been left unchanged. The August 11 data therefore supports a narrower conclusion: ARK's disclosed buying on that session was concentrated in Rocket Lab and, to a lesser extent, Cloudflare rather than its major crypto-linked holdings. The rest of ARK's trading. Beyond Rocket Lab and Cloudflare, ARK's August 11 activity included purchases across biotechnology and drug-discovery companies. The firm bought shares of Intellia Therapeutics, Cerus, and Schrödinger across its funds. It also reduced positions in several companies, including Shopify, Snowflake, Deere, Caterpillar, 10x Genomics, and Twist Bioscience. None of those disclosed sales involved the major crypto-linked companies identified above. The mix shows that ARK's daily activity extended well beyond digital assets. The firm's portfolios cover a range of disruptive-technology themes, meaning individual trade disclosures should be viewed within that broader investment mandate rather than as a direct measure of crypto sentiment. What the trades show. The August 11 disclosures point to two clear developments: Rocket Lab was the dominant purchase, while Cloudflare was the day's most direct crypto-adjacent addition. The Rocket Lab buying came as the space company faced renewed investor scrutiny following its second-quarter results and concerns around the timing of its Neutron program. Cloudflare, meanwhile, gives ARK's trading activity a connection to the developing stablecoin and agentic-payment ecosystem through x402 and related products. What the trades do not establish is a new ARK position on crypto equities. The absence of Coinbase, Circle, BitMine, Robinhood, and Bullish from the day's disclosed transactions is observable, but it does not reveal why ARK did not trade those names. For investors using ARK's daily disclosures as a gauge of institutional sentiment, the most defensible takeaway is therefore limited: on August 11, ARK's disclosed buying favored Rocket Lab and Cloudflare, while its major crypto-linked holdings were not part of the day's reported transactions. This article is for general informational purposes only and is not investment advice. It makes no prediction about ARK Invest's future trades. Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions. Discover more Digital Currencies Company News

Cloudflare reported second-quarter revenue of $696.1 million, up 35.9% year-on-year and beating analyst estimates by 4.7%. The cloud security firm's adjusted earnings per share of $0.29 also exceeded expectations by 7.5%. CEO Matthew Prince attributed the strong performance to rapid adoption of the company's Workers developer platform and growing demand for application security services. He said developers are choosing Cloudflare to build applications for machine-to-machine internet traffic. The company raised its full-year revenue guidance to $2.87 billion and lifted adjusted EPS guidance to $1.26. Next quarter's revenue is forecast at $736.5 million, above analyst projections. Management highlighted new monetization models for agent-based internet traffic as key growth drivers. CFO Thomas Seifert noted Cloudflare's position to capitalise on changing internet business models whilst maintaining operational efficiency.