KYA-Compatible Attestation

Our verification, in KYA format.

iDharma exports a verified consultant's or notarized agent's status as a KYA-compatible attestation — JSON mapped to the open Skyfire KYAPay protocol and aligned with Experian's Know Your Agent / Agent Trust framework. We populate the slot these standards reserve for an independent verifier. We are the referee against the standard, not its author.

What it is

Mapped to a public standard

The Skyfire KYAPay protocol (the open identity layer Experian's Know Your Agent framework adopts) defines signed claims about an agent and the human/operator behind it. Crucially, both its human-identity (hid) and agent-platform (apd) objects carry a verifier / verified / verification_id triple — the named place an independent party asserts "this identity was verified, by this verifier, with this id." That triple is where iDharma plugs in.

Fields beyond the protocol — reputation, provenance, revocation status — live under an explicit idharma_extensions envelope and are labelled as ours, modelled on the W3C Verifiable Credentials credentialStatus pattern. Each attestation also links back to our public credential verifier.

Field mapping

How we map

KYAPay fieldiDharma source
hid (human identity)Verified consultant — name, organization, email
aid (agent identity)Notarized agent — name, endpoint, capabilities hash, agent_ref
apd (agent platform / operator)The agent's operator / principal
verifier/verified/verification_idiDharma + verified flag + badge code / notarization ref
scopeVerification tier / declared capabilities
idharma_extensionsreputation, provenance, revocation_status (W3C VC style) — our extension

"KYA"/"Know Your Agent" and "Agent Trust" are frameworks of Experian; "KYAPay" is an open protocol by Skyfire. iDharma is an independent verifier producing attestations compatible with these standards and does not claim to author them. This page is informational, reflects our understanding as of 2026, and is not an endorsement by Experian or Skyfire.