OpenAI dots for retailers: how ChatGPT's always-on agent signs in and buys from your store

Direct answer: Dots are OpenAI's always-on agents in ChatGPT. Each has its own cloud computer and browser, and OpenAI's help pages say a dot can buy from a store using a card the user has saved on that store's website, once the user approves the purchase. That makes your sign-in page and your customer account the front door for dot purchases, not only your guest checkout. There is no integration to build. The work is to let OpenAI's signed cloud browser through your bot defences, and to make sure a returning customer can sign in with a one-time code and pay with a saved card without hitting a challenge.

This guide is for ecommerce directors, heads of digital and engineering leads. It covers what dots are and who has one, how a dot reaches and pays at a store, how to recognise and allow its traffic, what we found on the sign-in pages of the 225 retailers in our Agent Commerce Index, and what to check first.

Last verified: 31 October 2026 against OpenAI's announcement, Help Center and ChatGPT Learn documentation, OpenAI's crawler page and Shopify's Help Center. Dots are rolling out gradually and OpenAI updates these pages often (one was updated on the day we read it), so check the current versions before you plan work.

What dots are and who has one

OpenAI introduced dots on 29 September 2026. The points that matter to a retailer:

• Each dot has its own computer and browser. OpenAI says dots "can do nearly anything using their own cloud computer, their own browser, and the apps you've connected", and keep working on the user's goals around the clock.
• Work first, shopping second. OpenAI's launch examples are work: fixing an app, revising a launch, updating a sales proposal. Buying is a capability rather than the headline. The Verge's hands-on review of 2 October was titled "OpenAI's Dot agent is enterprise software that can also order your dinner".
• It can buy. OpenAI's dots safety FAQ says: "Your dot can also make purchases using a card you've saved on a merchant's website. These purchases require your approval, which may be given in advance when it specifically covers the purchase."
• The user sets the rules. Users can set custom rules for what a dot can "share, purchase, or access", choosing between take action without asking, take action if pre-approved, ask before taking action, and hand off to the user. Built-in safeguards can't be switched off: changing a password or transferring money always goes back to the user.
• Who has one. OpenAI's Getting started page says dots are rolling out to Pro users aged 18 and over "in markets excluding the European Economic Area, Switzerland, and the UK", to Business Premium users in supported ChatGPT regions, and as a beta that Enterprise admins must switch on. The rollout is gradual.

The shopper's location matters, not yours. A UK or European store that sells to the US, Canada or Australia can already receive dot visits. Dots sit on premium and business plans, so our reading is that early users will mostly be professionals, buying for work as well as for themselves.

How a dot reaches and pays at a store

A dot reaches most stores the same way: in its own browser in the cloud. OpenAI's ChatGPT Learn page on computers and apps sets out what happens next.

Two things follow for a retailer.

Sign-in is the step most likely to stop a dot. The dot needs to be signed in to use a saved card, and sign-in pages are where many stores put their strictest defences against credential stuffing. A challenge tuned to stop automated logins can't tell a dot from an attacker unless it checks the signature OpenAI sends (see the next section). The Verge reported that a dot "got stuck in a looping security check" signing in to a large retailer's account, that a restaurant's ordering page "wouldn't allow Dot", and and that Dot "required more manual input and browser takeovers" than the Muse and Instinct agents it was compared with.

Without a saved card, the shopper finishes the payment. OpenAI's help pages tell users never to paste payment details into the conversation. The Verge found no equivalent of Muse's Link by Stripe integration with its one-time card: at one checkout, the dot asked the reviewer to enter bank details themselves. Compare our Claude Duet guide and Meta Muse guide: both of those agents pay with a one-time card and can buy as a guest. A dot, as documented today, buys best as your signed-in returning customer.

How a dot identifies itself

OpenAI's dot pages don't name a user agent for dots. They say a dot uses "the same private sign-in flow as ChatGPT Work", and the Getting started page talks about "its cloud browser". OpenAI documents how ChatGPT Work's cloud browser identifies itself on its allowlisting page:

• Signed requests. The cloud browser signs outbound requests with Web Bot Auth (the HTTP Message Signatures standard, RFC 9421). Each request carries Signature, Signature-Input and a Signature-Agent header set to "https://chatgpt.com". The public keys are at https://chatgpt.com/.well-known/http-message-signatures-directory.
• Cloudflare. Bot tag chatgpt-agent, detection ID 129220581 (listed in the dashboard as ChatGPT Operator). OpenAI's instructions are a WAF custom rule that allows or skips requests with that detection ID.
• Akamai. Bot name ChatGPT Agent in the Artificial Intelligence bots category.
• HUMAN. ChatGPT Agent under Known Bots & Crawlers.
• Vercel. No configuration needed; Vercel recognises the traffic as chatgpt-operator.
• Other CDNs and proxies. Verify the signature yourself, and make sure any proxy in front of your origin keeps all three signature headers.

Three cautions. First, OpenAI's dot pages don't state in so many words that a dot's browser signs every request this way. Our reading is that it is the same ChatGPT cloud browser, but confirm it in your own logs before you rely on it. Second, OpenAI's own pages disagree on one point: the HUMAN section of the allowlisting page, updated about 12 days before we read it, still says that "at launch, Cloud browser cannot sign in to websites or complete payments", while the newer cloud browser page and the dot pages describe both. Third, robots.txt is not the control. OpenAI's crawler page says that for ChatGPT-User, "because these actions are initiated by a user, robots.txt rules may not apply", and it lists no separate dot agent.

