← Back to the Muse connector directory

The Personal Agent Protocol and PACT, Explained

Published October 6, 2026. This is a fast-moving story. Details below show what's confirmed as of announcement day.

Updated October 9, 2026: full company roster, FAQ, and adoption tracking.

On October 6, 2026, Meta and Sierra published the Personal Agent Protocol, an open standard for how personal AI agents deal with businesses. Days earlier, Decagon announced PACT, the Personal Agent Consent & Trust protocol, at its Dialogues event. Both announcements circle the same question: when your AI agent talks to a company for you, how does the company know who's behind it, and what that agent may do?

Here's what each protocol is, how they work, and what they mean if you connect apps to a personal agent like Meta's Muse.

What was announced

The Personal Agent Protocol sets out how personal AI agents interact with businesses. The problem it takes on: right now a business can't reliably tell whether it's dealing with a personal agent acting for a real customer or some random bot. The protocol gives businesses one consistent way to recognize personal agents and handle them. It uses OAuth-style sessions. You stay in control, choosing read access, write access, or nothing for the agent. The agent never sees your raw credentials.

PACT (Personal Agent Consent & Trust) comes from Decagon and approaches the same problem through consent. It builds on the Agent2Agent protocol, which covers how agents find each other and trade messages, and adds delegated authorization on top of OAuth 2.0. In plain terms, that's a signed, verifiable token proving this agent represents this person, and this person approved these specific actions. When your agent meets a business's agent, the business checks the token instead of guessing.

Who's behind it

Sierra leads the Personal Agent Protocol with Meta. Sierra is the enterprise AI company Bret Taylor co-founded after co-running Salesforce; Taylor also chairs OpenAI's board. Launch partners named in Sierra's announcement: Genesys, Instinct, Rocket, Shopify, Stripe, and Walmart. Taylor put the motivation bluntly to CNBC: "Companies will know when it's a personal agent versus an actual person… It is kind of chaos until such a standard exists."

PACT comes from Decagon, which builds AI customer-service agents for enterprises. Decagon introduced it alongside its Personal Agent Gateway, a product that spots personal agents contacting a business over chat and voice, then routes them to a dedicated channel run under separate procedures. Decagon says the PACT specification is published and that it's refining it with personal agent providers and enterprise customers.

Every company involved

Sierra's announcement graphic names 43 companies, grouped in three tiers. The graphic does not spell out what each tier signifies, so the groupings below follow the announcement as shown.

Protocol leads

  • Meta. Runs the Muse personal agent. Co-developing the standard with Sierra. David Singleton, VP of Meta Superintelligence Labs, compared the standard to email. Meta's company blog: "Turning away a personal agent means turning away the customer behind it."
  • Sierra. Enterprise conversational AI company co-founded by Bret Taylor and Clay Bavor. Taylor also chairs OpenAI's board. Sierra authored the announcement and will publish the v0.1 spec later in October, host design workshops, and ship a reference implementation. Taylor told CNBC: "It is kind of chaos until such a standard exists."
  • Genesys. Contact-center and customer-experience cloud platform. CEO Tony Bates: "Brands need a trusted way to know who an AI agent represents, what it's authorized to do." He called it the "new front door to the enterprise."
  • Instinct. Personal AI assistant app.
  • Rocket. Rocket Companies, mortgage and homeownership (Rocket Mortgage, Redfin). CTO Shawn Malhotra: Rocket and Redfin built agentic technology with Sierra that lets a Muse agent work across Rocket's platform.
  • Shopify. E-commerce platform. Mani Fazeli, VP Product: the protocol "helps establish how agents and merchants can work together."
  • Stripe. Payments infrastructure. Kevin Miller, Head of Payments: "We're contributing to the Personal Agent Protocol to give businesses a standard way to recognize their customers' agents."
  • Walmart. The world's largest retailer.

