Navigating the AI Frontier : Part 1: Art, Identity, and Fairness: AI in Our Creative and Daily Lives

In a nutshell (TL;DR)...

Artificial intelligence offers exciting creative possibilities, but it also poses serious risks to human creators, individual privacy, and societal fairness. Generative AI tools frequently scrape copyrighted artwork, books, and music without permission or compensation, threatening artist livelihoods and flooding digital markets. Meanwhile, voice cloning and digital replicas enable identity theft and likeness exploitation without clear legal protections. Additionally, AI systems can absorb and amplify historical human biases, leading to unfair decisions in hiring, healthcare, and law enforcement. To navigate this frontier responsibly, we must protect human creative rights, advocate for algorithmic transparency, and remain vigilant media consumers.

It’s been all over the news lately. AI is going to kill us all. So I decided to think about the different ways in which AI can negatively impact us and what we could possibly do about it. In this first blog, let’s look at a subject that concerns my arty pursuits and that’s how AI is encroaching on the creative efforts of humans by pretty much doing it for us….

Welcome to the AI Creative Era

Today, AI is everywhere, generating vibrant digital paintings, drafting essays, composing melodies, and answering complex questions in seconds. It is an extraordinarily exciting tool that expands what human imagination can achieve. At the same time, like any powerful breakthrough, it requires gentle care, clear understanding, and thoughtful guardrails. As we step into this new creative era, we must ask: how do we celebrate technological magic while respecting the human skill, dedication, and legal rights behind the data that makes it all possible?

However, while AI tools offer thrilling new capabilities, they also introduce a subtle tug-of-war between high-speed digital automation and fundamental human creative rights.

The Creative Dilemma: Art Scraping, Copyright, and Style Theft

Behind every generative AI model sits a massive mountain of training data. To teach these systems how to draw, write, or compose, automated software tools known as "web crawlers" scan publicly available websites, databases, and digital platforms. They harvest books, news articles, photographs, artwork, and sound recordings, storing multiple digital copies to train complex machine learning algorithms.

This process frequently occurs without asking for the creator's permission, without giving credit, and without paying a licensing fee. In the UK copyright framework, this creates a significant legal issue. Under the Copyright, Designs and Patents Act 1988 (CDPA), making digital copies of protected works engages the restricted act of reproduction. While Section 29A of the CDPA provides a specific exception allowing automated text and data mining (TDM), that exception applies strictly to non-commercial research. Commercial AI developers building models for market deployment cannot legally rely on Section 29A. Proposals to introduce a broad commercial TDM exception, or to allow unlicensed scraping under an "opt-out" scheme, threaten to strip creators of their primary lever for fair compensation.

For creative workers, this creates a profound dilemma. Human artists spend years, sometimes a lifetime, honing their craft, only to find that automated web crawlers ingest their catalog without consent, allowing software to imitate their work in seconds and flood the market.

To understand the contrast between human artistic effort and machine outputs, consider the following comparison:

Human Creative Value	AI-Generated Output Characteristics
Skill & Dedication: Built on years of personal effort, emotional experience, and deliberate practice.	Instant Pattern Assembly: Generated in seconds by synthesizing statistical patterns from massive datasets.
Unique Expression: Produces original, intent-driven works rooted in human culture and storytelling.	Style Imitation: Capable of generating close replications or "in the style of" imitations without personal understanding.
Economic Livelihood: Relies on paid commissions, royalties, and explicit licensing to sustain a career.	High-Volume Output: Produces vast quantities of low-cost content (sometimes called "AI slop") that can crowd out human work.

The financial and professional impact on human creators is backed by striking evidence:

• Economic Powerhouse at Risk: The UK creative industries contributed £124 billion in Gross Value Added (GVA) to the economy in 2023 (projected to reach £141 billion by 2030) and employ 2.4 million people. By comparison, dedicated UK AI firms generated £11.8 billion GVA in 2024. Sacrificing a proven creative sector for speculative AI gains risks undermining a vital economic engine.

• Loss of Artist Livelihoods: Sector surveys reveal that 58% of surveyed photographers have lost work to generative AI, while 86% of authors report decreased earnings, leading 57% of authors to feel that writing is no longer a sustainable career.

• Streaming Market Dilution: Music streaming platforms face an unprecedented surge of fully AI-generated tracks—rising from 30,000 to 60,000 AI tracks uploaded per day on platforms like Deezer (representing 39% of all daily uploads)—which dilutes royalty pools meant for human musicians.

