Artic Edu Art Institute of Chicago API

Name: Art Institute of Chicago API
Brand: Art Institute of Chicago API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationLmsnone97 EndpointsREST

For Agents

Search and fetch artworks, artists, exhibitions, and related collections data from the Art Institute of Chicago — no authentication required.

Install Jentic One Beta

Connect the Art Institute of Chicago API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Art Institute of Chicago 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Art Institute of Chicago API.

Search the artwork collection by query string and filters

Fetch artwork detail records including titles, artists, dates, and images

Search and fetch artists, agents, places, galleries, and exhibitions

GET STARTED

Start building with Art Institute of Chicago API

Explore with Jentic

View OpenAPI Document

The Art Institute of Chicago API is a public, read-only aggregator over the museum's collections data. It exposes 97 endpoints across artworks, artists, agents, places, galleries, exhibitions, sites, events, articles, tours, mobile sounds, publications, sections, products, images, videos, and sounds. Each primary entity supports list and detail operations, and the major collection entities (artworks, artists, agents, places, galleries, exhibitions, sites) also support search. The API is unauthenticated, intended for educational and research use, and serves as an open data layer for museum integrations.

Use Cases

Patterns agents use Art Institute of Chicago API for, with concrete tasks.

★ Educational App Integration

Power a museum education app or classroom tool by searching the Art Institute of Chicago collection through /artworks/search and rendering details from /artworks/{id}. Because the API is unauthenticated, classroom deployments avoid credential management entirely. Strong fit for art history coursework that needs licensed-clean reproductions and curator-written descriptions.

Call /artworks/search with q='impressionism', then for each hit call /artworks/{id} and render title, artist, and primary image url

Cultural Discovery Feed

Build a daily discovery feed for design or art newsletters by pulling new exhibitions, articles, and featured artworks. /exhibitions and /articles surface what's currently on at the museum, while /artworks/search with a date filter can rotate featured pieces. The unauthenticated read model makes it well suited to static site builds.

GET /exhibitions filtered by current date, take the top 5 results, and write them as JSON for a newsletter generator

Tour and Audio Guide Surfacing

Surface museum tours and mobile audio guide content inside a third-party visitor app. /tours and /mobile_sounds expose curated walkthroughs and narration, so partner apps don't need to redesign tour content from scratch.

Fetch /tours, take the first tour, and for each stop GET /artworks/{id} plus /mobile_sounds for the narration audio

Research Catalog Mining

Mine the museum's public catalog for academic research — for example, computing how the artwork collection's coverage of a movement or geography has shifted over time. The /artworks, /artists, /places, and /agents endpoints provide enough metadata to build datasets without scraping HTML.

Page through /artworks filtered by place id, aggregate counts by century, and emit a CSV of works-per-century for a place

Agent-Driven Art Lookup via Jentic

Give an AI assistant a tool that answers art-history questions by calling the Art Institute of Chicago API. The agent searches Jentic for 'search artworks at Art Institute of Chicago', loads the schema for /artworks/search, and executes — with no credentials to manage.

Search Jentic for 'search artworks at Art Institute of Chicago', load the schema, and execute with q='Monet water lilies' to retrieve matching artworks

Key Endpoints

97 endpoints — the art institute of chicago api is a public, read-only aggregator over the museum's collections data.

METHOD

PATH

DESCRIPTION

GET

/artworks

List artworks

GET

/artworks/search

Search artworks by query and filters

GET

/artworks/{id}

Fetch a single artwork

GET

/artists

List artists

GET

/exhibitions

List exhibitions

GET

/galleries/search

Search galleries

GET

/tours

List curated tours

GET

/articles

List published articles

GET

/artworks

List artworks

GET

/artworks/search

Search artworks by query and filters

GET

/artworks/{id}

Fetch a single artwork

GET

/artists

List artists

GET

/exhibitions

List exhibitions

GET

/galleries/search

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Art Institute of Chicago API is unauthenticated, so no credentials are stored. Jentic still routes the call through its execution layer for consistent observability alongside authenticated APIs in the same workflow.

Intent-based discovery

Agents search Jentic with intents like 'search artworks at Art Institute of Chicago' or 'list exhibitions' and Jentic returns the matching operation with input schema — no need to read 97 endpoints of docs to find the right path.

Time to first call

Direct integration: half a day to wire up search, paginate, and stitch image URLs. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Art Institute of Chicago API through Jentic.

What authentication does the Art Institute of Chicago API require?

None for read access. The API is public and unauthenticated for collection browsing and search. The museum requests a User-Agent that identifies your application but does not require an API key. Through Jentic, no credential entry is needed in the vault for this API.

Can I search for artworks by an artist or movement?

Yes. GET /artworks/search accepts a q parameter for free-text search and supports filters such as artist id and date ranges. Combine with /artists/search to resolve artist ids first when needed.

What are the rate limits for the Art Institute of Chicago API?

The museum asks consumers to identify themselves with a meaningful User-Agent and to keep traffic reasonable for an open educational API. There is no hard public rate limit, but cache responses and avoid per-request calls in user-facing loops.

How do I get the image for an artwork?

Each artwork record includes an image_id which can be combined with the IIIF image base URL to produce an image. /images and /images/{id} also expose image asset records directly when you need additional metadata.

How do I search the collection through Jentic?

Run pip install jentic, then search Jentic with 'search artworks at Art Institute of Chicago', load the schema for GET /artworks/search, and execute with your query string. Pagination uses page and limit parameters described in the spec.

Can I list current exhibitions at the museum?

Yes. GET /exhibitions returns exhibitions with date metadata; filter by current date to surface what is on now.

Can I include the API in a commercial product?

The Art Institute of Chicago publishes its data under open terms appropriate for educational and research use. Check the museum's Terms of Use page for the current licensing detail before shipping a commercial product on top of the API.