← Back to the series

When AI acts in your name · 08

Your AI has agency. Your identity needs a rail.

Verified people, verified businesses, signed approvals, and shared rules, working as one network.

Your personal agent has an inbox, a browser, and a growing list of things it can do in your name.

Meta's Muse can fill out forms, arrange travel, and negotiate on your behalf. Meta says it seeks approval before sensitive actions such as purchases. Instinct is part of the same shift toward assistants that take care of tasks for you.

You can see the appeal. Get the refund. Book the appointment. Pay the bill. Handle the things you keep putting off.

You can also see where confidence starts to break.

Katie Jacobs Stanton reported that Instinct sent an email without checking with her first, prompting her to disconnect email access.

In a firsthand Reddit discussion, another user described setting up an agent for routine shopping, then reviewing every purchase anyway. Delegating research felt easy. Letting software spend money felt different.

These are individual accounts, but they expose the question every owner eventually faces: how much authority did I just give this thing?

An unwanted purchase is one problem. Now imagine an agent accepting a yearlong service agreement when you only wanted a quote. The provider says you owe twelve months of fees. You say you never agreed.

Depending on the circumstances, getting out of that dispute could mean hiring a lawyer or explaining the evidence to a judge. "My AI did it" is the beginning of that conversation, not the resolution.

You wanted help with your life. You didn't want a new legal problem.

Identity needs a rail.

An agent needs more than access to your accounts. The businesses it encounters need a way to establish who you are, what you authorized, and whether the request in front of them fits that authorization.

You need the same confidence in the other direction. Is that really your bank asking for information? Did that invoice come from the supplier you intended to pay? Is the company receiving your mortgage application who it claims to be?

This is why identity needs a rail: a network connecting verified humans and verified businesses. This gives companies and people common way to exchange and check evidence of what they have agreed to.

That is the identity authorization network we're building at Proof.

Our certificate authority provides the foundation for trusted digital identities, with published issuance policies and independently audited operations. Our business identity infrastructure brings KYB verification and organization certificates to the other side of the exchange. Businesses can sign the content and requests they send; people can verify whom they are dealing with before responding.

Both sides arrive with an identity the other can evaluate. The agent carries the exchange between them.

The record is what lets an agent’s work proceed.

Take that service agreement. The owner authorizes one appointment, at an agreed price, with a named provider. The business supplies its terms. The owner approves them through a trusted signing flow.

The result should be a verifiable record binding the owner, the business, the action, and the agreed terms. If an agent is involved, the record also identifies the agent and the limits of its authority.

Proof's transaction signing connects verified identity to specific terms. Delegate Authority extends that approach to an owner's permission for a named agent to act within a defined scope.

These records can travel through agents and intermediaries and be verified on receipt. A service can use the open x401 protocol to request the identity and authority evidence it requires before proceeding.

The agent cannot manufacture the owner's valid signature without access to the owner's protected signing key. If AI changes anything about the transaction, like the signed price,, and the altered terms fail verification against the original signature.

That gives each participant evidence it can use. The agent has limits to follow. The business checks that the request is authorized. A payment provider evaluates the relevant approval alongside its other controls. Each can retain the record of what it accepted and why.

The rules need facts. The facts need consequences.

A rule that says "only accept actions the owner authorized" needs evidence of that authorization. A rule that assigns responsibility when an agent exceeds its mandate needs evidence of the mandate and what the agent actually did. Verifiable records supply those facts.

Network operating rules define what participants must do with them.

  • Who checks the business?
  • Who verifies the owner's approval?
  • Who stops a request that exceeds it?
  • If a customer disputes the outcome, who receives the claim, produces the records, and resolves the disagreement?
  • Who bears the loss if a participant failed to perform its duties?

Those answers must be explicit before businesses rely on an identity network. They need to govern insurance applications, loans, prescriptions, signatures, and disclosures as well as payments. The duties differ by use case; the need for evidence and accountability runs through all of them.

A signed credential cannot allocate liability on its own. That requires agreed operating rules and enforceable commitments consistent with applicable law and consumer rights. This is part of the network vision, alongside the technology that lets participants establish whether those commitments were met.

Fraud defense belongs inside the network.

Even verified identities can be compromised. A valid credential is no reason to ignore a suspicious transaction.

Proof already has fraud monitoring built into its platform through Defend. It combines transaction context, deepfake detection and network signals to identify suspicious patterns and route activity for review in supported workflows.

That capability is essential in an identity authorization network. Verification establishes who is participating. Signed records establish what was approved. Fraud defenses help identify when something about the activity calls for intervention.

Those pieces need to work together while the transaction is happening, before a customer is left trying to recover their money or undo a commitment.

One identity for the things you agree to.

Our ambition is a universal credential for the commitments you make: paying, signing, applying, sharing information, and authorizing others to act. The same foundation should work when you are there yourself and when your agent is acting for you, with each recipient applying the requirements of the transaction.

The credential connects to a verified owner. The network connects that owner to verified businesses. Signed records carry their agreements. Operating rules define responsibilities and recourse. Defend brings fraud intelligence into the flow.

That's the identity authorization network. It's what lets a business accept an agent's request with more to rely on than the agent's word.

End of the series

Bring us a workflow. Leave with a map.

Tell us about one agentic workflow and a Proof representative will follow up to set a time. Booth #5069 · October 18–21, 2026 · Las Vegas

Book a meeting at Money20/20
← Back to the series