As automated scraping captures the written and visual work of human creators, an even more personal question arises: what happens when technology captures our physical identity and voice?

The Digital Doppelgänger: Voice Cloning and Likeness Rights

Beyond taking written or visual works, generative AI can now capture the distinct characteristics of a human being, their physical appearance, facial expressions, and vocal tone. Using short audio snippets or a handful of photos, software can generate highly realistic "digital replicas" or "deepfakes" that make a person appear to say or do things they never actually did.

> What is a "Digital Replica"? A Digital Replica is an AI-generated copy of an individual's unique voice, face, or physical appearance. When deployed without permission, digital replicas strip individuals, from professional actors and voice artists to everyday citizens, of control over their identity and livelihood. Under current UK law, there is a distinct legal gap: there is no standalone "personality right" or "voice likeness right," leaving creators unable to easily stop others from commercializing their personal persona.

International policy offers clear models for closing this gap. For instance, Denmark has proposed Copyright Act amendments specifically creating statutory protections against unauthorized digital replicas of an individual's physical characteristics and artistic performances (while preserving traditional carve-outs for parody and political satire). Similarly, in the United States, proposed federal legislation like the NO FAKES Act, alongside state-level publicity rights, aims to give every individual explicit legal control over their voice and visual likeness.

For voice artists and performers, digital cloning means a single recording session can be scraped once and endlessly reused by software without further consent or payment. For everyday individuals, it opens the door to identity theft, harassment, and public misrepresentation.

Losing control over our creative style and personal likeness is deeply concerning; even more troubling is when hidden algorithms make automated, biased choices about our actual lives.

The Invisible Mirror: Algorithmic Bias and Real-World Impact

Artificial intelligence does not think or feel on its own; it learns by analyzing human data. If the data fed into an AI system contains historical unfairness, societal prejudice, or narrow representations of certain groups, the AI learns those exact patterns. When deployed, the software acts as an "invisible mirror," reflecting and amplifying human bias under the guise of neutral mathematical logic.

When algorithmic bias goes unchecked, it causes real-world harm across everyday society:

1. Applicant Tracking Systems (Employment): Automated hiring software trained on historical corporate resume data has been shown to discriminate based on gender, penalizing job candidates whose resumes include female-associated terms or institutions because historical tech hiring skewed heavily male.

2. Healthcare Diagnostic Tools (Medicine): Clinical decision models trained primarily on medical data from majority demographic groups return lower diagnostic accuracy for historically underserved populations, leading to misdiagnoses or inadequate treatment recommendations.

3. Predictive Policing Tools (Justice): Law enforcement algorithms trained on historical arrest statistics risk disproportionately targeting systemically marginalized communities, creating a self-fulfilling feedback loop that over-polices specific neighborhoods regardless of actual individual behavior.

Understanding how algorithms can reflect our past mistakes is the first step toward taking control of our digital future.

Reader’s Empowerment Guide: Spotting Signs & Taking Action

You don't need a degree in computer science to spot the presence of AI risks in your daily life. Use this simple two-section checklist to evaluate online media and take practical steps to protect human creativity and fairness.

Section A: Signs to Spot

• Generic 'In the Style of' Content: Artwork, illustrations, or music tracks that copy a specific living artist's distinctive style without citing or linking to the human creator.

• Unnatural Audio or Visual Glitches: Subtle unnatural lip movements, robotic cadence changes, or strange audio artifacts in video clips that might indicate a cloned voice or digital replica.

• Unexplained Automated Decisions: Receiving an instant rejection on a job application, loan request, or service evaluation without clear, understandable reasons or human review options.

Section B: Practical Mitigation Strategies

• Support Human Creators: Actively seek out, buy, and subscribe to original books, news publications, music, and artwork directly from human creators and artists. Don’t read this blog! Read something else!

• Verify Information Sources: Cross-check surprising, controversial, or striking digital images and voice recordings against established, primary news outlets before sharing them.

• Demand Organizational Transparency: Support platforms, institutions, and businesses that clearly label AI-generated content and publish ethical AI governance practices.

• Exercise Privacy Options: Utilize privacy controls on websites and social media platforms to opt out of having your personal posts, images, and data scraped for public model training.