Enterprise brands

  • Bank of America. Banking.
  • BBVA. Banking.
  • Chime. Digital banking.
  • Cigna. Health insurance.
  • Comcast. Telecom and media.
  • DirecTV. Satellite TV.
  • Fox. Media.
  • Gap Inc. Apparel retail.
  • Geico. Auto insurance.
  • Hertz. Car rental.
  • Insurify. AI insurance comparison, early design partner. Co-founder and co-CEO Giorgos Zacharia called the protocol's potential impact "as transformative as the internet itself."
  • Liberty Mutual. Insurance.
  • Mastercard. Payments network.
  • Nordstrom. Department store retail.
  • PayPal. Digital payments.
  • SiriusXM. Satellite radio.
  • Synchrony. Consumer financial services.
  • Target. Retail.
  • United. United Airlines.
  • Venmo. Peer-to-peer payments.
  • Visa. Payments network.
  • Wells Fargo. Banking.

Technology and ecosystem

  • 1Password. Password management.
  • Adyen. Payments platform.
  • Atomic. Payroll and employment data APIs.
  • Cloudflare. Internet infrastructure and security.
  • ElevenLabs. AI voice and audio.
  • Klaviyo. Marketing automation.
  • Notion. Productivity software.
  • Okta. Identity management.
  • OpenAI. AI lab behind ChatGPT.
  • OneSignal. Push notification and messaging platform.
  • Plaid. Financial data connectivity.
  • Zapier. Workflow automation.
  • Zendesk. Customer support software.

Two names from Meta's own partner posts, NiCE and Decagon, do not appear in Sierra's graphic. Decagon separately open-sourced PACT (Personal Agent Consent and Trust) and joined the protocol working group.

What skeptics are asking

Three open questions around AI agent shopping and AI agent spending limits.

  • Trust gap: In a September 2026 survey of 1,392 consumers across 7 countries, 78% were open to AI helping them shop, but only 5% were comfortable with an agent purchasing on its own. 32% wanted the agent to propose and wait for approval. (Cover Genius and Gather)
  • Identity is not mandate: a widely shared technical objection holds that verifying an agent's identity answers "is this agent allowed to act" but not "is this specific action within what the person approved."
  • Retry risk: purchases are hard to undo, and the most dangerous agent failure is a retry after an ambiguous timeout, which can double-charge. Technical commenters call for idempotency keys and spend ceilings built into the protocol itself.

How it works

Two mechanisms, in plain terms.

Sessions (Personal Agent Protocol). Picture signing into an app with Google, except it's your agent signing in. When your personal agent contacts a business, it opens a session identifying itself as your agent, acting for a verified customer. You set the session's scope: read-only for looking up an order status, write for changing a booking, or nothing at all. The session carries a grant of permission. Your passwords and payment details stay out of the agent's hands entirely.

Delegation tokens (PACT). Say your agent needs to work directly with a business's own agent, like your travel agent negotiating with an airline's support agent. PACT supplies a verifiable token that travels with the request. The token certifies which person the agent represents and exactly what that person authorized. Decagon's own example: a traveler lets their personal agent view flights but not rebook them. The airline's agent shares earlier flight options. It can't complete the change until the traveler approves rebooking. Permission sits in the token.

In both designs the person grants permission up front, and the business verifies a token before acting on it.

What it means for Muse connector permissions

This should sound familiar if you use Meta's Muse. Muse connectors already work on the same principles: OAuth-style connections, read-versus-write control per app, approval prompts before sensitive actions, credentials held in a secure store the agent can't read directly. Check the full list of Meta Muse connectors to see how each one is permissioned today.

These protocols stretch that model past the apps you've explicitly connected, out to every business your agent might contact. That matters because of what agents do today with no connector in place. Muse often drives a website in a browser, clicking around the way a person would. It's the most fragile way to connect. It's also the traffic Amazon blocked in September, citing scraping concerns. In a world where businesses adopt the Personal Agent Protocol, your agent identifies itself properly at checkout instead of tripping bot defenses. Connectors stop being per-app workarounds and turn into standard handshakes.