The cloud browser page is clear about who decides: "each website ultimately decides whether to allow cloud browser traffic." Our guide to Know Your Agent (KYA) for retailers explains how signed agent traffic can be verified and treated differently from anonymous automation.

What we found in the Index

On 31 October 2026 we visited the sign-in pages of the 225 scored retailers in our Agent Commerce Index. We used a standard headless Chrome browser from a data-centre IP address, with no signature, as a stand-in for an agent's cloud browser. We loaded each homepage, followed its account or sign-in link (or tried common account paths), and recorded what the first sign-in screen showed. We did not enter any details or sign in anywhere. We ran the scan twice, about ten minutes apart, and 224 of the 225 results matched. The figures below are from the second run.

Of the 182 sign-in pages we reached:

What it means:

• Most retailers' sign-in pages opened for a cloud browser. 182 of 225 showed our unsigned browser a sign-in form. 21 refused or challenged it at the homepage or the sign-in page, the same number in both runs. OpenAI's signed traffic may be treated differently, in either direction, so treat 21 as an indication rather than a count of stores that block dots.
• The one-time code is common. 80 stores used Shopify's passwordless customer accounts, where Shopify's Help Center says the customer enters an email address and receives a 6-digit code. OpenAI's private form is built for exactly that step: the user types the code and the dot carries on. Shopify adds that sessions persist for up to 365 days, which suits an agent that comes back.
• Captchas are mostly invisible until they aren't. 30 sign-in pages loaded a captcha script, but only 8 showed a widget on load. The rest score the visitor in the background, and a low score can trigger a challenge after the form is submitted, which is where an agent's attempt usually ends.

Two figures we have already published add context. In our Know Your Agent guide, Cloudflare headers appeared on 173 of the 225 homepages, so OpenAI's Cloudflare detection ID is the relevant setting for most of the Index. And in the Index basket test, 96 of 116 tested stores let a browsing agent reach checkout, against 8 for a page-fetching agent. A dot browses, so it sits on the more favourable side of that split. Our guide to agent checkout friction covers what stops it between basket and payment.

Limits: this was one unsigned browser on one day from one network. It shows what each sign-in page asked for, not whether a signed-in dot could complete a purchase. We publish totals only.

What dots mean for your sign-in and checkout

Dots don't need an integration. They need your site to work for a returning customer acting through a signed cloud browser. That gives five checks:

1. Bot rules on sign-in, cart and checkout. Decide whether verified ChatGPT Agent traffic may reach these pages, and set the rule on purpose rather than letting a general bot score decide. In our scoring specification, ACC-10 to ACC-12 cover agent access to product pages and the homepage without a challenge, and TRX-02 (cart is reachable by agent identities) and TRX-03 (no captcha on cart or checkout pages) cover the buying path. Our guide to whether you are blocking AI shopping agents walks through CDN and WAF settings.
2. A sign-in an agent can finish with help. OpenAI's private form takes a password or a verification code. A challenge that loops, or one the form can't pass on, makes the user take over or ends the attempt.
3. Saved cards that work at checkout. If your platform lets customers save a card to their account, check what a signed-in customer has to type at checkout. OpenAI tells users never to paste payment details into the conversation, so any step that asks for card details again is likely to hand the purchase back to the user.
4. Session length. OpenAI says a dot keeps a session until the user signs out or the site expires it. Very short sessions turn every repeat order into a new sign-in.
5. A guest route as the fallback. TRX-01 (guest checkout is available) still matters: when the shopper has no account, the user can take over and pay as a guest.

What to do this week

1. Find the setting. If you run your own Cloudflare, Akamai, HUMAN or Vercel set-up, look up how ChatGPT Agent traffic is handled on your sign-in, cart and checkout paths today. OpenAI's allowlisting page has the exact names and detection ID. On Shopify, Shopify's Help Center says Cloudflare sits in front of every store and needs no action from you, so the edge decision is Shopify's. The same page says hCaptcha is on by default for customer account pages, and that Plus stores can switch on extra bot protection for checkout, so review both settings with dots in mind.
2. Check your proxies keep the signature. If anything sits between your CDN and your origin, confirm the Signature, Signature-Input and Signature-Agent headers survive.
3. Sign in from a cloud browser. Using a test account, sign in to your store from a standard browser on a data-centre IP. Note every challenge, redirect and code step, and whether a saved card appears at checkout.
4. Ask your fraud team one question. Will a correct sign-in from a data-centre IP, followed by a saved-card order, be challenged or declined? If yes, decide whether verified ChatGPT Agent traffic should be treated differently.
5. Watch your logs. Start a saved search for requests with Signature-Agent: "https://chatgpt.com" on account and checkout URLs, so you can see dots arrive and where they stop.

Sources

• OpenAI, Introducing dots, 29 September 2026
• OpenAI Help Center, Getting started with your dot and Dots privacy, security, and safety FAQs, read 31 October 2026
• ChatGPT Learn, Dots: computers and apps, read 31 October 2026
• OpenAI Help Center, Using cloud browser in ChatGPT and ChatGPT Work's Cloud browser allowlisting, read 31 October 2026
• OpenAI, Overview of OpenAI crawlers, read 31 October 2026
• The Verge, "OpenAI's Dot agent is enterprise software that can also order your dinner", 2 October 2026
• Shopify Help Center, Customer accounts and Dealing with bots, read 31 October 2026
• ConversionVector, sign-in page scan of the 225 scored Index retailers, 31 October 2026; Agent Commerce Index Q4 2026 (CC BY 4.0) and Agent Conversion Score specification v0.6