com.linkedclaims.claim

A verifiable claim about any URI-addressable subject.

Details · record, key tid
Kindrecord
Record keytid
Authoritylinkedclaims.com
Indexed

Record

record · key tid

Properties

aspect

string

The specific aspect being rated or assessed (e.g., quality, reliability, timeliness).

claimType

requiredstring

Category of claim. Open vocabulary — common values include skill, credential, impact, endorsement, dispute, rating, review, membership, supersedes, revocation.

claimUri

string · uri

Persistent URI identity of this claim per the DIF Labs LinkedClaims spec. This is how other claims reference this one (by using this URI as their subject). May be an AT-URI if the claim originated on ATProto, or an HTTPS URL or other URI if it originated elsewhere. Must be a well-formed, persistent, dereferenceable URI.

Signer's confidence in this claim (0-1).

  • minimum: 0
  • maximum: 1

createdAt

requiredstring · datetime

When this record was created.

effectiveDate

string · datetime

When the claim became/becomes true (may differ from createdAt).

For claims signed by external methods (MetaMask, aca-py, Digital Bazaar, etc.) before being published to ATProto. Preserves the original signer identity when the ATProto repo owner differs from the claim signer.

Reference

Supporting materials provided to back up this claim — photos, videos, screenshots, documents, links. For example: source might be a Wikipedia article, evidence is the screenshot you took of it. Source might be you (first-hand), evidence is the video you recorded. Each item has a URI and optionally a content hash for integrity.

itemsref
Reference

object

string

Optional object of the claim (e.g., skill name, credential type, rating category).

respondAt

string · uri

URI where endorsements, disputes, or other responses to this claim may be sent. Per the LinkedClaims spec, MAY behave like an ActivityPub inbox.

Where this claim comes from — a person, a website, a document. For example: 'I saw this on Wikipedia' (source.uri = the Wikipedia URL), or 'My colleague told me' (source.uri = their DID, howKnown = SECOND_HAND). Source is not evidence — it's the origin of the information.

Reference

stars

integer

Star rating (for rating-type claims).

  • minimum: 1
  • maximum: 5

statement

string

Human-readable explanation of the claim.

  • maxLength: 10000

subject

requiredstring · uri

The entity this claim is about. Can be any URI: HTTPS URL, DID, AT-URI, IPFS CID, or another claim's claimUri (for claims-about-claims such as endorsements or disputes).

#claimSource

object

Where this claim comes from. A source can be a person (DID, URL), a website, a document, or any URI-addressable origin. Based on the cooperation.org/credentials/v1 ClaimSource vocabulary.

Properties

author

string · uri

Original author of the evidence (if different from claim signer).

curator

string · uri

Entity that curated/surfaced this evidence.

dateObserved

string · datetime

When the evidence was observed/collected.

Multibase-encoded hash of the evidence content for integrity verification, per W3C VC Data Model 2.0 (e.g., zQm...).

howKnown

string

How the signer knows this claim to be true.

  • knownValues: FIRST_HAND | SECOND_HAND | WEB_DOCUMENT | VERIFIED_LOGIN | SIGNED_DOCUMENT | BLOCKCHAIN | RESEARCH | OPINION | OTHER

uri

string · uri

URI of the evidence (HTTPS URL, IPFS CID, AT-URI, etc.).

#embeddedProof

object

Cryptographic proof from external signing methods. Allows claims signed via MetaMask, aca-py, Digital Bazaar, etc. to be published on ATProto while preserving the original signer identity.

Properties

created

requiredstring · datetime

When the signature was created.

Purpose of the proof (typically assertionMethod for claims).

  • default: "assertionMethod"

proofValue

requiredstring

The signature value (format depends on type).

type

requiredstring

Signature suite type (e.g., EthereumEip712Signature2021, Ed25519Signature2020, JsonWebSignature2020).

verificationMethod

requiredstring

DID or key identifier of the actual claim signer (e.g., did:pkh:eip155:1:0xABC..., did:key:z6Mk..., did:web:example.com).

#evidenceItem

object

A piece of supporting material for a claim — a photo, video, screenshot, document, or link. Evidence is what backs up the claim; source is where the claim comes from.

Properties

What this evidence shows or contains.

  • maxLength: 1000

Multibase-encoded hash of the content for integrity verification (e.g., zQm...).

mediaType

string

MIME type of the evidence (e.g., image/jpeg, video/mp4, application/pdf).

uri

string · uri

URI of the evidence (HTTPS URL, IPFS CID, AT-URI, blob reference, etc.).

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • An identity claim linking this DID to an external account

  • monster.attest.verification

    record not from the namespace authority

    A verifier's statement that it checked a claim and found the proof token in place. Issued by any account, including the attest service's own; trusted as far as the verifier is.

  • network.attested.proof

    record not from the namespace authority

    A remote attestation proof: a standalone record in the attestor's repository that binds, via a canonical attestation CID, to a subject record living elsewhere. Referenced from the subject's `signatures` array via com.atproto.repo.strongRef. The `cid` is computed from the subject record (signatures stripped) with this record's metadata (cid/signature/signatures stripped, `repository` = subject's repo DID added) inserted as $sig, DAG-CBOR + SHA-256 + CIDv1. Verifiers recompute that CID and require

  • A remote attestation proof record holding the CID of attested content. Lives in the attestor's repository and is referenced from the attested record's `signatures` array via `com.atproto.repo.strongRef`. Conforms to the ATProtocol Attestation Specification.

  • monster.attest.claim

    record not from the namespace authority

    The author claims control of a website, domain, or handle on another service. A verifier places attest-proof:<record cid> where only the controller could and issues a monster.attest.verification. Record key: a base32 sha256 of the subject/target, so there is one per author per subject.