Tarno docs portal
Tarno exposes a neutral read contract over the INAPI trademark corpus: a versioned REST
API (under /v1) and a Model Context Protocol (MCP) server, both backed by the same query layer
and the same Zod schemas, so the two transports return identical results. This portal is the
human-facing onboarding documentation; it is neutral and reusable across consumers.
The authoritative schema lives in the live OpenAPI reference at
/docs(an interactive Scalar page generated from the code). These guides explain how to onboard and link to that reference — they do not duplicate the schema. When a field or endpoint detail is not spelled out here,/docsis the source of truth.
Integration guides (DOCS-01)
| Guide | What it covers |
|---|---|
| Getting started | Base URL + /v1, getting an operator-issued key, first GET /v1/brands call (curl + TS fetch), keyset pagination/filtering, the error envelope, quota basics. |
| Authentication and scopes | The X-API-Key header, scopes brands:read / insights:read (empty = unrestricted), key lifecycle (rotate/revoke/expiry), and 401 / 403 / 429 semantics. |
| Connect your AI agent (MCP) | The https://mcp.tarno.cl endpoint, X-API-Key, Streamable HTTP transport, the search_brands / get_brand_detail tools, and example client configs. |
| Code samples | Copy-paste REST (curl + TS fetch) and MCP (@modelcontextprotocol/sdk) clients. |
Contract and operations (DOCS-02)
| Document | What it covers |
|---|---|
| Status | Service status and where live freshness/health surfaces. |
| Versioning & deprecation | The /v1 prefix contract and how breaking changes get a new version. |
| v1.6 migration | The v1.6 consolidation, now applied (window closed): denominacion→nombre, fechaDesde/Hasta→fechaPresentacion* (retired), and estado→a validated 14-code vocabulary (out → 400). |
| SLA | Uptime stance, sync/freshness cadence, support expectations. |
| Holiday calendar | The Chilean statutory calendar the corpus uses to count business days: tipo/origen per row, the range it claims to cover (GET /v1/feriados/cobertura), and the 422 fuera_de_cobertura when you ask beyond it. |
| Historical coverage | How far back the trademark corpus reaches (distinct from the holiday calendar). |
| Changelog | Release history of the read contract. |
The DOCS-02 documents are produced by the sibling plan in this phase; their links are listed here so this index is the single entry point to the whole portal.
Authoritative API reference
The full, always-current per-field REST schema is the interactive OpenAPI (Scalar) reference
served at https://api.tarno.cl/docs. Start with the
guides above to onboard, then use that reference as the canonical schema for every endpoint,
parameter, and response shape.