In this first post, we've explored how AI touches our creative expressions, our individual identities, and our rights to fair treatment. But what happens when these powerful tools are turned directly toward our wallets, our private data, and our jobs? Join us in Part 2: Digital Safety, Deepfakes, and Data: Protecting Your Identity and Wallet , where we will unpack online scams, data scraping, workplace shifts, and how to build your personal cyber-detective toolkit!

Who's Real Online? How Web3 Identity Protects Humans and Empowers AI Agents in Digital Commerce

 In a nutshell (TL;DR)...

• The Internet's Identity Crisis: AI advances make distinguishing humans from automated bots increasingly difficult, enabling Sybil attacks and credential abuse in digital commerce.

• Proof of Personhood: Web3 uses privacy-preserving biometrics and Zero-Knowledge Proofs (ZKPs) to verify unique human identity without revealing personal data.

• Digital Passports for AI: Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs) grant AI agents auditable, cryptographic permissions instead of vulnerable shared API keys.

• Mutual Trust in Action: Autonomous agents conduct secure transactions through mutual authentication, machine-readable trust lists, and scoped one-time mandates.

The Internet's "Identity Crisis" in the Age of AI

OK I know, but better late than never eh? Last week I looked into how we can trust agentic software to take a more independent role and the technologies put into place to ensure that. But, as artificial intelligence rapidly advances, distinguishing between a real human user and an autonomous software bot is becoming increasingly difficult. This poses a major threat to digital commerce and online communities:

• The Sybil Attack Problem: Named after a psychological study on multiple personalities, a "Sybil attack" occurs when a single bad actor creates thousands of fake online accounts to exploit systems designed for real individuals. In Web3, malicious bot farms routinely drain free token distributions, manipulate community voting, and hoard limited-edition event tickets before genuine users can connect.

• The "Shared Secret" Vulnerability: Historically, software programs have authenticated themselves across corporate systems using static API keys or shared passwords. If multiple AI agents share the same API key, security logs cannot tell which specific agent performed an action. If that key is stolen or intercepted, attackers can impersonate legitimate AI agents at machine speed.

To build a safe agentic economy, where AI agents buy products, book travel, and manage services on our behalf, we need a modern digital identity layer that protects human rights while giving software agents verifiable digital passports.

Proof of Personhood: Proving You're Human Without Sacrificing Privacy

When an online service or merchant wants to grant special rewards, discount codes, or voting rights to real people, it needs a way to confirm that each participant is a unique human being rather than an automated bot farm.

This design goal is known as Proof of Personhood, a cryptographic guarantee that a digital credential belongs to exactly one living human.

• How Biometrics Meet Privacy: Systems like Worldcoin (using iris scans) and Humanity Protocol (using infrared palm-vein scanning) verify physical uniqueness. Because palm vein patterns and iris textures are statistically unique, they prevent a single user from signing up thousands of times.

• Zero-Knowledge Proofs (ZKPs): To prevent these systems from turning into invasive surveillance databases, they use Zero-Knowledge Proofs. A ZKP is a mathematical tool that allows a user's digital wallet to prove the statement "I am a verified, unique human" to an online merchant without revealing their name, home address, or underlying biometric scan.

Digital Passports for Software: Verifiable Credentials for AI Agents

While humans need to prove their uniqueness, AI agents need a way to prove who built them, who owns them, and what specific authority they hold.

Instead of relying on easily stolen API keys, Web3 identity frameworks issue Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs) directly to software agents:

• What is a Verifiable Credential? Think of a VC as a cryptographically signed, tamper-evident digital certificate. It is signed by an issuing authority (like a bank, a government agency, or a corporation). Anyone who inspects the credential can instantly verify who issued it and confirm that the data inside has not been altered or forged.

• Identity Binding: Giving an AI agent its own distinct cryptographic keypair binds its actions directly to its owner's digital signature. This creates an auditable chain of command so businesses always know which agent initiated a purchase or database query.

Mutual Trust in Action: How Buyer and Seller Agents Do Business

Imagine asking your personal AI assistant to book a multi-city vacation for under $1,500. Your AI agent must interact with airline agents, hotel bots, and payment processors across companies it has never interacted with before. Web3 identity standards allow these autonomous systems to negotiate safely through a three-step handshake:

Step A: Mutual Authentication ("Show Me Your ID")

Before any sensitive personal details or credit card information are shared, the buyer agent and seller agent verify each other's credentials. The buyer agent verifies that the airline bot actually holds a private key signed by an accredited airline brand. As security researchers note: "You can spoof a website or an agent's text output, but you cannot fake an organization's private cryptographic key".

