Paylogee
KYA Check Agent Authority Test Create free Sandbox

Agent Identity & Governance

Can you prove who your AI agent is before you trust it with money?

Verify machine identity, enforce spend boundaries, and generate audit-ready cryptographic proof before authorizing payments.

Principal-bound Key-backed Policy-enforced Evidence-ready
Run free KYA Check Set up KYA Test an Agent
No wallet · No real funds · No account required for the public check. The public check demonstrates KYA posture only. The public check does not create a KYA identity or issue a KYA Verified badge.

Free KYA Check

The 9 Standards of a Verified Machine Identity

See how Paylogee evaluates machine identity posture before an agent is trusted with delegated financial authority.

NOT COMMERCE-READY
Current check Can you prove which agent made the request?
Shared credential Identity drift Commerce-ready agent
Identity posture 5 / 9 controls ready
✓ Unique Agent ID i A stable machine identity that can be referenced consistently across policy, execution, and evidence.
✓ Principal binding i Links the agent to the accountable organization principal responsible for its delegated authority.
! Dedicated signing key i Uses an agent-specific public verification key rather than a shared credential.
! Credential expiry i Requires time-bounded credentials so stale authority cannot remain valid indefinitely.
! Replay protection i Rejects reuse of previously consumed or duplicated signed requests.
✓ Bounded spend authority i Constrains what the agent may spend independently of model instructions or prompts.
✓ Server-side policy i Keeps enforceable commerce rules on the trusted Paylogee control plane.
! Runtime signature i Proves that the current request was signed by the bound agent identity.
✓ Evidence chain i Preserves append-only evidence so identity and authority decisions can be inspected later.

The public check demonstrates control posture only. A real KYA Verified badge is earned after a registered agent satisfies Paylogee's current identity, principal-binding, fingerprint, and active signing-key requirements.

Put the standards on your own agent

Create a governed KYA identity in Paylogee Sandbox.

Real KYA setup requires a registered Paylogee account, organization context, registered agent, principal binding, current fingerprint, and active signing key before the KYA Verified badge or Agent Passport becomes available. Then apply spend authority and policy before commerce execution.

Set up KYA

Verifiable proof

Build Customer Trust with Verifiable Proof

Give buyers, platforms, and enterprise reviewers a compact identity artifact they can inspect instead of relying on an agent's self-declared claims.

Sample KYA badge

Earned proof that travels with the agent.

✓ KYA VERIFIED BY PAYLOGEE
SAMPLE · DEMONSTRATION ONLY

An eligible registered agent can publish this trust signal after satisfying Paylogee's current KYA identity criteria.

Preview only — not issued to a real agent, organization, or customer.

Sample Agent Passport

Demo Procurement Agent
KYA VERIFIED · SAMPLE

A real Agent Passport is published only after the registered Paylogee identity satisfies current principal-binding, fingerprint, and active signing-key requirements.

Principal binding✓ Verified organization principal
Agent fingerprint✓ Current
Signing key✓ Active
Runtime identity✓ Recent proof
Delegated authorityBound separately
Commerce evidenceInspectable
Inspect sample metadata

Static demonstration metadata — not a signed certificate.

{
  "identity_posture": "sample",
  "principal_binding": "verified",
  "fingerprint": "current",
  "signing_key": "active",
  "runtime_identity": "recent",
  "commerce_evidence": "inspectable"
}
DEMONSTRATION ONLY · No live customer identity, agent verification, payment authority, or real funds are represented by this sample.