Turn anonymous agents into known customers.

Put a verified human behind every AI agent, with cryptographically bounded access to funds, wallets, and checkout rails. Add it to your MCP server in one integration to enforce strict spending guardrails and keep your direct customer relationships.

FIDO2·NIST AAL2·SOC 2·PSD2 SCA
Agent requestOrder #4821

Shopping agent is requesting checkout on your behalf.

Guardrails activeMax transaction limit: $50
Checkout up to $200
Use saved shipping address
Store payment method

Jordan A. Reyes

Verified customer · opted in

Identity provided by LoginID

Securing and identifying autonomous agents across all major frameworks

  • ChatGPT
  • Claude
  • Gemini
  • Copilot
  • Perplexity

An agent checkout doesn't have to cost you the customer.

When an AI agent buys on someone's behalf, most merchants get an anonymous guest and a masked email. LoginID hands back a verified, opted-in customer you can keep: the relationship, the loyalty, the lifetime value.

Guest checkout

Unknown customer

a••••@••••.com

  • No relationship
  • No loyalty or LTV
  • No re-engagement

Known customer

Jordan A. Reyes

jordan.reyes@email.com

  • 100% human-to-agent attribution
  • Zero fraud-related chargebacks from rogue agent loops
  • Seamless 1-click biometric authorization

For developers

One integration for your MCP server.

Add verified identity and signed payment mandates to your MCP server or agent app without building auth from scratch. One SDK handles the passkey ceremony, the scope, and the signed confirmation, so you never touch a raw credential.

  • Passkey-backed proof of the human, not just the agent
  • Scoped, signed, revocable mandates by amount, merchant, and intent
  • FIDO2 under the hood; works with any agent or MCP client
Read the docs
agent-checkout.ts
// 1. Verify the human behind the agentconst { token } = await loginid.verifyPasskey({ user }); // 2. Scope what the agent may doconst mandate = await loginid.createMandate({  token,  scope: { maxAmount: 200, currency: "USD" },  expiresIn: "15m",}); // 3. Confirm the signed transaction at checkoutawait loginid.verifyTransaction(mandate.id);

Illustrative: see docs.loginid.io for the full API

Whether you sell to agents or build for them.

Merchants keep the customer relationship when an agent buys. Developers add verified identity to their MCP server. Same platform, one integration.

For merchants

Own the customer when an agent buys.

Agentic shoppers arrive with high purchase intent. Welcome that traffic on your terms, and don't get intermediated the way grocers were by delivery apps.

  • A new high-intent sales channel
  • Keep loyalty, LTV, and the direct relationship
  • Verified customers, not anonymous guests
Explore for merchants
For developers

Add agent identity to your MCP Server.

Drop verified identity, scoped consent, and signed payment mandates into your MCP Server or agent app, without building auth from scratch. One API, FIDO2 under the hood.

  • One integration, no auth to build
  • Scoped, signed, revocable mandates
  • Works with any agent or MCP client
Read the docs

Trust is the product.

Standards-based by design

FIDO2-certified and a FIDO Alliance member. Standards aren't an afterthought; they're our foundation.

Compliance, by default

FIDO2, NIST AAL2, SOC 2, PSD2 SCA, and PCI. The assurance level enterprise risk and payments teams require, built in from the start.

Non-repudiation you can account for

Every approval is a signed, hardware-protected attestation of intent, an audit trail that holds up against chargebacks and disputes.

Certified & auditedFIDO Certified: FIDO2 and UAFAICPA SOC for Service Organizations

Frequently asked questions

What is LoginID?
LoginID is a FIDO2-certified strong authentication platform that provides end-to-end passwordless login, identity verification, and digitally-signed transaction authorization for both people and AI agents. It lets businesses replace passwords and one-time passcodes with passkeys, and add verifiable trust to payments, banking, and agentic commerce with minimal backend changes.
What is passkey authentication?
Passkey authentication uses FIDO2/WebAuthn credentials bound to a user's device and unlocked with biometrics or a device PIN instead of a password. The private key never leaves the device and there is no shared secret to phish, intercept, or breach, which makes passkeys both faster for users and phishing-resistant by design.
Is LoginID phishing-resistant MFA?
Yes. LoginID is built on FIDO2/WebAuthn passkeys, which are origin-bound and use public-key cryptography, so there is no password or one-time passcode for an attacker to phish, replay, or steal. This meets the bar for phishing-resistant multi-factor authentication and aligns with NIST AAL2 guidance.
How does LoginID authenticate AI agents?
LoginID verifies both the agent and the human behind it. It confirms the agent's identity using standards like Web Bot Auth, then binds the action to a passkey-backed user consent with scoped, signed, and revocable mandates, so an AI agent can only do what its user explicitly authorized in agentic commerce and checkout flows.
What standards and certifications does LoginID support?
LoginID is FIDO2 certified and supports NIST AAL2 assurance, SOC 2, and PSD2 Strong Customer Authentication (SCA). Authentication is based on the open FIDO2/WebAuthn standards, so it interoperates with existing devices, browsers, and passkey ecosystems.
How is LoginID different from passwords and one-time passcodes?
Passwords and SMS or app-based one-time passcodes rely on shared secrets that can be phished, intercepted, or breached, and they add friction at login. LoginID uses device-bound passkeys with no shared secret, which removes the most common account-takeover attack vectors while giving users a one-tap biometric sign-in.

Know the agent. Keep the customer.

Open the door to AI agents on your terms, with a verified human behind every transaction. Ship it with a single integration.