Step B: Machine-Readable Trust Lists

How does your AI agent know if a new merchant is legitimate? Web3 identity relies on machine-readable trust lists—published, cached files listing approved merchants, banks, and identity issuers. Your AI agent automatically checks this list on first contact to confirm the merchant has been vetted, eliminating the need for manual, hand-built integrations.

Step C: One-Time Delegated Mandates

To execute the actual purchase, you don't give your AI agent unrestricted access to your entire bank account. Instead, your device generates a scoped, one-time payment mandate (a feature standardized in payment frameworks like Google's AP2 and W3C standards).

This digital mandate explicitly states: "Authorized to spend up to $1,500 with Flight Vendor X for Transaction Y". If a malicious actor intercepts this message, the mandate cannot be replayed or redirected to buy a different product or pay a different merchant. Furthermore, using protocols like DIDComm, the cryptographic authority to sign these mandates can stay safely stored inside a digital wallet on your personal smartphone rather than sitting exposed on a cloud server.

Summary: A Transparent, High-Trust Internet

Web3 identity technology solves the fundamental trust gap in digital commerce. By combining Proof of Personhood to shield human systems from bot fraud with Verifiable Credentials to give AI agents cryptographically bounded spending authority, Web3 creates an open, secure environment where software can safely pay software on behalf of real people.

Next week I’ll take a look at on how AI agents can improve DAO governance and community decision-making…..

Beyond the Black Box: How We Can Actually Trust AI Agents with Real Money and Private Data

 

In a nutshell (TL;DR)...

As AI agents take on autonomous real-world actions, trusting them requires moving from unexplainable "black box" logic to verifiable auditability. By combining zero-knowledge proofs (zkML) for computational integrity, hardware enclaves (TEEs) for data privacy, and smart contract guardrails with strict spending limits, Web3 technologies provide a robust, layered defense to make AI-driven commerce safe and transparent.

The "Black Box" Problem in Everyday Life

Last week I looked at how Web3 technology can open the door to even more agentic independence with Agentic Commerce solutions. So, as artificial intelligence transitions from simple chatbots into autonomous agents capable of making purchases, managing investments, and handling private documents on our behalf, a major question arises: How can we actually trust software when even its creators cannot always explain how it reaches a decision?

Advanced AI models, such as deep neural networks, are often described as "black boxes" because their internal calculations involve billions of variables interacting simultaneously. If an AI agent approves or denies a loan, orders manufacturing inventory, or books an expensive vacation, traditional computer logging cannot show a simple line-by-line decision trail.

However, regulators and financial security experts emphasize a crucial distinction between explainability and auditability:

• Explainability asks why an AI model made a specific prediction.

• Auditability asks for proof: Can we mathematically prove which model version made the decision, what exact data it used, and that no one altered the results or tampered with the record after the fact?

While making an AI's internal reasoning fully transparent remains difficult, Web3 technologies and specialized hardware offer a tamper-evident audit trail that makes autonomous AI commerce safe and verifiable in the real world.

1. Mathematical "Receipts" (zkML) and Digital Safe-Deposit Boxes (Hardware Enclaves)

If you hire a third-party AI service to analyze your private company tax records or evaluate medical data, two immediate risks emerge: How do you know the provider ran the genuine, high-quality AI model rather than a cheap, inaccurate substitute? And how do you ensure your sensitive data isn't leaked or stored on a server?

To solve this, developers combine two breakthrough technologies:

• Zero-Knowledge Machine Learning (zkML): Think of zkML as a cryptographic "proof of work done right". By running the AI's calculations through zero-knowledge mathematical circuits, the system generates a lightweight digital proof alongside the output. This proof guarantees to any user or auditor that the exact requested AI model was executed correctly on the input data, without revealing proprietary model weights or exposing private information.

• Trusted Execution Environments (TEEs) & Confidential Computing: Imagine a digital safe-deposit box built directly inside a high-performance computer chip (such as NVIDIA’s Hopper H100 GPUs). The data processing happens inside an encrypted memory vault where even the owner of the physical computer server room cannot view or extract the data being processed.

Decentralized platforms (like Super Protocol) combine these hardware "safe-deposit boxes" with blockchain smart contracts. This allows an AI developer to lease a base model, fine-tune it with private company data inside an encrypted hardware vault, and deploy a secure AI service without risking data leaks or centralized server breaches.