What v0.1 won't cover

  • No universal adoption. This is a shared proposal. Nobody has to follow it. Amazon, the highest-profile agent blocker, isn't part of either effort.
  • The specs are still moving. Decagon says the PACT specification is available and under refinement with partners. Expect details to shift before anything is final.
  • Nobody has described enforcement. Nothing compels a business to implement either protocol, or an agent provider to support them.
  • The hard edge cases stay open. Nobody has said what happens when the person can't be reached for approval mid-task. Token expiry, revocation, dispute resolution: none of that is public yet.

Why it matters

Personal agents went mainstream in about a month. Muse topped app store charts within days of launch. Businesses suddenly field support requests from software. Until now, almost every one of those interactions has been improvised. Agents drive browsers while posing as humans. On the other end, businesses guess who's calling. Anti-bot systems usually block first and ask questions later.

The Personal Agent Protocol and PACT are the first serious attempts at real infrastructure for this. They give agents a way to prove identity and attach the person's consent in machine-checkable form. If these stick, a new list starts to matter: which businesses speak the protocol. We'll track adoption here as it happens.

Personal Agent Protocol FAQ

Plain-language answers on the personal agent protocol, agentic commerce, and AI agent shopping. Covers how a Muse agent checks out and where Amazon blocks Muse traffic.

What is the Personal Agent Protocol?

An open standard co-developed by Sierra and Meta, announced October 6, 2026. It defines how a person's AI agent signs in to a business and gets tasks done there: authentication, permissions, and business-side visibility. It is built on OAuth. The v0.1 spec is expected later in October 2026.

Which companies are involved in the Personal Agent Protocol?

Sierra's announcement graphic names 43 companies: 8 protocol leads (Meta, Sierra, Genesys, Instinct, Rocket, Shopify, Stripe, Walmart), 22 enterprise brands including Bank of America, Visa, Mastercard, PayPal, Target, and United, and 13 technology companies including OpenAI, Cloudflare, Okta, Plaid, and Zendesk. Insurify joined as an early design partner around October 8.

How does the Personal Agent Protocol work?

An agent first arrives as a guest and can check things like stock or return policies. After the customer signs in through OAuth, the agent gets read-only or write access based on the permissions granted. The session carries across channels as one visit. The business chooses the entry point: its website, its APIs, or its own agent.

Does the Personal Agent Protocol handle payments?

Not in v0.1. Payments, finer-grained permissions, and push notifications are flagged as future extensions. Payment handling stays on existing financial rails for now.

Why was the Personal Agent Protocol created?

Businesses are blocking agent traffic. Amazon deliberately blocked Meta's Muse agent in September 2026 over identity and credential concerns. Blocks have also been documented across Delta, United, Zillow, Yelp, and eBay. Meta's position: turning away a personal agent means turning away the customer behind it.

Does the Personal Agent Protocol replace checkout?

No. It standardizes how an agent authenticates and what it may do. It does not replace checkout flows or payment rails.

How is the Personal Agent Protocol different from MCP?

