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.

​
TattooAPI

TattooAPI is the headless control plane for the tattoo industry: an open ontology, a structured knowledge and search API, and the contract layer for future workflow and agent tooling.

Open Ontology

The canonical domain model lives in the repo-native ontology package and generated reference docs.

Project Status

The current wave posture, Convex runtime cutover, public boundaries, and future-wave gates.

Trust-Tiered Data

Every serious record needs explicit provenance, trust, and data-maturity state.

Knowledge/Search API

The current public surface starts with search and studio discovery on top of the existing data foundation.

Open Source Build

The ontology, docs, and future SDK/tooling path are being built in public.

​
Product Model

TattooAPI is not a studio SaaS dashboard and not a consumer marketplace.
  • System of Context: open ontology plus structured tattoo entities and taxonomies.
  • System of Work: browserless workflow APIs built on top of that domain model.
  • System of Agency: tattoo-specific tools and orchestration once the lower layers are stable.

​
What Exists Today

  • A repo-native ontology package at packages/domain-ontology
  • Generated reference material in project-context/ontology
  • A self-hosted Convex target runtime for internal execution, with remaining legacy paths being isolated
  • A transitional public API surface for health, search, studios, auth, and API key endpoints
  • Internal SDK and operator workbench layers that are moving toward Convex-backed runtime truth
  • A large studio, artist, and portfolio corpus that is being staged and normalized with explicit provenance

​
Build Order

1

Ontology First

Lock the object model, taxonomies, relationships, governance, and trust fields.
2

Normalize Data

Map the existing studio and artist corpus into canonical records with explicit recordState.
3

Stabilize API

Document and harden only the endpoints that are real today.
4

SDK and Agents

Project the stabilized contracts into SDKs, tools, and workflow orchestration.

​
Start Here