Two archives, queried live.
Every record below comes from The Met or Smithsonian Open Access and was filtered on that archive’s own rights field before it reached this page. 15 shown for “Indo-Persian carpet with vine scroll and palmette pattern” — 29 records examined, 3 dropped by the rights gate.
Archives queried 2026-08-28 06:59 UTC · fetched live for this request
isPublicDomain field is true for this object.metadata_usage.access reads CC0 — a waiver, not an expired term.
Indo-Persian carpet with vine scroll and palmette pattern
Artist not stated in the record · second half of the 17th century

Textile
Cheney Brothers, South Manchester, Connecticut, USA · ca. 1915

Indo-Persian carpet with vine scroll and palmette pattern
Artist not stated in the record · second half of the 17th century

Frieze
F. E. James Co., New York, New York · 1905–1915

Indo-Persian carpet with vine scroll and palmette pattern
Artist not stated in the record · middle of the 17th century

Fragment
Artist not stated in the record · 17th century

Indo-Persian carpet with vine scroll and palmette pattern
Artist not stated in the record · ca. 1625 (or earlier)

The Emperor's Carpet
Artist not stated in the record · second half 16th century

Carpet with Palm Trees, Ibexes, and Birds
Artist not stated in the record · late 16th–early 17th century

Carpet with Scrolling Vines and Blossoms
Artist not stated in the record · ca. 1650

Indo-Persian carpet with repeat pattern of vine scrolls and palmettes.
Artist not stated in the record · second half of the 17th century

Vase-technique Carpet with Overlapping Cartouches
Artist not stated in the record · 17th century

Vase Carpet
Artist not stated in the record · late 16th–early 17th century

Indo-Persian carpet with repeat pattern of vine scrolls and palmettes
Artist not stated in the record · second half of the 17th century

Carpet with vine scroll and palmette pattern
Artist not stated in the record · late 19th century
Where these records came from.
Two archives are wired, and only two. Each one is filtered on its own rights field — never on a title match, and never on the presence of an image file.
- The Met Collection API (Open Access)Rights field:
isPublicDomain. 57 matched · 24 examined · 1 dropped by the rights gate. Kept only where isPublicDomain === true and a file URL was published.12 shown - Smithsonian Open Access API (api.si.edu)Rights field:
content.descriptiveNonRepeating.metadata_usage.access. 5 matched · 5 examined · 2 dropped by the rights gate. Kept only where metadata_usage.access === "CC0" and an image resource was published.3 shown
These figures describe the pass run at 2026-08-28 06:59 UTC, during this request. A completed pass is kept for 24 hours and replayed for an identical search, which is what keeps repeated queries inside Smithsonian’s 30-requests-per-hour allowance. A pass in which either archive failed to answer is never kept — an outage must not be replayed as though it were a finding about the catalogue.
Wikimedia Commons and the Library of Congress are deliberately not wired. Wikimedia was confirmed, on a live query, to return CC-BY material inside the same result set as genuine public domain works, and filtering it safely has not been designed yet. loc.gov was blocked by bot detection during the source evaluation, so its rights vocabulary has never been observed — and nothing here is built on a field nobody has read.
An image file is a rights claim. It never travels without its field.