2. Protecting AI Agents from Scams and Hacks in the Real World

In an agent-driven web, software programs will routinely negotiate and transact with other software programs across different companies. This creates new real-world security challenges that do not exist in traditional human shopping:

• Prompt Injection (Hidden Trick Commands): A rogue website or fake news article might hide invisible text designed to trick an AI shopping agent into buying a fake product or transferring money to a scammer's wallet.

• Evaluator Collusion: In automated commerce protocols (like EIP-8183), when a buyer agent hires a seller agent, a third "evaluator" agent inspects the finished work before releasing escrowed funds. If a seller agent secretly colludes with or bribes a rogue evaluator agent, the escrow could be drained even if the work was inferior or fraudulent.

3. The Layered Defense: How the System Stays Safe

To protect everyday users and businesses from these real-world risks, modern agentic security frameworks rely on a layered defense architecture:

1. Automated Spending Limits (Policy Engines): Rather than giving an AI agent unrestricted access to a bank account or wallet, developers use smart agent wallets equipped with strict spending rules. An agent might be authorized to spend a maximum of $50 per day or only interact with pre-approved merchant contracts.

2. Neutral, Bonded Reviewers: To prevent evaluator fraud, systems require evaluators to stake financial collateral (reputation capital or tokens) that gets automatically forfeited ("slashed") if audit monitoring detects suspicious approval patterns.

3. Immutable On-Chain Paper Trails: Every purchase, contract agreement, and cryptographic proof is recorded on a public or shared blockchain ledger. This creates a permanent, regulator-ready paper trail so that if an unauthorized transaction or error occurs, auditors can trace the exact chain of events back to its source.

Summary: Trust Through Verification, Not Faith

We don't need to unravel the mysterious internal math of deep neural networks to safely use AI in the real world. By surrounding autonomous AI agents with zero-knowledge proofs, hardware-encrypted memory vaults, and smart contract guardrails, Web3 infrastructure provides the mathematical verifiability required to turn AI agents into safe, accountable partners in digital commerce.

Next week lets turn our attention to exploring Proof of Personhood, biometric privacy, and distinguishing humans from bots. Exciting stuff...

The Machine-Native Economy: How Web3 Gives AI Agents Their Own Identities and Wallets

In a nutshell (TL;DR)...

TL;DR: AI agents require a machine-native financial and identity layer powered by Web3 to move beyond digital sandboxes and operate autonomously. This emerging machine economy relies on key standards: EIP-8004 for verifiable agent identity and smart wallets, EIP-8183 for structured hire-deliver-settle escrow agreements, and x402 for sub-cent, instant HTTP micropayments.

It’s another late post, sorry! I have a day job which gets in the way! I was approached recently by a company asking if I wanted a job which sounded incredibly interesting. All about developing AI systems in a Web3 architecture, and it struck me how utterly unqualified I am for that whole scenario. So I am determined to understand what Web3 is (I have dabbled with Crypto Wallets and NFTs) and how it might fit with the rise of AI, especially Agentic Commerce which is a lot closer aligned with my pesky day job…..

The Bottleneck in the AI Revolution

Artificial intelligence is undergoing a fundamental transformation. AI is moving beyond simple conversational chatbots toward autonomous agentic systems, software that can perceive its environment, formulate multi-step plans, and execute complex goals with minimal human supervision.
Yet, despite these cognitive leaps, today’s AI agents remain fundamentally trapped in a digital "sandbox". An agent can write code, analyze financial markets, or plan a detailed vacation itinerary, but it cannot independently buy software, rent computer server space, or hire another specialized AI tool without a human stepping in to provide a credit card or an API access key.
The core issue is that our legacy legal and financial infrastructure was built strictly for human beings. Opening a bank account or holding a credit card requires government-issued identity documents, physical addresses, and manual signatures. Furthermore, legacy credit cards charge high baseline transaction fees (often $0.30 plus 2–3% per swipe). This fee structure makes it economically impossible for an AI agent to execute high-frequency, sub-cent micropayments, such as paying $0.001 for a single second of computer processing power or a single data query.
As institutional researchers at BlackRock and Franklin Templeton point out, AI represents machine-native intelligence, and it requires machine-native money, a programmable, permissionless financial layer built on Web3. By integrating three emerging Web3 technical standards, developers are building an open machine economy where AI agents can operate as sovereign economic actors.

1. Giving AI a Digital Identity and Wallet (EIP-8004 & Smart Wallets)

