Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tattoo.dev/llms.txt

Use this file to discover all available pages before exploring further.

Trust Model

TattooAPI is not just a dataset. It is a trust-layered dataset. The ontology-first model separates data maturity, verification, rights, consent, and visibility so downstream APIs and agents do not confuse them.

Core Fields

FieldPurpose
recordStateData maturity: raw, normalized, curated, verified, deprecated
verificationStatusHow much the identity or claim has been checked
approvalStatusWhether the record is draft, pending review, approved, restricted, or rejected
visibilityPrivate, internal, partner, or public publication scope
licenseStatusRights posture for creative or factual assets
consentLevelAllowed use level for automation, recommendation, publishing, and reuse
sourceTypeHow the record entered the system
originAuthorityWho or what stands behind the record

Why recordState Exists

recordState is separate from verificationStatus.
  • A record can be normalized but still unverified.
  • A record can be curated for public discovery without being fully credential-verified.
  • A record should not be marketed as trusted just because it exists in the database.

Current Data Tiers

  • Raw: scrape output or imported source records, not yet normalized
  • Normalized: mapped into canonical fields
  • Curated: normalized, deduplicated, taxonomy-bound
  • Verified: explicitly reviewed by editorial or credential workflow

Current Runtime Caveat

The current API runtime is still transitioning. Where full trust metadata is not available in the underlying legacy tables, the goal is to return conservative values such as:
  • verificationStatus: "unverified"
  • licenseStatus: "rights_unknown"
  • consentLevel: "recommendation_only" or another intentionally narrow scope
That is preferable to pretending certainty.

Governance Priority

The first governance priorities are:
  • rights and provenance for creative assets
  • consent boundaries for client and session records
  • cultural review for sensitive motifs and references
  • verified operator preference for high-trust matching