Skip to content

WIPO Madrid System (WO/WIPO/Madrid)
Layer multilateral
Jurisdiction n/a (Madrid Protocol — 116 members, 132 countries)
Issuing body World Intellectual Property Organization (WIPO),

International Bureau (IB)

Rights administered: trademark (international registrations under the Madrid Agreement + Madrid Protocol) Working languages: English, French, Spanish (Common Regulations Rule 6) Connector status: skipped (ToS-blocked; no zero-infra path) Last verified: 2026-05-16 Manifest entry: not yet listed in coverage/sources.yaml — skipped pending a public WIPO Madrid search API.

Detail surveys:

Higher layers covering this office transitively:

Rating: 🔴 Red — ToS

ToS §6 bans automated queries (≤10 actions/min/IP); CHF 30,000/yr ICC FTP bulk is only programmatic path Jump to access details → View on the atlas →

§1 Mission

The Madrid System lets a trademark holder file a single international application in one language and one set of fees to seek protection in up to 132 countries through the WIPO International Bureau. The Madrid Agreement (1891) and Madrid Protocol (1989) define the legal infrastructure; the IB runs the International Register and publishes registration data through Madrid Monitor and (post-2024) the eMadrid Find-and-Monitor service. Agents care because the Madrid IR number is the canonical identifier that links national TM records back to a single international filing.

§2 What's unique here

  • The IR number — cross-jurisdiction identifier tying US, EU, JP, etc. designations to one filing.
  • The full designation chain (which countries, when, under Agreement vs Protocol, with which Nice classes).
  • Subsequent designations (Article 3ter additions).
  • Transformation and replacement events (Article 4bis; five-year "central attack" conversion to national applications).
  • Provisional refusals, refusals, final decisions, declarations of grant by designated offices on a standardized IB timeline.

§3 Programmatic surfaces

Madrid Monitor — public UI

Field Value
Endpoint https://www3.wipo.int/madrid/monitor/en/
Auth none
Format HTML (UI)
Rate limit "≤ 10 search-related actions per minute per IP"
ToS posture proxy-prohibited (automated queries forbidden)
Verdict 🔴 red
Primary source Madrid Monitor Terms of Use (July 2025)

ToS §5 prohibits bulk acquisition; §6 prohibits automated queries. Even though the UI is free, server-side proxying for end-users is not permitted. Slated for decommissioning once eMadrid Find-and-Monitor reaches parity.

Madrid Monitor — undocumented per-IR XML endpoints

Field Value
Endpoint GET /madrid/monitor/api/v1/data/{IRN} and /api/v1/tmxml/data/{IRN} on www3.wipo.int / www.wipo.int
Auth none
Format XML (WIPO ST.66 / Romarin v1.3 on /data/; TM-View on /tmxml/data/)
Rate limit inherits Madrid Monitor fair-use cap
ToS posture proxy-prohibited (same Madrid Monitor ToS applies)
Verdict 🔴 red
Primary source confirmed by probe 2026-05-16; example record /api/v1/data/WO500000000789955

Lookup-by-IRN only — no documented search params. Not advertised on the WIPO API Catalog and could disappear in the Find-and-Monitor migration without notice.

eMadrid "Find and Monitor"

UI-only successor to Madrid Monitor at madrid.wipo.int/findmonit/quick-search. Auth: none for search, WIPO User Account for watchlists/alerts. Format: HTML; export PDF/CSV/XML. ToS inherits the Madrid System family — 🔴 red, proxy-prohibited. No public REST/JSON API behind it as of 2026-05-16; primary source Finding and Monitoring International Trademark Registrations.

Madrid Monitor bulk XML (UN ICC FTP)

CHF 30,000/yr paid contract; daily yyyymmdd.zip deltas + images via UN International Computing Centre anonymous FTP; format ST.66 XML + TIFF. 🔴 red — violates zero-infra constraint by definition (we'd host an index, not proxy). Primary source Download Madrid Monitor update files.

WIPO API Catalog — no Madrid entries

apicatalog.wipo.int/api/apis/all probe 2026-05-16: 181 APIs total, 4 WIPO-org (Pearl, Hague HWS, GBD image, IPCPUB). No Madrid search API listed — primary-source confirmation that WIPO does not publish one.

Madrid Office Portal (MOP) / Madrid e-Filing (MeF)

Partner-IP-office-only filing and document-exchange surfaces, not search APIs — irrelevant to a third-party proxy. See mm_ld_wg_23_roundtable_1_ib.pdf.

§4 Fees

Madrid fees are charged in CHF and combine a basic fee + complementary or individual fee per designated office + supplementary fee per class beyond three. Renewal cycle is 10 years. Individual fees move per WIPO Information Notices, so the fee calculator is the only authoritative source at any given time.

§5 Access via patent-client-agents

What we cover today

Nothing direct for Madrid. We cover Madrid designations transitively through national TM connectors:

  • patent_client_agents.uspto_odp — US designations of Madrid IRs land in TSDR as US TM applications/registrations.
  • ip_australia_trademarks — AU designations via the IP Australia Trade Marks OAuth API.
  • (Planned — see coverage/atlas.json) — EUIPO TMView for EU designations.

What we should add (if anything)

Nothing for now. Any Madrid connector would require one of: (1) the paid bulk ICC FTP mirror — violates zero-infra; (2) proxying Madrid Monitor — violates ToS §5/§6; or (3) reselling a commercial Madrid aggregator — out of scope. A BYOK config path for clients with their own bulk subscription is possible but not on the roadmap.

Next steps

  • Monitor for a public WIPO Madrid REST/JSON API in the eMadrid Find-and-Monitor decommissioning timeline. WIPO has published its own WIPO Standard on Web API pushing REST/JSON — Madrid is a candidate but not announced.
  • Watch the WIPO API Catalog for a new Madrid entry under organization == "WIPO". We probe this monthly as a side-effect of our broader sweep.

§6 Known unknowns

  • Will eMadrid Find-and-Monitor ship a public API? WIPO's webapi standard suggests it should, but no announcement as of 2026-05-16. Worth a direct email to madrid.assistance@wipo.int.
  • Are the undocumented per-IR XML endpoints stable under the Find-and-Monitor migration? No commitment is published; they could break with the Madrid Monitor decommissioning.
  • Does Madrid Monitor expose a search endpoint behind the JSF UI we haven't found? A 2026-05-16 probe of /api/v1/search?q=test was 404; a deeper look at the UI's actual XHR traffic may reveal more.
  • What is the smallest paid Madrid product? The Download page lists only the CHF 30,000 full feed; is there a per-jurisdiction or per-day pricing tier WIPO offers on request?

§7 References

Last updated 2026-05-16.