# tattoo.dev

> The human-facing developer platform for TattooAPI, the governed data and workflow API for the tattoo industry.

tattoo.dev explains the platform and its use cases. docs.tattoo.dev is the canonical implementation reference. api.tattooapi.com is the canonical machine-facing API origin.

## Canonical developer surfaces

- [Developer platform](https://www.tattoo.dev/)
- [Documentation](https://docs.tattoo.dev/)
- [Developer console](https://partners.tattoo.dev/)
- [TattooAPI discovery document](https://api.tattooapi.com/)
- [OpenAPI 3.1 contract](https://api.tattooapi.com/openapi.json)
- [Authenticated read-only MCP endpoint](https://api.tattooapi.com/mcp)
- [MCP OAuth protected-resource metadata](https://api.tattooapi.com/.well-known/oauth-protected-resource/mcp)
- [GitHub](https://github.com/Tattoo-co/tattoo-api)

## API posture

- Canonical resource operations use the `api-version=2026-07-01-preview` query parameter.
- `/api/v1` remains available as a compatibility base path.
- Public reads are limited to approved projections.
- Public writes are blocked.
- Owner and partner operations require scoped authentication, policy checks, and review where applicable.
- Raw private records, credentials, internal worker infrastructure, and unapproved source data are not public API truth.

## Recommended agent flow

1. Read the TattooAPI discovery document.
2. Load the OpenAPI contract for HTTP operations.
3. Use docs.tattoo.dev for implementation guidance and authentication details.
4. Use the protected-resource metadata before connecting an OAuth-capable MCP client.
5. Treat mutation requests as unavailable unless a documented, authenticated, and approval-gated contract explicitly permits them.