MCP (Anthropic's Model Context Protocol) standardizes how an AI model calls tools and data sources. The Personal Agent Protocol standardizes how a personal agent authenticates to a business and proves delegated authority. Sierra's announcement names MCP as one of the API standards a business can expose. They are complementary.

How is the Personal Agent Protocol different from A2A?

Google's Agent-to-Agent protocol governs how agents talk to each other. The Personal Agent Protocol governs the personal-agent-to-business relationship: sign-in, permission tiers, and business visibility. Different layer.

What is the Agentic Commerce Protocol (ACP)?

ACP, co-developed by Stripe and OpenAI, focuses on completing purchases inside a chat experience. The Personal Agent Protocol v0.1 excludes payments, so they currently sit in different lanes. Stripe participates in both.

Who is liable when an AI agent makes a wrong purchase?

Unresolved. In a Q1 2026 Riskified survey, 50.8% of consumers said the AI platform should be responsible for unauthorized AI-driven purchases. The protocol announcement does not address liability.

Is the Personal Agent Protocol really open?

Sierra and Meta call it an open standard anyone can implement. As of October 9, no license or governing body has been named. Treat governance as to be determined.

What should businesses do to prepare for AI shopping agents?

Make pricing and policies machine-readable text, decide what agents may do alone versus with human approval, keep inventory data current, and test how AI agents currently experience the site.

Is ChatGPT an agent or LLM?

Both, depending on how you use it. ChatGPT is built on a large language model. When it answers questions in chat, it works as an LLM. When it uses tools, browses the web, runs code, or completes multi-step tasks like shopping, it acts as an agent. The Personal Agent Protocol is built for that second mode: when your agent leaves the chat and does things at real businesses.

Who are the big 4 AI agents?

There is no official ranking, but the four personal agents that dominate the conversation are Meta's Muse, ChatGPT, Claude, and Gemini. All four can now take actions on a user's behalf, which is why a shared standard for how they identify themselves to businesses matters.

What does 'personal agent' mean?

A personal agent is an AI that acts on your behalf. It is tied to you as an individual. It knows your accounts, your preferences, and your payment methods, and it takes actions in the world for you: booking, buying, scheduling, messaging. That is different from a general chatbot that only answers questions, and different from a company's support agent that serves the business. The Personal Agent Protocol exists because a personal agent needs a standard way to prove it represents you when it contacts a business.

What are the 7 types of AI agents?

There is no single standard list, but the categories most often cited are: simple reflex agents, model-based reflex agents, goal-based agents, utility-based agents, learning agents, hierarchical agents, and multi-agent systems. The personal agents covered by this protocol, like Muse and ChatGPT in agent mode, are typically goal-based or utility-based agents that learn from interaction.

What does Sierra AI actually do?

Sierra builds AI agents for customer service and customer experience. Businesses deploy Sierra's agents to handle support conversations across chat and voice. The company was co-founded by Bret Taylor and Clay Bavor, and Sierra co-developed the Personal Agent Protocol with Meta.

Is Sierra AI free?

No. Sierra is an enterprise product sold to businesses on contract pricing. It is not a free consumer app.

Who owns Sierra AI?

Sierra is a private company co-founded by Bret Taylor and Clay Bavor. Taylor previously served as co-CEO of Salesforce. Bavor previously led Google Labs and Google Workspace.

Where is Sierra AI headquartered?

San Francisco, California.

What do Sierra AI employees say about working there?

Public review volume is thin because Sierra is a young private company. Employee reviews appear on Glassdoor and Blind under the company name.

What is the salary range at Sierra AI?

Sierra does not publish company-wide bands. Current postings show wide ranges by role. In September 2026 listings, Enterprise Sales Director roles were posted at 240k to 305k dollars and 300k to 345k dollars per year, and one remote-jobs tracker put median base pay across Sierra's remote roles around 330k dollars. Ranges are disclosed per posting and vary by role and location.

Is Sierra AI hiring?

Yes. An October 2026 scrape of 45,000 career-page listings found Sierra had 75 open roles with "agent" in the title, more than any other company tracked, including OpenAI and Anthropic. Openings span sales, engineering, and agent development and are listed on Sierra's careers page.

What is the Sierra AI interview process like?

Sierra does not publish its interview process. Detailed candidate accounts appear in Reddit and Blind threads. Read recent threads there before interviewing, since the process changes as the company grows.

Why this matters for agent trust

The protocol answers whether an agent is allowed to act. The adjacent problem is knowing exactly who is calling: human, agent, and whose agent, before access is granted. That is what Valiron works on: trust infrastructure for AI agents at valiron.co. This page is built by the team behind Valiron.

Sources

Get your Muse connector readiness score
← Back to the Muse connector directory