AI Agent Faces Obstacles: Controllable Permissions More Urgent than Payments
When enterprises empower AI Agents, the most urgent concerns are controllable and verifiable permissions, rather than payments.
Written by: Christian
Compiled by: AididiaoJP, Foresight News
AI Agent Implementation Stuck on Permissions: Opportunities for Crypto Teams
Our crypto team has had many discussions with AI infrastructure companies, initially thinking that payments would be the biggest entry point. Stablecoin settlements are faster, cheaper, and easier to manage, which seems obvious.
However, the actual conversations have not reflected this. Compute and inference providers are more concerned with growth and fundamentals: how to lock in capacity, how to get deployments running, and how to maintain gross margins. Teams developing Agents repeatedly mention reliability and control—what the Agent can access, which actions must be pre-approved, and how the company can confirm what has actually occurred.
Payments remain a long-term direction for crypto and AI, but the clearer immediate need is verifiability. As enterprises delegate more tasks to Agents, they must be clear about: who approved the operation, where the permission boundaries lie, and whether the authorization is still valid. The crypto team’s long-standing work in signatures and delegated authorizations fits perfectly into this area.
Define Boundaries Clearly Before Delegating
When delegating tasks to an Agent, it must be reliable enough, and its permissions must be clearly defined. A permissions system cannot solve the problem of Agents making mistakes; however, once an Agent performs well enough to be trusted, enterprises still need to decide: which systems it can access, which actions require approval, and how to revoke permissions at any time.
This is especially important under new systems. Whether the Agent is helping users adjust company information or assisting developers in modifying production systems, enterprises must first define boundaries and ensure they can enforce them.
For example, a company uses an external software Agent to investigate production incidents. The Agent can read logs and propose fixes, but must obtain approval before modifying the system. The company authorizes, the provider runs the Agent, and the receiving system checks permissions—the entire process needs to be verifiable. A survey conducted in January 2026 with 150 IT and security decision-makers showed that 69% believe security concerns are slowing down Agent implementations, while only 27% think existing identity systems can effectively manage Agents at scale. Data breaches and excessive permissions are the main worries.
Research on deployed Agents points to the same issue. In "Measuring Agents in Production," reliability is cited as the biggest development challenge. Teams often restrict Agents to short processes and retain human intervention. Jellyfish’s engineering data similarly shows that while Agent participation is increasing, fully automated processes from demand to pull requests remain rare.
Coding Agents is another example: they can produce useful changes, but each deployment still requires human approval. Companies must clarify which systems they can modify, which actions need review, and how to revoke access. Better control allows enterprises to delegate more work.
Cross-Company Collaboration Requires a Trusted Record
When Agents work across companies, the issues become more complex. The company authorizes, the provider operates, and the receiving system enforces—three parties need a common basis to confirm whether "this operation was authorized."
Existing identity systems and application permissions already cover some of these needs. The opportunity for crypto technology lies in simplifying authorization, execution, revocation, and auditing across systems. The crypto team’s experience in signatures, delegated authorizations, and user-controlled accounts is directly applicable.
Existing cases illustrate this point. In the Turnkey Wayfinder case, Parallel Studios used session-based signatures, allowing users to authorize multiple transactions in one go while still retaining control of their wallets. Wayfinder is focused on on-chain transactions, but the more noteworthy aspect is enabling software actions without granting it unlimited permissions. A greater opportunity is to allow Agents to perform more tasks within the permissions that can be executed and revoked by the enterprise, while leaving a traceable record.
The value of blockchain lies in the need for multiple parties to have a shared permission record that no one can control alone, or the assets themselves are already on-chain. However, all parties must first agree on "who can authorize, what permissions are specifically allowed, and how to revoke"—this is precisely what blockchain excels at.
For off-chain applications, enterprises can put the Agent’s permissions, expiration times, and revocation records on-chain. This registry runs parallel to existing off-chain identity and application systems, with the receiving system verifying signature requests before allowing operations. Both the company and the provider can check the authorization content, while the receiving system is responsible for enforcement.
Most Agents currently operate off-chain. To enter enterprise clients, built-in controls must be able to integrate into their existing systems. For crypto teams, this means extending products beyond purely on-chain scenarios. The key test for market entry is simple: can target clients delegate tasks that were previously stalled due to permissions or approvals to the Agent?
-- Price
Selling to Enterprises: Start with Specific Stalled Tasks
Telling enterprises directly, "You need to trust your Agent," makes it hard to close a deal. A better approach is to start with specific tasks they want to delegate but are blocked by permissions or approvals, demonstrating how your product removes those barriers, and then explaining whether this improvement justifies introducing a new system—whether it’s worth it, and whether it can improve profits or open new business avenues.
Buyers depend on the scenario.
When deploying Agents internally, decision-makers are often identity or security engineering leads, with the CISO potentially being a sponsor. Pain points typically include excessive permissions, slow revocation, or difficulties in reconstructing operations during cross-system investigations. Sales should focus on a specific deployable solution that can unlock these issues, explaining how it integrates into the existing security framework.
Software companies selling Agents should engage with the CTO or the engineering lead for the Agent platform. First, inquire how much custom authorization each client deployment requires, whether it slows down onboarding or consumes engineering resources, and then demonstrate how your product meets those needs with less customization work and accelerates deployment.
In either case, founders must first clarify: who is maintaining the current temporary solution, what the costs are, and whether they are more likely to solve it themselves or are willing to pay a vendor.
Existing identity vendors have a first-mover advantage because their systems are already operational. Even if new products offer better control, clients will weigh integration and maintenance costs—some salespeople describe this as fighting against gravity. You must be clear about the shortcomings of existing systems and why clients would choose you over extending old systems. The threshold is not just filling gaps but ensuring improvements significantly outweigh adoption costs. Unlocking important Agent deployments may justify significant integration efforts; minor operational improvements must be easy to implement.
Starting with very specific workflows, take on as much integration work as possible yourself, rather than offloading the entire burden onto the client. If conversations confirm opportunities, conduct narrow pilots: allow the Agent to perform specific actions within the permissions the client can execute and revoke, and return records to existing auditing tools. Test whether it reduces integration work or allows clients to delegate tasks that previously required manual review while blocking unauthorized actions.
When assessing client opportunities, clarify these questions before engaging:
- What tasks does the client want to delegate? What is currently preventing that?
- Who is maintaining the temporary solution? What are the costs?
- What kind of improvements justify introducing a new system?
- What does adoption require from the client? How much can you take on?
- What does your solution make possible or significantly easier that existing tools cannot?
These questions should be clear before contacting clients, not afterward.
Payments Remain Important, but Should Be Secondary to Control
New payment infrastructures will only be adopted when they remove friction from what clients genuinely want to do. The growth of Agent adoption itself does not indicate which processes require new payment solutions. Specific needs depend on the scenario:
- When an Agent needs to access unfamiliar APIs, immediate payments may be necessary;
- When a coding Agent uses existing enterprise subscriptions, there may be no payment friction at all;
- Compute providers might benefit from different settlement methods, but more pressing operational issues often take precedence.
Only when current setups block clients from doing what they want will improving payments become a priority: needing to manually open accounts to purchase services, billing models making small purchases unfeasible, or settlements incurring high operational costs—these are the reasons for adopting new systems.
Payments also require control. Take AP2 as an example; it uses cryptographically verifiable authorizations to record what users allow Agents to do (including purchases made in the user’s absence). However, clients may only need better control, not necessarily another new payment method. An increase in transaction volume alone does not prove the need for new payment infrastructure unless you understand what clients are buying and why existing options are insufficient.
Conclusion
Before entering the agent economy, the real question is not how to bring stablecoins into AI business, but what can make these companies comfortable delegating more responsibility to Agents. Crypto and other cutting-edge teams should spend time working with teams that are filling this gap to solve problems. This is like selling anything new to enterprises: you must start from where the customer currently is, not from where you hope they will be.
This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.
You may also like

