Quick definition
Session authentication is the mechanism a B2B portal uses to verify who the buyer is and keep that identity throughout the visit, so it can show the right catalog, prices and terms. It works well for a person in a browser and it is where most AI agents stop today.
What does it mean?
A B2B portal is not an open store. The allowed catalog, the price and the credit depend on the account, so the portal asks for a username and password and keeps the session in the browser.
Within one account there are also different permissions: the person who requests, the one who approves and the one who pays are not the same.
Why is it important?
Everything valuable on a B2B portal sits behind the sign-in. A visitor without a session, person or program, sees a reduced version: list prices, no stock, no terms.
An AI agent acting for a buyer needs to get in with that account’s permission. Sharing the password with it is not a solution: it leaves no record of who did what and gives no way to limit what the agent can do.
How does an AI agent identify itself on a B2B portal?
The right way is delegated access: the buyer authorizes the agent and the portal issues it its own credential, with a limited scope (for example, quote and build an order, but not approve it) and an expiry. It is the same principle OAuth 2.0 uses when an application asks permission to act on behalf of a user.
Corporate purchasing already has a precedent: PunchOut opens a session in the supplier’s catalog from the customer’s purchasing system, without the user typing another password. The pending work is offering agents something equivalent.
Applied example
A plant authorizes its purchasing agent to check prices and prepare orders up to a certain amount. The distributor’s portal issues a credential with that scope. The agent quotes, builds the order and leaves it pending approval by the maintenance manager, who authorizes it from their own session.
Related concepts
Session authentication is the key to contract pricing and multi-branch fulfillment. AI agents need it to operate, and protocols such as MCP define how an agent connects to a system with permissions. It is part of agentic commerce in B2B, along with the part cross-reference.
Common mistakes
Blocking every automated visitor without telling apart those authorized by a customer. Giving the agent a person’s password. And also hiding what could be public, such as technical data sheets, so neither search engines nor assistants find the catalog.
Edgebound Labs perspective
At the lab we separate two layers: what should stay public so the catalog can be found, and what requires identity. The ACR scanner measures the first from the outside, without signing in; the second is designed with each operation, because it defines what an agent can do on behalf of a customer.
Frequently asked questions about session authentication
Why can an AI agent not simply sign in?
Because sign-in is designed for a person in a browser. An agent needs its own credential, with limited permissions and a record of what it does.
What is delegated access?
It is when the owner of an account authorizes a program to act on their behalf within a defined scope, without sharing their password.
Does PunchOut solve authentication for agents?
It solves a closely related case: it opens a session between the customer’s purchasing system and the supplier’s catalog. It is a foundation, but it was designed for purchasing systems, not for agents.
Should I hide my whole catalog behind the sign-in?
No. Technical data sheets and product data can be public so search engines and assistants find them. The account’s price and credit do require identity.
Keep exploring the glossary
Does your portal recognize an authorized agent?
We audit your B2B commerce operation and tell you what it needs so that people and agents can buy from you, with clearly defined success metrics.