For an AI model to operate independently, it must first be able to prove who it is, establish a verifiable track record, and hold digital assets safely.

EIP-8004 (The Agent’s Digital Passport): In traditional cloud environments, an AI is just an anonymous script running inside a corporate server. The EIP-8004 standard changes this by issuing the AI a unique, portable identity anchored on the blockchain. This standard consists of an Identity Registry (which functions as a global passport listing the agent's capabilities and its cryptographically linked wallet address), a Reputation Registry (a permanent, tamper-evident audit trail of past job performance), and a Validation Registry (which allows independent auditors or mathematical proofs to verify the accuracy of the agent's work).

Smart Agent Wallets (Account Abstraction): Traditional crypto wallets require a human to manually review and approve every single signature. AI agent wallets utilize Account Abstraction (ERC-4337) and automated policy engines to allow 24/7 autonomous operations within strict safety boundaries. Developers can program explicit risk controls directly into the wallet—such as daily spending limits, whitelisted addresses, and automatic circuit breakers that pause operations if anomalous activity is detected.

2. The "Hire-Deliver-Settle" Handshake (EIP-8183)

Once an AI agent has a verifiable identity and a smart wallet, how does it safely conduct business with another software agent or service it has never interacted with before?

EIP-8183 (The Agentic Commerce Protocol) solves this by establishing a state-machine-driven escrow agreement. Instead of relying on trust or traditional legal contracts, EIP-8183 organizes commercial tasks into a structured, three-party workflow:

1. The Client (the human or AI hiring for a task) defines the job parameters and locks the required payment into a smart contract escrow.
2. The Provider (the AI performing the work) executes the task and submits the completed deliverable.
3. The Evaluator (a neutral arbiter, such as an automated zero-knowledge proof, a trusted hardware enclave, or a specialized reviewer agent) inspects the deliverable.

If the Evaluator confirms the deliverable meets the agreed specifications, the smart contract automatically releases the escrowed funds to the Provider. If the task is rejected or times out, the escrowed funds are automatically returned to the Client. This eliminates counterparty risk without requiring human court systems.

3. Software Paying Software at Machine Speed (x402 Micropayments)

In a fully automated economy, software agents do not negotiate monthly invoices; they purchase resources on demand, paying per API request, per data query, or per second of compute time.

x402 (The Native Machine Payment Rail): Developed as an open standard, x402 revives the long-dormant web status code "HTTP 402: Payment Required". When an AI agent requests data or processing power from a web service, the server responds with a 402 status code containing a digital price tag (such as $0.001 in stablecoins). The AI agent’s wallet automatically signs a sub-cent payment payload, the server validates the authorization instantaneously, and the requested resource is delivered in milliseconds.

By bypassing traditional payment processors, x402 allows software to pay software instantly without requiring pre-existing billing accounts, recurring monthly subscriptions, or manual human approval.

The Big Picture: A Continuous Machine Economy

When these three standards converge, they create a complete, self-sustaining feedback loop: Discovery > Transaction > Payment > Reputation.

Consider a practical example: A primary AI assistant tasked with booking complex travel can locate a specialized weather-analysis AI, verify its on-chain EIP-8004 reputation score, lock job funds in an EIP-8183 escrow contract, pay sub-cent x402 fees to access real-time satellite data feeds, and finalize the booking. Once the task is validated, the escrow releases payment to the sub-agent, and both agents' reputation scores automatically update on-chain.

By replacing centralized gatekeepers and high-fee legacy rails with Web3 protocols, Web3 technology moves artificial intelligence out of passive isolation and into a sovereign, global, machine-native economy.

Next week I will focus on zero-knowledge security, hardware enclaves, and threat defenses - whatever that means!

The Fraud Paradox: Why Legacy Security is Killing Agentic Commerce (And How KYA Fixes It)

In a nutshell (TL;DR)...

Legacy fraud detection systems often block legitimate AI agents, mistaking them for malicious bots. "Know Your Agent" (KYA) solves this by verifying AI identity via Cryptographic Agent Passports, setting Delegated Spend Mandates to control agent scope, and using machine-readable risk scoring. Adopting KYA allows merchants to safely embrace the growing automated commerce economy.

This week I am on vacation in Italy and on my short flight I started worrying about how easy it might be to get scammed in this new agentic commerce world. What kind of protection do we have? How do merchants know that your transaction is legitimate?.

