Harvard Art Museums API
45
AI ReadinessFoundational (D)45/100
Official vendor OpenAPI document · agent-readyMediaContent DeliveryapiKey6 EndpointsREST
For Agents
Search and retrieve Harvard Art Museums objects, people, exhibitions, and galleries with a free API key.
Use for: Search Harvard Art Museums for paintings by Rembrandt, Get the full record for object ID 299843, List all exhibitions ever held at the Harvard Art Museums, Find every artist named in the Harvard Art Museums collection
Not supported: Does not handle ticketing, donations, or write-back metadata edits - use for read-only Harvard Art Museums collection lookups only.
The Harvard Art Museums API is a REST-style service that exposes the same collections data that powers the museums' public website, including objects, the people associated with them, exhibitions, and galleries. The API has 6 read-only endpoints covering listings and single-record lookups for objects, persons, exhibitions, and galleries. Authentication is a free API key passed as an apikey query parameter. Image and IIIF media URLs are returned alongside metadata so consumers can render artwork directly from the response.
Install Jentic One Beta
Connect the Harvard Art Museums API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Harvard Art Museums API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fharvardartmuseums.org%2Fharvardartmuseums" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fharvardartmuseums.org%2Fharvardartmuseums" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Harvard Art Museums API.
Search the Harvard Art Museums object collection with rich filters
Fetch a single object record by ID with image and provenance data
List people (artists, sitters, makers) and fetch a single person by ID
List exhibitions held by the Harvard Art Museums
List galleries within the Harvard Art Museums physical space
Use Cases
Patterns agents use Harvard Art Museums API for, with concrete tasks.
★ Educational Collection Browser
Build a teaching tool that surfaces a curated subset of Harvard Art Museums objects with image, title, and credit line by querying GET /object with filters. Each object record returns IIIF image URLs that classroom apps can render directly. The API is free and requires only an apikey query parameter.
Query GET /object with classification 'Paintings' and century '19th' and return the first 20 objects with their primary image URL.
Artist Lookup and Linked Records
Use GET /person to list artists, sitters, and makers in the collection, and GET /person/{id} to retrieve a full biographical record. The same person ID appears on object records, so a UI can chain object > person > other works by the same artist. Useful for biography pages and 'related works' sections.
Get person ID 28017 via GET /person/28017 and then query GET /object with that person's ID to list their works in the collection.
Exhibition Programming Display
List past and current exhibitions for a public-facing exhibitions page by calling GET /exhibition. Each record returns dates, gallery, and a description, which a website or kiosk can render without scraping. Pair with GET /gallery to map exhibitions to physical spaces.
List recent exhibitions via GET /exhibition and pair each with its gallery from GET /gallery for a 'now showing' page.
AI Agent Art Research Assistant
Wire an art research assistant that answers 'show me Dutch Golden Age paintings at Harvard' by calling /object with appropriate filters through Jentic. The free API key is held in your Jentic One instance, and the agent only handles structured object records, never the raw key. The API is read-only, so an agent cannot modify museum data.
When asked 'find Dutch Golden Age portraits', call GET /object with culture 'Dutch' and classification 'Paintings' and return titles, makers, and image URLs.
Key Endpoints
6 endpoints — the harvard art museums api is a rest-style service that exposes the same collections data that powers the museums' public website, including objects, the people associated with them, exhibitions, and galleries.
METHOD
PATH
DESCRIPTION
GET
/object
Search and list objects
GET
/object/{id}
Get a single object by ID
GET
/person
List people
GET
/person/{id}
Get a single person by ID
GET
/exhibition
List exhibitions
GET
/gallery
List galleries
GET
/object
Search and list objects
GET
/object/{id}
Get a single object by ID
GET
/person
List people
GET
/person/{id}
Get a single person by ID
GET
/exhibition
List exhibitions
GET
/gallery
List galleries
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
H
Harvard Art Museums API
- Foundational (D)45/100
85
Foundational Compliance63
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability15
Security58
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
85
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
21%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
58
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
58%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Harvard Art Museums API by hand means appending its apikey query parameter to every call and building each object, person, exhibition, and gallery lookup yourself. Through Jentic you install once, import the Harvard Art Museums API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Harvard Art Museums API is read-only, covering collection lookups like objects, people, exhibitions, and galleries, so scope your agent to the operations it needs, such as searching objects or reading a person by id. You choose what it may call, and there are no write operations for it to reach.
Credential isolation
Your Harvard Art Museums API key is stored once, encrypted, by your own Jentic One instance and appended as the apikey query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search harvard art museums for paintings', and Jentic returns the GET /object operation with its input schema and filter parameters so the agent calls the right endpoint without crawling the api-docs repo on GitHub.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Harvard Art Museums API through Jentic.
What authentication does the Harvard Art Museums API use?
The API uses an API key passed as the apikey query parameter on every request. Keys are issued for free by the Harvard Art Museums. Through Jentic the key is stored in the encrypted vault and appended to each call, so it never enters the agent's prompt context.
Can I retrieve full image URLs for artworks via this API?
Yes. GET /object and GET /object/{id} return primary image URLs and IIIF service URLs in each object record, so a downstream UI can render the artwork without a separate image lookup. Image rights vary per object and are reflected in the record's metadata.
What are the rate limits for the Harvard Art Museums API?
The Harvard Art Museums applies fair-use throttling rather than a hard published quota. Their developer documentation requests considerate use and back-off on errors. Expect HTTP 429 if a client bursts well above ordinary read traffic.
How do I search for paintings through Jentic?
Search Jentic for 'search harvard art museums objects', load the schema for GET /object, and execute with classification 'Paintings' plus any culture or century filter. Run pip install jentic and use the async client.search, client.load, and client.execute pattern.
Does the Harvard Art Museums API support write operations like submitting metadata?
No. The API is read-only across all six endpoints. Crowdsourced metadata corrections go through a separate editorial process at the museums; this API only exposes the published, curated collection.
Can I limit what my agent is allowed to do with the Harvard Art Museums API?
Yes. Because Jentic One is self-hosted, you write the rules that decide which operations and credentials your agent may use, so you can scope it to just the reads it needs, such as searching objects with GET /object or reading a person by ID with GET /person/{id}, while withholding exhibition or gallery lookups. The API is read-only across all six endpoints, so there are no write operations for the agent to reach even if it tried. Your free API key stays in your own Jentic One instance and is appended as the apikey query parameter at execution time, so the agent never sees the raw key.
GET STARTED