Ecosystem
tattoo.dev sits underneath the products that make the category real.
This route explains the relationship between tattoo.dev, tattoo.co, tattoo.agency, and Tattoo OS so the API is clearly framed as the foundation rather than a side project.
tattoo.co
Discovery and marketplace surface
Consumer-facing discovery, style-tagged artist portfolios, geo-indexed listings, and real-time availability — all running on tattoo.dev APIs. Not a reference implementation. A live product serving real artists and clients.
What it demonstrates
Consumer discovery, artist visibility, and listing distribution at scale.
tattoo.agency
Operator and growth workflows
Studio growth workflows, inquiry routing, conversion optimization, and operator dashboards — built on the same platform you'd access. Live proof that the booking and inquiry APIs hold up in production.
What it demonstrates
Studio growth systems, inquiry routing, and conversion pipelines in production.
Tattoo OS
Studio modules on the same foundation
Portfolio management, booking systems, client communication, and studio operations as modular products — one API layer, multiple surfaces. Proof of the platform's breadth across the full studio lifecycle.
What it demonstrates
Booking, portfolio, website, and studio workflow modules as ecosystem products.
TattooAPI is the primitive layer for the industry
TattooAPI keeps the shared objects portable across product surfaces: no vendor lock-in, open-core contracts, AI-native context, and reviewed writes for the people who actually do the work.
Artists
Artist, PortfolioAsset, ConsentRecord
Carry portfolio proof, attribution, travel history, flash, and reputation across studios and websites without surrendering ownership.
Clients
Inquiry, Booking, ReviewQueueItem
Move from discovery to consultation, deposit, consent, aftercare, and rebooking with clearer status and fewer broken handoffs.
Owners & Managers
Studio, WorkRequest, Policy
Operate the studio around approved artist, booking, portfolio, and communication state instead of scattered inboxes and stale spreadsheets.
Growth Operators
MediaObject, Signal, DistributionRule
Run SEO, attribution, reactivation, campaign, and local demand workflows from governed projections instead of scraping or copying raw source systems.
Builders & Agencies
Projection, API Key, Audit Event
Build websites, directories, AI-native agents, and partner tools against open-core contracts while TattooAPI keeps writes reviewed and accountable.
Architecture stack
Domain Ontology
Open ontology with structured tattoo entities, style taxonomies, and trust-tiered records. Every record carries a `recordState` field tracking data maturity and verification status across the corpus.
Workflow APIs
Browserless workflow APIs built on the domain ontology — artist search, studio discovery, portfolio, booking inquiry, and trust signals. This is the layer you build on.
Tools & MCP Orchestration
Tattoo-specific AI tools and Model Context Protocol integration built on the stable lower layers. The docs are live at docs.tattoo.dev/mcp — connect any MCP-compatible AI client directly.
Build alongside these products
The same API foundation that powers tattoo.co, tattoo.agency, and Tattoo OS is available for builders creating software inside the tattoo category.