Picture this scenario: An AI agent attempts to execute a valid $150 transaction for an automated grocery restock. It requests the product payload via API, validates the cart token in 12 milliseconds, and sends a payment request.

To a legacy fraud engine, this rapid-fire, non-human interaction looks like a brute-force bot attack or a credential-stuffing attempt. The system immediately triggers a Cloudflare CAPTCHA or rejects the payment card outright.

Result? A legitimate customer gets turned away, a merchant loses a sale, and the AI agent hits a brick wall.

As AI agents transition from simple recommendation engines to fully autonomous economic actors, the retail industry is running headfirst into a massive security challenge: How do you stop malicious scrapers and scalper bots without blocking legitimate AI buyers?

The Death of Human-Centric Fraud Detection

For two decades, e-commerce fraud prevention relied on evaluating human behavioral signals:

• How long did the user linger on the product page?

• Is the mouse cursor moving in natural, imperfect arcs?

• How fast is the user typing their credit card details?

• Can the visitor identify all the crosswalks in a 3x3 image grid?

In an agentic economy, every single one of these assumptions breaks.

Autonomous agents don't move mice, linger on product images, or solve CAPTCHAs. They execute headless transactions at machine speeds. If risk management platforms treat all non-human traffic as hostile, they risk locking out the fastest-growing customer segment in digital commerce.

Enter Know Your Agent (KYA)

To solve this trust gap, identity verification providers (including Experian, Trulioo, and Entrust) are pioneering a new compliance and governance standard: Know Your Agent (KYA).

Just as Know Your Customer (KYC) revolutionized banking by verifying human identities, KYA creates an infrastructure to verify non-human actors and establish their operational authority.

        THE KYA TRUST TRIAD
               
      +-------------------+
      |   VERIFIED HUMAN  |
      |  (Account Owner)  |
      +-------------------+
                |
  Delegated     |     Cryptographic
  Mandate       |     Binding
                v
      +-------------------+
      |  AUTHENTICATED AI |
      |   (Digital Agent) |
      +-------------------+
                |
  Authorized    |     Scoped
  Intent        |     Limits
                v
      +-------------------+
      |  TRANSACTION DATA |
      | (Cart & Merchant) |
      +-------------------+

Instead of evaluating how a page was navigated, a KYA-compliant merchant system evaluates the Trust Triad:

1. The Human (Identity): Is this agent bound to a real, verified individual or organization?
2. The Agent (Passport): Does the agent present a valid, tamper-proof credential (a Digital Agent Passport) issued by a trusted entity?
3. The Intent (Authorization): Has the human owner explicitly granted this agent a delegated mandate to spend up to a specific dollar amount for a specific category?

3 Core Components of the KYA Stack

When an AI agent checks out at a modern merchant platform, three security mechanics validate the order behind the scenes:

1. Cryptographic Agent Passports

Instead of exposing raw API keys or static credentials, agents carry a Digital Agent Passport (DAP) or cryptographic token signed by an identity registry. When requesting a checkout endpoint, the agent presents this token, immediately proving its publisher (e.g., OpenAI, Google, Anthropic) and its active verification status.

2. Delegated Spend Mandates

To limit blast radius if an agent is compromised or subjected to prompt injection attacks, KYA enforces strict scope boundaries. A user might grant an agent a tokenized spend mandate: "You are authorized to spend up to $200 on running shoes before midnight on Friday." If the agent attempts to purchase a $1,000 television, the transaction fails at the gateway level regardless of payment card limits.

3. Machine-Readable Risk Scoring

Rather than looking for device fingerprints or browser headers, next-gen fraud models evaluate machine-native signals:

• Has this agent's digital passport been revoked?
• Is the merchant endpoint receiving requests consistent with the agent's stated policy parameters?
• Is the transaction origin signed by a verified enclave or zero-knowledge proof?

The Strategic Choice for Merchants

E-commerce brands face a clear strategic fork in the road:

• Path A (The Defensiveness Trap): Double down on legacy bot detection, block headless browsers, enforce aggressive CAPTCHAs, and inadvertently shut out millions of dollars in automated customer orders.
• Path B (The KYA Highway): Implement agent-friendly APIs with clear authentication endpoints, accept cryptographic agent passports, and capture market share in an increasingly automated retail landscape.

The future of digital commerce isn't about choosing between security and automation. It's about establishing a verified layer of identity where humans, agents, and merchants can trade with absolute trust.