Polymarket US plans oil and gas bets after $1B in crypto trading

Threshold resumes tBTC bridge operations after outage from Oct 30 to Nov 10

Tencent: WorkBuddy Achieves Annualized Revenue of Over $500 Million in Seven Days, More Than Twice That of Tencent Meeting

Mining Giant MARA's Strategic Shift: Selling 40,000 BTC for Power Plants

Hyundai Card and JPMorgan's Kinexys Complete AI Agent Cross-Border Fund Management Proof of Concept

Tencent Open Sources Hy4 Flash, Releases Three Versions of Model Weights

Nomura Analysis: Tightening Overseas High-End Computing Power Creates Opportunities for Domestic AI Chips

Coinbase Ventures Dissects Agent's Four-Layer Tech Stack and Explains Investment Logic in the Sector

FinCEN Withdraws Crypto Travel Rule Proposal: What Still Applies

Key Focus Areas in NVIDIA's Earnings Report

AEREDIUM launches LOVEH lending protocol on testnet, offers 10,000 AERX for security flaws

Grvt Launches RWA Perpetual Contracts Linked to Traditional Market Financing Costs

Power Policy Dominates Midterm Elections, 'European Virginia' Becomes Latest Battleground

Hong Kong-listed firm sells 300 Bitcoin for $19.2M to fund AI deal

唐华斑竹 Suggests Optimizing WEEX Platform Token Functionality

Cardano Foundation seeks 25M ADA for 2027 events despite $1.2M funding gap

IOSF: The Cost Paradox of Video AI - Why Is Generating Cheaper but Final Cuts Still Expensive?

India Considers Limiting Leverage Trading to Curb Market Volatility

Uniswap freezes $300,000 in stranded fees, halting automatic token burns

Invesco Stablecoin Reserve Fund Launches on Ethereum, Issuing 80,000 Tokenized Shares

Strategy planned to slow STRC buybacks near $100 but spent another $1.4 billion instead

Thailand Stablecoin Transfer Limit: What the SEC Draft Proposes

J.P. Morgan's Forecast for 2027: Inflation Around 2% and Increased Pressure on the Dollar

The Amber Controversy: Diverging Paths with Wintermute

Mr&强 Attends WEEX Anthropic Event

Win an iPhone 18 Pro Max on WEEX? 201 Lucky Eggs Explained

Cardano holders reject 22M ADA treasury bid to buy physical copper

Global Cryptocurrency 'Audit' Trend Emerges

WEEX Lucky Eggs: How to Earn Daily Egg Cracks and Win Every Time
Learn how to earn daily WEEX Lucky Eggs from qualifying futures trading volume, check your progress, and understand what “Win Every Time” means.









