Tarno docs portal
Tarno exposes a neutral read contract over the INAPI trademark corpus: a REST API (no version prefix) and a Model Context Protocol (MCP) server, both backed by the same query layer and the same 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
https://api.tarno.cl/docs(an interactive Scalar page generated from the schemas the server actually uses). 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, the reference is the source of truth.
Integration guides
| Guide | What it covers |
|---|---|
| Getting started | Base URL https://api.tarno.cl, getting an operator-issued key, first GET /trademarks call (curl + TS fetch), keyset-cursor pagination, the results[] envelope, the RFC 9457 error body. |
| Authentication and scopes | The X-API-Key header, scopes (empty = base reads only), 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 catalogue of 54 tools, 4 resources and 3 prompts, and example client configs. |
| Field-scoped search | Searching with the text scoped to one field (denomination, holder, representative, tax id) and the advanced mode. |
| Similarity watch | Watching applications by number and reading their matches: /watch/applications and /watch/hits. |
| "Sync finished" webhook | The sync.finished notice when the daily chain ends, its signature and the test delivery. |
| Reports & oppositions | Daily bulletin, clearance, conflict landscape, portfolio and opposition briefs. |
| Documentary base (guidelines & statutes) | INAPI's Guidelines, statute texts, fees and indicators (legal:read). |
| Analysis and calculation | Comparing marks, class statistics, deadlines, business days and fees. |
| People search | Parties (holders and representatives), their marks, relations and outcomes. |
| Code samples | Copy-paste REST (curl + TS fetch) and MCP (@modelcontextprotocol/sdk) clients. |
Contract and operations
| Document | What it covers |
|---|---|
| Status | Service status and where live freshness/health surfaces. |
| Versioning & deprecation | The contract with no version prefix: versioned by its changelog, with a contract date as version. |
| SLA | Committed availability, RPO/RTO, maintenance, freshness and support. |
| Holiday calendar | The Chilean statutory calendar the corpus uses to count business days: GET /holidays, with declared coverage in meta.coverage. |
| Data model | The entities the API returns (trademark, annotation, party, class, norm, report, watch), their fields and how they relate. |
| Historical coverage | How far back the trademark corpus reaches (distinct from the holiday calendar). |
| Contract changelog | Every API and MCP change since 2026-09-17, with its label ([BREAK], [BEH], [ADD]…), its date and what you have to do. |
| Legal documents | Terms of service, personal data policy, data processing agreement (DPA) and sub-processors. |
Authoritative API reference
The full, always-current, schema-generated 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.