Skip to main content
Know Your Agent (KYA) has two sides, joined by the KYA credential. One side gives agents a verified identity. The other side checks it, and sees every agent that arrives.

Where to start

If agents come to your site, app or API

If you build or run agents

For everyone

Get access

Email support@baselayer.com to get your keys and a sandbox to test in.

Accept agents

AI agents already browse, search and buy on your site. Most look like regular visitors or anonymous bots. Agent Acceptance tells you which visits are agents, how strongly each one is identified, and who stands behind it. Then you decide what each may do. How strongly an agent is identified, weakest to strongest: What you see, starting in watch-only mode:
  • Every agent visit, from the first page to checkout.
  • Which agent platforms visit, and how strongly each is identified.
  • Returning customers, recognized by an ID unique to your site, when their agent presents a credential.
  • Which agent visits end in a purchase, if you report purchases.
1

Install

Add the baselayer.js tag to your pages, check credentials in your own code at your server, or both. See Install Options.
2

Watch

Every decision your rules would make is recorded, and nothing changes for visitors. See Reading Agent Activity.
3

Set your rules

For each step, such as browse, cart and checkout, choose what each kind of agent gets: allow, step up or block. Baselayer supplies the facts, and your rules decide. See Set Your Rules.
Only visits detection finds to be automated are stored, and typed text and form values are never sent. See What baselayer.js Reports.

Give agents an identity

To most sites, your agent looks like any other bot, so it gets blocked, challenged or handed back to the person. A KYA credential lets your agent prove that a verified person or business stands behind it, so sites that accept KYA can let it browse, sign in and check out.
  • The person verifies once with Baselayer. Your agent then gets a credential for each site it visits, with no new sign-up at each one.
  • Each site gets its own stable ID for the customer, so it can recognize them and connect their account, loyalty and order history. A different site gets a different ID for the same person.
  • A credential includes only the fields the site’s rules ask for, never more.
  • Each credential is short-lived, signed by Baselayer and bound to your agent’s key, so a copied credential can’t be replayed. You can revoke it at any time.
Built on open standards: SD-JWT VC credentials, OAuth 2.0 token exchange, signed revocation lists, and keys published as JWKS and DID documents, so any site can check a credential with standard libraries. A credential says who is behind the agent and which checks Baselayer ran. It does not include spending authority or payment details.
1

Verify once

  • The platform sends the person through Baselayer’s hosted enrollment flow, or submits identity details it already collected.
  • In the hosted flow, the person enters their phone number, date of birth and country, types the code Baselayer texts them, and confirms their details.
  • The platform receives a stable individual_ref, plus a business_ref when a business is verified.
Runs once per person or business. See Verifying an Identity.
2

Mint for a site

  • The platform’s backend asks Baselayer to mint a credential for one site, using the audience the site returns with its nonce.
  • The credential is bound to the agent’s public key and can include only the verified fields the site’s rules ask for.
Runs for each site, and again when the credential expires. See Minting Credentials and the list of fields a credential can share.
3

Present

  • The agent gets a one-time nonce from the site and signs the presentation with its private key.
  • It then exchanges the presentation for the site’s access token.
Runs each session. See Presenting a Credential.
4

Check

  • The site, app, or API checks Baselayer’s signature, the credential’s revocation status, the agent’s signature, and that the credential was issued for it.
  • It then reads the shared details and decides what the agent may do.
Runs on each presentation. See Accepting Agents at Your Site and the Credential Format Reference.
The platform can revoke a credential through Baselayer at any time. See Managing and Revoking Credentials. It can also look up verification, issuance, and revocation events for a person, business, or credential it already holds. See Audit Log.

Support

Questions or issues? Email support@baselayer.com or check status.baselayer.com.