People search
This guide covers the person-centred read: find a holder or representative and learn how much of the register is theirs. It complements field-scoped search, where people are a filter over marks; here they are the subject of the query.
The complete, always-current per-field schema lives in the interactive OpenAPI reference at
https://api.tarno.cl/docs(Scalar). This guide explains the contract and links to that reference — it does not restate the schema. The reference is authoritative when a field is not documented here.
Throughout this guide the base URL is https://api.tarno.cl and every call carries the X-API-Key
header.
GET /parties · scope brands:read · MCP twin: list_parties
The parties resource inverts the question: it starts from the person and tells you how much of the
register is theirs. Holder, applicant, representative and opponent are one entity with a role wherever
it participates.
curl -sS "https://api.tarno.cl/parties?q=carey" -H "X-API-Key: $TARNO_API_KEY"
{
"results": [
{
"id": "1261017",
"name": "ESTUDIO CAREY LIMITADA",
"taxId": "76111111-6",
"country": "CL",
"kind": "legal",
"kindSource": "tax_id",
"trademarkCount": 3492,
"publishedName": "Estudio Carey Limitada",
"review": null,
"mergedInto": null
}
],
"limit": 20,
"next": null,
"hasMore": false,
"meta": { "dataAsOf": "2026-09-20T19:05:06Z", "coverageThrough": "2026-09-17" }
}
How to search
| Parameter | What it does |
|---|---|
q |
Partial, accent-insensitive match on the name. 2 to 256 characters. argandona finds Argandoña. |
taxId |
Exact match. Accepts any format (12.345.678-5, 12345678-5) and normalizes it. |
kind |
natural | legal | unknown. |
role |
holder | applicant | representative | opponent. |
sort |
trademarkCount (default, largest first) | name, with optional asc or desc (name desc). |
limit / cursor |
Opaque-cursor pagination. limit default 20, max 100. |
No parameter is required: without filters every party is listed, including those with no marks.
Without sort, results come ordered by trademark volume, largest first.
Both orders are fast, with any filter. Each party's mark count is stored at the end of every daily sync,
so ordering by volume comes from an index; with sort=name the page is chosen first and the count is
computed only for its rows. ⚠ While a sync is running (about 25 minutes a day) the stored count is no longer
asserted and ordering by volume is computed on the fly: the response is the same, but it takes one to three
seconds (up to eight with kind or role).
Every response carries the corpus freshness in meta: dataAsOf (when the last sync finished) and
coverageThrough (up to which filing date coverage reaches).
Counts are of NOW — trademarkCount does not filter
trademarkCount counts only what the person holds today. ⭐ It does not filter: people with
no marks still appear, with their trademarkCount at zero — a person without marks today may have them
tomorrow, and why they are there is data.
Merged parties — mergedInto
When two records turn out to be the same party (the same holder written two ways, a corrected RUT…), one
is merged into the other: its trademarks and annotations move to the one that survives. The merged
record is not returned by GET /parties (list_parties), under any sort or filter. If you stored its
id, GET /parties/{id} (get_party) still returns it, with mergedInto = the id of the party that
holds its trademarks now (the end of the chain, if that one was merged later too). For any other party,
mergedInto is null.
The other reads by id (/trademarks, /relations, /outcomes, the portfolio report) answer for the
record you asked for, which has no trademarks after the merge: for the party's data, use the mergedInto id.
What the SII says — sii
Every party with a Chilean RUT listed in the SII roster of legal entities carries the sii block (in
GET /parties/{id} ≡ get_party and in every party of GET /parties ≡ list_parties): the legal name
(legalName; the INAPI name stays in name), the company type (companyType: SII code, our label in three
languages and the SII wording), the start of activities, the end of business, the comuna and region of the
current domicile per the SII and the current branches by comuna. The street address is not published.
- Source and date on each block:
source: "sii"andasOf= the date of the SII file it was read from. The roster and the addresses are two files, each with its own date. A change after that date is not seen. addressis the CURRENT domicile per the SII (basis: "current_sii_domicile"), not the one at filing: that isterritory, from INAPI. They often differ (moves).businessEndedOnis the end of business («término de giro»): the end of the tax activity, not a dissolution. A company whose business ended may still hold its trademarks.sii: null= no data: the party has no Chilean RUT, the current SII file does not list it (or lists it with another check digit), or the party was merged into another (mergedInto; read that one). Never a guessed value. Inside the block,branches: null= no addresses read yet for that RUT;address: null= not read yet or the SII lists no current domicile for it (ifbrancheshas a value, it is the second case);branches.count: 0= the SII lists no current branches.address.regionNameis the SII's literal text: to compare regions useregionCode.
"sii": {
"source": "sii",
"asOf": "2026-08-05",
"legalName": "EJEMPLO SOCIEDAD POR ACCIONES",
"companyType": {
"code": "223",
"label": { "es-CL": "Sociedad por acciones (SpA)", "en": "Stock company (SpA)", "pt-BR": "Sociedade por ações (SpA)" },
"source": { "label": "SOCIEDAD POR ACCIONES", "kind": "PERSONA JURIDICA COMERCIAL" }
},
"activityStartedOn": "2011-04-12",
"businessEndedOn": null,
"address": {
"source": "sii",
"asOf": "2026-08-05",
"basis": "current_sii_domicile",
"since": "2019-03-01",
"communeCode": "13114", "communeName": "LAS CONDES",
"regionCode": "13", "regionName": "XIII REGION METROPOLITANA"
},
"branches": {
"count": 3,
"communes": [
{ "communeCode": "13101", "communeName": "SANTIAGO", "regionCode": "13" },
{ "communeCode": "13123", "communeName": "PROVIDENCIA", "regionCode": "13" }
]
}
}
To get a person's marks (not just the count), use
GET /parties/{id}/trademarks or the person filters on GET /trademarks:
# a person's marks, by id
curl -sS "https://api.tarno.cl/parties/1261017/trademarks" -H "X-API-Key: $TARNO_API_KEY"
# by RUT (any role), in the trademark search
curl -sS "https://api.tarno.cl/trademarks?taxId=76111111-6" -H "X-API-Key: $TARNO_API_KEY"
What kind of party each person is
Each person publishes kind (natural | legal | unknown) and kindSource (which signal produced it:
tax_id | suffix | manual | name_pattern; the SAME vocabulary on the party embedded in a trademark,
since 2026-09-23). name_pattern (since the change of 2026-10-28) is a calibrated inference from the shape of the name (words of
personal names, or company words such as SOCIEDAD or FUNDACION), applied only where its accuracy measured
against the cards with a RUT has a lower Wilson bound ≥ 98 %; a RUT that arrives later corrects it. unknown is a value, not a gap: about a third of the corpus carries
neither a RUT nor a company suffix, and the contract says so instead of inferring it. taxId is null for
foreigners (by definition, a RUT does not exist) and in older filings where INAPI did not publish it. For the
rest of the person's fields (territory, publishedName, jurisdictionClause, review, …), see the
reference https://api.tarno.cl/docs.
Relations between parties
GET /parties/{id}/relations (MCP tool list_party_relations) answers in one call "who does this party share
marks with, who represents it, whom did it assign to, who opposed it?". It returns typed edges, each backed
by marks in the corpus:
type |
meaning | date (firstOn/lastOn) |
coverageFrom |
|---|---|---|---|
co_holder |
both hold the same mark (a holder retired by a change of name, a transfer or the cession of the pending application does not count as a former co-holder) | filing date of the marks | null (whole corpus) |
represents / represented_by |
this party represents marks of the other, or the reverse | filing date of the marks | null |
assigned_to / assigned_from |
assignment: a holder retired by an INAPI transfer (A07T) vs the mark's holder |
date of the act | 2011-08-01 |
opposed / opposed_by |
an identified opponent in an act on the mark vs its holders | date of the act | 2024-04-19 |
Each edge carries the other party (party: id, name, taxId, kind), trademarkCount, firstOn/lastOn,
up to five evidence marks (newest first) with evidenceTruncated — page the full list with
GET /parties/{id}/trademarks or the trademark search —, and a label in the three languages. Filter by
type (a list) and by relation (current by default, former, all — the same vocabulary as
/parties/{id}/trademarks); ordered by trademarkCount, paginated with cursor.
curl -sS "https://api.tarno.cl/parties/1261017/relations?type=represented_by,opposed_by" \
-H "X-API-Key: $TARNO_API_KEY"
⚠ How to read them:
- "Never opposed" reads "not since 2024-04-19": oppositions exist in the corpus only since the first
Estado Diario of our own (the one of 2024-04-19). And only identified opponents count: when the printed name matches no party or several,
the counterpart is not invented; with
opposed_by,meta.unresolvedOpponentMentionssays how many mentions stayed unidentified. - The counterpart of an opposition or an assignment is the mark's holder per
relation(today's, by default), not the holder at the date of the act: the corpus does not record since when each holder is listed. With chained assignments, today's holder is not necessarily the assignee of that act. - ⛔ They are signals with evidence, never verdicts: there are no "same business group" edges and no edges by name or address similarity. A person duplicated in the corpus may show up split into two counterparts.
Outcomes and changes of a party
GET /parties/{id}/outcomes≡get_party_outcomes: how the party's trademarks ended up (as representative by default, or as holder), by published status group, withn,grantShareover the decided ones (pending excluded) and the full definition. Not a «success rate»: see outcomes.POST /annotations/searchwithpartyIdortaxId(andpartyRole,relation,dateFrom…): the acts of the party's trademarks — «what happened this week to this RUT's trademarks?». See annotations by party.- In the trademark search,
partyRolenext totaxIdlimits the RUT to one role (RUT).
From an AI agent
list_parties(q: "carey", limit: 5)
list_parties(taxId: "12.345.678-5")
get_party(id: "1261017")
list_party_trademarks(id: "1261017")
list_party_relations(id: "1261017", type: ["represented_by", "opposed_by"])
The MCP tool returns the same { results[], … } envelope and is byte-identical to GET /parties.
See also
- Field-scoped search — people as a filter over marks.
- Getting started — envelope and keyset pagination.
- The live OpenAPI reference at
https://api.tarno.cl/docs.