Eight products. One record.

An agent gateway sits between AI agents and your business. It is the one official way for agents to learn about you, talk with you and do business with you, and your policy decides every request. TrueSession checks that the agent is who it claims to be, applies your rules and the access the customer granted, answers from your own systems and the facts you reviewed, and only lets an order through with the customer’s exact approval and a payment your provider confirmed.

No. TrueSession does not process payments. Your customer pays on your existing payment provider’s page, and TrueSession only accepts the provider’s verified result. Agents and TrueSession never see card numbers or one-time passcodes.

No. Your customers bring their own agents. TrueSession gives your business the agent address, the open protocols those agents speak, the approval and payment handoff, and the dashboard. You connect your systems and choose your rules.

Yes, that is the intended setup. You point a subdomain such as agent.yourstore.com to TrueSession with one DNS record, and agents find your official agent card, commerce document and connector there. If you prefer no DNS change, you can use a hosted TrueSession address instead.

You prove you own your domain, review what agents will be told and connect your catalog, booking or order system. Then you publish your agent address with a DNS record and add an entry script for browser agents. If you use a CDN, the TrueSession module there checks requests before they reach your site. Your human website and checkout stay as they are.

No script can do that alone, because many agents never run JavaScript. TrueSession uses the script for discovery and handoff, and enforces at your server or CDN edge, where every request arrives. Requests without a valid grant cannot reach protected data or complete consequential actions.

No one can identify every visitor. An agent working inside a customer’s own browser session can look identical to that customer. When behaviour suggests an agent, TrueSession flags the visit on your server and points it to your agent address, and your policy can slow it down or ask for a check. Behaviour alone never blocks anyone or unlocks anything. And even an undetected agent cannot complete a purchase, transfer or account change without the customer’s exact approval.

No. The goal is to let legitimate agents shop and ask questions through an official route that respects your rules. You decide what stays public, what needs a verified agent, and what needs the customer’s approval.

Yes, within limits the customer controls. During a task you can ask questions, send updates and attach discounts you fund, always labelled as merchant offers. Price alerts and follow-ups after the task need the customer’s separate consent for one purpose, with a message limit and an expiry, and the customer can revoke it at any time. Messages travel through the customer’s agent where it supports callbacks or an inbox. You can also run reminder and offer campaigns across many customers, with each person’s consent checked for every message.

Yes, that is one of the industries we are designing for. Agents can ask about products, pay known bills or move money between a customer’s own accounts within limits the customer set. A new payee, a larger amount or an account change always waits for the customer’s exact approval. The bank keeps its own strong customer authentication and core systems.

That is part of Offers, which is in the lab. The plan is to turn offers you already reviewed into ads in AI assistant ad programs, with every campaign paused until you approve it, and to sign offers so assistants and ad platforms can check them. Inside agent tasks, labelled offers you fund already work in our lab.

A price, stock level, opening hour or policy clause issued by your business as a small signed statement with a source and an expiry. Anyone, from an agent to a payment provider handling a dispute, can check that you really said it and when. No AI search engine checks signed business facts yet, so they first help with disputes and misquotes; this is in the lab.

One signed record per agent order, booking, payment or refusal that links five separate proofs: who asked, what your policy allowed, what the agent was told, what the customer approved and what happened. Signed receipts work in our lab today; the linked record and a public verifier are in the lab.

Bot management decides which traffic reaches your site. MCP gateways turn APIs into tools for a company’s own agents. TrueSession is for other people’s agents acting for your customers: it adds your policy per action, the customer’s delegation and exact approval, payment confirmation, signed answers, conversations and proof, across every agent protocol, and it works with the CDN you already have.

Which assistants reached you and how sure you can be (proven by signature, only claimed, or just observed on your website), what agents asked for and what you could not answer, what was refused and why, and how agent tasks ended, counting only orders your systems and payment provider confirmed. Customers’ prompts are not collected by default, and very small groups are hidden.

Any business where agents act for customers: retail and marketplaces, travel, banking and payments, subscriptions, telecom, utilities and ticketing. The authorization core is industry-neutral and first demonstrated with a synthetic travel merchant in our lab. Industry profiles add each sector’s own rules on top.

TrueSession is in early development. Its core flows work in our synthetic merchant laboratory, and we are preparing the first pilots. Join the pilot to help shape the first deployments.