Source: raw/reddit-1vhlrsd.md — r/hermesagent, u/obdurant93, 2026-08-07, 38 score / 32 comments, “Strategy — Business models, monetization, automation” flair. Refreshed 2026-09-29 with raw/Robinhood_s_Vlad_Tenev_on_Tokenizing_Everything_OpenAI_s_6_Misalignment_Reports_Figure_s_Robot.md (Peter H. Diamandis Moonshots, interview with Robinhood CEO Vlad Tenev, https://www.youtube.com/watch?v=LNBzLTLuLUo). Refreshed 2026-10-27 with The AI Daily Brief (raw/Where_Gemini_4_Argon_Fits.md, https://www.youtube.com/watch?v=SX9LQD3yINg), Greg Isenberg (raw/The_9_Stages_of_AI_Agent_Adoption_Explained.md, https://www.youtube.com/watch?v=nRl-7Yhmbog), Last Week in AI 258, Hard Fork and The Artificial Intelligence Show Ep 247: the October split between platforms that block personal agents and platforms that open an API for them. Refreshed 2026-11-09 with The AI Daily Brief (raw/How_a_Data_Center_Slowdown_Benefits_Big_Tech.md, https://www.youtube.com/watch?v=ssEWGHjKHTM): smaller banks issuing agent accounts.
Most writing about monetizing agents assumes the constraint is capability. This argues the constraint is permission — that the tasks where an agent could plausibly generate direct revenue are precisely the tasks that violate some critical platform’s terms of service or have no authorized control surface at all. It is the counterweight the wiki’s agent coverage has been missing: extensive material on what agents can do, almost none on what they are allowed to do.
The author’s reframe is the keeper:
The real question is not “What can an agent do?” It is “What can an agent legally, reliably, and contractually be allowed to do that someone will actually pay for?”
The gap this fills
The author opens by naming what agent-monetization content usually covers: basic office automation (responding to email) or, in their words, “unicorn-fart marketing and advertising nonsense like SEO and CRM optimization.” Both are real, but both are internal — they automate work inside systems you already control.
The moment an agent reaches for external economic value — buying, selling, listing, negotiating, executing a transaction — it hits a wall that has nothing to do with model capability.
The worked example: marketplace arbitrage
Retail and marketplace arbitrage is chosen deliberately because it is the cleanest theoretical fit. An agent should be able to search multiple marketplaces, identify pricing discrepancies, calculate fees and shipping, evaluate sell-through rates, and flag profitable inventory. Every step is well within current capability.
What actually blocks it:
- eBay tightly controls production access to portions of its Buy APIs. Developers may need business-model approval, support approval, contracts, and additional eligibility checks. eBay itself advises obtaining production approval before investing heavily in development — an unusually direct warning that building first is a mistake.
- eBay’s User Agreement broadly prohibits robots, scrapers, data-mining tools, LLM-driven bots, and other automated access without express permission. Note that LLM-driven bots are named as their own category.
- Other marketplaces offer less. Frequently no useful public API for search, sold-history analysis, purchasing, inventory management, or order execution. Some offer seller integrations but no meaningful buyer-side control surface. Others provide APIs only to approved partners whose business models align with the marketplace’s own interests — which is to say, partners who are not competing with the marketplace.
Why the scraper workaround is not a workaround
The fallback is unofficial scrapers, browser automation, and services built on platforms like Apify. The author’s argument against treating this as a solution has two parts, and the second is the one that matters:
It is fragile. Marketplaces deploy CAPTCHAs, rate limits, fingerprinting, session controls, IP blocking, and constantly changing page structures. Apify’s own documentation discusses the need to bypass anti-scraping systems through proxies and session rotation — the tooling openly acknowledges it operates against active resistance.
It is adversarial by construction. A business automation built this way depends on an unauthorized and adversarial data source that might stop working tomorrow, get its accounts blocked, lose access to a critical endpoint, or expose your own marketplace account to enforcement. The existence of an eBay scraper on a marketplace of scrapers does not mean eBay authorized it — and the account at risk is yours.
This is a materially different risk profile from ordinary technical debt. The dependency is not merely brittle; it is one whose counterparty is actively trying to break it and can penalize you for using it.
The pattern generalizes
The author’s list of near-misses is the most useful part of the source, because each one is a capability that exists paired with a permission that does not:
| The agent can | But it cannot |
|---|---|
| Identify profitable inventory | Reliably purchase it |
| Generate listings | Publish them without restricted API access |
| Cross-list inventory | Safely monitor every marketplace for sales and auto-remove duplicates |
| Evaluate sold comparables | Legally or reliably collect enough historical data |
| Negotiate with buyers | Avoid rules against automated messaging or autonomous purchasing |
| Find a profitable opportunity | Execute the transaction without handing control back to a human |
Every row terminates at the same place: the step that actually moves money is the step that is gated.
The author’s closing image:
We keep hearing that agents will become autonomous workers. Right now, however, many of them are more like extremely capable employees who are prohibited from entering the building, using the company software, accessing the necessary records, touching the inventory, communicating with customers, or completing a transaction.
Framed via Joel Salatin’s Everything I Want to Do Is Illegal, a book about regulatory constraints on small-scale agriculture — the analogy being that the binding constraint sits in institutions rather than in the work itself. The author is careful not to make this a grievance: “Automation is not trusted by default, perhaps for good reason.”
A sanctioned counter-example: Robinhood Agentic Trading (2026-09-29)
One platform has built the authorized agent surface itself. On Peter H. Diamandis’s Moonshots, Robinhood CEO Vlad Tenev describes Agentic Trading (raw/Robinhood_s_Vlad_Tenev_on_Tokenizing_Everything_OpenAI_s_6_Misalignment_Reports_Figure_s_Robot.md):
- A separate, segregated brokerage account, walled off from the user’s main Robinhood and retirement accounts.
- The user creates it and funds it affirmatively. “People typically fund it with $100.”
- It started narrow and widened. Launch was equities only, “no leverage, no margin.” Robinhood has since added options trading, limited margin and crypto.
- The agent runs from Claude Code or Codex. “Right now you have to do all of your trading from within your Claude Code or your Codex,” using Robinhood’s tools and MCPs. Tenev calls that “very very complicated” for the general public, and says Robinhood is working to slim it down.
He gives two operator lessons:
- General models often refuse to trade. They say things like “I don’t really feel like trading right now,” because they are not trained for it. He expects specialised or fine-tuned models to follow.
- The real use today is automation, not alpha. Agents are “really really good” at assembling multi-leg option structures such as an iron condor, “removing the paper cuts” of building a trade you already had in mind.
Diamandis puts usage at “over 100,000” Robinhood accounts running AI agents for trading. That figure is the host’s, not Tenev’s, and is unverified.
Read against this article. The platform has pre-built the gate this article’s Try It recommends. A small, separately funded account is a spend ceiling set by the platform rather than by the agent builder. So “the revenue step is the gated step” still holds; the platform decides where the gate sits, and inside it the agent may transact. ^[inferred — the reading against this article is this wiki’s; the product facts are Tenev’s, first-hand]
October 2026: the market splits into blockers and openers
Sources: The AI Daily Brief (raw/Where_Gemini_4_Argon_Fits.md, raw/Gemini_4_Argon_Sonnet_5.5_and_What_Models_You_Should_Be_Using_Right_Now.md); Greg Isenberg (raw/The_9_Stages_of_AI_Agent_Adoption_Explained.md); Last Week in AI 258; Hard Fork; The Artificial Intelligence Show Ep 247. All relays of public statements or the hosts’ own opinions.
Blockers.
- JPMorgan will block third-party agents that log in with customer credentials. Jamie Dimon: “We’re not going to allow just any outside agent to come inside the company because it’s just too risky.” A spokesperson told CNBC the bank supports “secure customer authorized data sharing through open banking providers.” Whittemore’s read: agents will likely get read-only access for tasks like budgeting, but not to “pay bills or settle invoices.”
- Amazon blocked Meta’s Muse agent. Last Week in AI: Meta “reportedly never notified Amazon,” and Amazon says Muse “doesn’t identify itself while browsing and appears to capture customer details.”
- Reservation apps. Hard Fork: agents booking tables are “breaking Resy,” and “these apps are getting banned.”
- The AI Daily Brief groups Amazon, eBay and JPMorgan as “locking their platforms down and forcing customers to use their proprietary agents.”
Openers.
- Shopify first gave Muse direct backend API access, which also spared it the hosting cost of agents scraping its storefront, then “extended this arrangement to agents from any provider … whether they’re using Muse, Town, Hermes, Instinct, Dots, or any of the other dozens of personal agents.”
- DoorDash built its own text-to-order agent and says “agentic orders have a 50% higher basket value when buying groceries.”
- A permission standard. Sierra and Meta announced the Personal Agent Protocol, “an open standard for personal AI agents to interact with businesses under customer controlled access and business defined limits,” with 35 more design partners including OpenAI, Visa and PayPal (The Artificial Intelligence Show).
The middle position (Bob Sue, via The AI Daily Brief): “Users don’t need agents locked out. They need agents locked down, scoped permissions, hard limits, a kill switch.”
Isenberg’s frame (opinion). An agent is “a customer with a credit card and no eyes,” and “loyal to whatever worked last time.” It climbs a ladder of trust: research (“find options, compare them”), prepare (“put it in the cart, hold the seats, get me a quote”), then pay, which is where the fight is. His nine-stage forecast runs from blocking, through an arms race and a split (sellers let agents in, data owners charge, giants build their own), to “a trusted middle layer for agent identity and payments” (“the plaid moment”), then welcomers winning, competition for agents, ads returning, and finally selling to agents becoming as normal as having a website. (The transcript skips stage six.)
Read against this article. The TOS ceiling is now being set platform by platform, and the platforms that make money on sales are the ones lifting it.
Update 2026-11-01: authorized payment routes multiply
Source: Nate B Jones, raw/The_Future_Of_The_Internet_Isn_t_Open_For_Your_Agent._Muse_Dots_And_Claude_Duet_Will_Find_Out..md (https://www.youtube.com/watch?v=c3HHFL_lsLM). Announcements as he relays them.
- A B2B invoice pilot. On October 20, Visa, Bill and Billtrust announced a live pilot: a buyer approves a supplier’s bill, and Bill’s agent pays it through the supplier’s portal via Billtrust. The agent is registered, its payment credentials follow the buyer’s instructions, the receiving system recognises the agent and grants access, and the payment is tied to the invoice from approval to completion.
- Credentials that carry their own limits. Google’s agent payments protocol (AP2, in the caption “a”) describes signed records for instructions and purchases. Stripe’s shared payment tokens restrict a credential to one seller, an amount limit, or an expiry time.
- No agreed schema yet. “We don’t yet have a full schema for rules of the road that everybody agrees on.” A site that “supports agents” may allow research but stop at payment, or accept one kind of payment authorization and not another.
- Shopping is still where hosted agents fail. In Claire Vo’s benchmark (
raw/I_tested_4_AI_agents_on_9_real_tasks._Here_s_who_won..md), Claude Duet was “blocked by almost every shopping site” on a shoe search while Grok Bot and Muse completed it. See Claire Vo’s Personal Agent Benchmark.
Read against this article. Each new route moves the gate, it does not remove it: payment happens where a registered agent, a scoped credential and the receiving business agree. ^[inferred] Jones’s three zones (partnership, browse-as-a-person, no-go) are summarised in The Agent-Readable Web.
Update 2026-11-09: smaller banks issue agent accounts
Source: The AI Daily Brief headlines, raw/How_a_Data_Center_Slowdown_Benefits_Big_Tech.md (https://www.youtube.com/watch?v=ssEWGHjKHTM), relaying The Information.
- The big banks block. Last month the CEOs of both JPMorgan and Bank of America said they would block agents from accessing customer accounts, seeing the risk of agent mistakes as too large.
- Smaller banks open a scoped route. Lead Bank in Missouri lets its fintech partners issue bank account numbers for agents. They work like a credit card issued to an agent: the customer sets spending limits and restrictions on what the agent can do, and a “panic button” locks the agent out “if it goes haywire.”
- Increase, an internet-only bank, offers segregated accounts for agent use and an agent-friendly API. Its owner, Derek Buckley: “we don’t need the entire industry to coordinate banking for agents. It’s sufficient to have just a small cohort of technology forward banks.”
These accounts are the “locked down, not locked out” position above put into a product: scoped limits plus a kill switch.
November 2026: United bars personal AI agents from booking
Source: ai-research/theverge-united-unauthorized-ai-agents-2026-11-13.md (a fact digest of The Verge, relaying the WSJ and a United statement, with other outlets’ snippets).
- United announced on November 11 that personal AI assistants may not book its tickets, on its own site and app or indirectly through travel agencies and aggregators, and added the rule to its Contract of Carriage (per the other outlets’ snippets). Agents can still show United flights; they cannot complete the purchase.
- United’s stated reasons: agents could expose customer information, make unintended purchases, and skip disclosures federal rules require, such as the dangerous-goods attestation. CEO Scott Kirby, per the WSJ: “I don’t want to create another middleman.”
- United says few people have tried to book through agents so far, and that it may revisit the rule as agents and traveller protections mature. The Verge names Meta’s Muse and OpenAI’s Dots as affected and says eBay and several large banks have similar restrictions.
- For anyone building a booking agent: an airline can now refuse agent purchases contractually, so plan for a hand-off to the user at checkout.
Key Takeaways
- The binding constraint on agent monetization is contractual, not technical. Model capability is ahead of platform permission, and the gap is widening rather than closing.
- Check the TOS and the API access tier before building, not after. eBay explicitly advises securing production approval before investing in development. This inverts the usual build-then-scale instinct.
- “LLM-driven bots” is now a named prohibited category in at least one major marketplace’s user agreement — automated access rules are being updated specifically for agents.
- Partner-only APIs are a business-model filter, not a technical one. Access is granted to partners whose interests align with the platform’s, which structurally excludes arbitrage and most disintermediation plays.
- A scraper dependency is an adversarial dependency. Unlike normal brittleness, the counterparty is actively working against you and can penalize your account for the attempt.
- The revenue-generating step is the gated step. Across every example, the agent can do the analysis and stops at execution — which means “human in the loop” is often a contractual requirement, not a safety preference.
- Some platforms now build the gate themselves. Robinhood Agentic Trading lets an agent execute trades, but only inside a segregated, separately funded account (Tenev, 2026-09-29). The gate moved from the agent builder to the platform; it did not disappear.
- October 2026 split the market (2026-10-27). JPMorgan and Amazon block personal agents; Shopify opened its backend API to any agent and DoorDash reports 50% larger agentic grocery baskets. The ceiling is now set per platform, by business model.
- Payment routes are being built per partnership (2026-11-01). The Visa-Bill-Billtrust invoice pilot, Google’s AP2 and Stripe’s scoped shared payment tokens each authorise a registered agent for a limited payment; there is no common standard yet.
- This is argument, not data. No revenue figures, no enforcement statistics, no cited case where an account was actually banned. Its value is the structural frame and the specific eBay citations, not measurement.
Try It
- Before scoping any agent that touches an external platform, read that platform’s user agreement for the automated-access clause and check whether the API tier you need is self-serve or approval-gated. Do this before writing code, not after a prototype works.
- Classify your agent idea as internal or external. Internal automation (your inbox, your CRM, your files) has no TOS ceiling. External automation almost always does. The wiki’s existing monetization coverage — see Hermes user stories — skews internal for exactly this reason.
- If an authorized API exists but is partner-gated, price the approval process into the plan — contracts and eligibility review are a timeline item, not a formality.
- Where the gate is real, design for the human-approval step rather than around it. The Cairn multisig gate and Managed Agents budgets both treat the human co-sign as a permanent architectural feature rather than a temporary limitation.
- If you sell online, run Isenberg’s agent-readiness check this week (from his five actions): take 10-12 real buying questions from your support inbox and give each to two or three agents to see where they get stuck; check that bot protection is not blocking agents by accident; put total price, delivery date, compatibility and returns in plain text on the page; make your advantage (for example faster delivery) visible to an agent; and decide what agents may do on each rung, with an extra check before money moves.
- Where a platform offers a sanctioned agent account, use it and fund it small. Robinhood’s model (a segregated account, funded affirmatively, starting around $100, with leverage added only later) is the shape to look for. Expect general models to balk at the transaction step; use them to assemble the order, not to hunt for alpha.
Open Questions
- No enforcement data. The argument that scraper-based automation gets accounts banned is presented as risk, not as an observed rate. How often does enforcement actually fire against small operators?
- The eBay citations are paraphrased from the source, not quoted from eBay’s documents. The Buy API access tiers and User Agreement language should be verified against eBay’s own text before being relied on for a real build.
- Does an authorized path exist that the author missed? Partly answered 2026-09-29. Some marketplaces run affiliate or partner programs that permit exactly this analysis under different terms, and the post surveys restrictions without surveying sanctioned alternatives. Robinhood Agentic Trading (above) is one sanctioned path in brokerage, not marketplaces. Whether eBay-style marketplaces will offer an equivalent segregated agent account is still unknown.
- Where is this heading? If agent-driven commerce grows, platforms could tighten further, or open metered authorized surfaces. The post does not forecast, and the wiki has no data either way. (Partly answered 2026-10-27: both are happening. JPMorgan and Amazon tightened, Shopify opened a metered API, and Isenberg forecasts an identity-and-payments layer as the eventual standard. Still no enforcement or revenue data.)
- Will the Personal Agent Protocol become the permission layer? Draft only, as of the Ep 247 report (added 2026-10-27).
- How does this interact with agent-to-agent payment rails? The Cairn experiment published a spec for machines paying machines with no human involved. That route sidesteps marketplace TOS entirely by not using marketplaces — whether it can reach real economic volume is untested.
Related
- Cairn — a Multisig Spend Gate for an Autonomous Agent — the same problem from the money side: what an agent may spend, versus what it may transact
- Token Economics — A Primer for the Agentic Era — the cost side of the same monetization question
- The Agent-Readable Web — the access half of this argument: what agents can reach, and who decides
- Personal Agents Compared (October 2026) — the agents (Muse, Dots, Grok Bot, Instinct) that platforms are now blocking or welcoming
- TinyFish and Firecrawl — the “give your agent the web” tools whose authorization status this post questions
- Hermes Agent — User Stories and Use Cases — the internal-automation use cases that sit below this ceiling
- Claude Managed Agents — where the human-approval step becomes a platform primitive