https://www.youtube.com/watch?v=c3HHFL_lsLM
TLDR AI agents can handle tasks like shopping, travel, email, and coding, but businesses are setting different rules for their access amid security and privacy risks. Shared authorization standards could make agents safer and more useful, but until they mature, expect a fragmented internet where agents work well only on approved services and specific tasks.
Start with a task the agent can handle well rather than expecting one assistant to do everything. The examples in the text show agents specializing in coding, email and scheduling, travel, or shopping. Test an agent on a low-stakes task first, and check its work before relying on it. A focused use case makes it easier to judge whether the agent is useful and dependable.
Decide what the agent may access, change, or purchase before asking it to act on your behalf. Permission to identify itself as an agent does not automatically mean permission to view private information, make payments, or cancel reservations. Use controls such as seller, spending-limit, and expiration restrictions when available, and review important actions before they are completed. These boundaries help reduce the risk of fraud, privacy leaks, and costly mistakes.
Do not assume an agent can use every website or service. Businesses may offer authorized routes, allow agents to browse with restrictions, or block them entirely. When an agent cannot complete a task, check the business’s rules or use its official app or website rather than trying to bypass its safeguards. Access can vary between services, so choose providers that support the tasks you need.
Agents can help compare products, travel options, and policies, but their results may be incomplete or outdated. Confirm key facts such as prices, cancellation terms, shipping destinations, and return windows on the business’s own site before committing. Be especially cautious when a task involves money, travel plans, or sensitive personal information. Treat proactive reminders and recommendations as useful prompts, not substitutes for verification.
When an agent needs to pay, use established checkout or payment methods that clearly connect the transaction to your approval. Emerging tools can limit payments by merchant, amount, or expiration, while some business payment pilots tie an agent’s purchase to a specific invoice. Before approving a transaction, confirm the seller, amount, and purpose. Avoid giving an agent broad or reusable payment credentials when a more restricted option is available.
AI agents can be useful for knowledge work, coding, scheduling, and email, while broader online tasks still involve uneven access and security risks. Introduce them to less-technical users through concrete, low-risk tasks and explain what the agent can and cannot do. Keep human review for consequential actions, and stop using an agent if it behaves unexpectedly or reveals sensitive information. Expand its responsibilities only after it has performed reliably.
Businesses are increasingly restricting automated access because agents can be difficult to distinguish from malicious activity and can make cyberattacks easier. Each business can decide whether to allow agents, so access will vary across the internet.
Grockbot is used for complex coding and coordinated builds; Dots for project-aware calendar and email coordination; Instinct for travel; Muse for shopping, gifts, and bookings; and Duet for intelligent assistance and proactive reminders. Dots and Duet are especially good at surfacing useful information before being asked.
Businesses need to distinguish authorized agents from malicious ones and determine exactly what each agent is allowed to do, such as view information, make purchases, or change or cancel reservations.
Examples include a Visa, Bill, and Billtrust pilot for paying approved invoices, Cloudflare’s signed-agent system, Google’s Agent Payments Protocol, and Stripe’s shared payment tokens, which can limit transactions by seller, amount, or expiration. There is not yet a shared standard.
Agents may follow malicious website instructions or expose personal information. For example, Claude reportedly disclosed human email addresses after following instructions to identify itself. Businesses and assistants need to handle agent identification responsibly and protect users from fraud and privacy leaks.
Businesses will need to make product details and policies—such as cancellation terms, shipping destinations, and return windows—easy for agents to find and compare. Since agents rely more on accurate information than flashy marketing, this could reward product quality. Shopify is adding agent-specific information and bringing Shop Pay into assistants, while retailers increasingly view assistant recommendations as a distribution channel.
The partnership zone offers authorized routes for agents; the aspiring-actor zone lets agents navigate websites like people, though they may encounter obstacles or be told to stop; and the no-go zone blocks agents. Businesses’ choices reflect, in part, who controls the customer relationship.
Organizations should support open safety protocols and make their agent-access rules clear. Consumers should focus on specific use cases where agents work well, such as coding, scheduling, email, and knowledge work, rather than assuming agents are safe and effective everywhere. Less-technical users need clear, specific explanations of what agents can do.