Cooper Hewitt Smithsonian Design Museum API

Name: Cooper Hewitt Smithsonian Design Museum API
Brand: Cooper Hewitt Smithsonian Design Museum API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey1 EndpointsREST

For Agents

Install Jentic One Beta

Connect the Cooper Hewitt Smithsonian Design Museum API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cooper Hewitt Smithsonian Design Museum 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 Cooper Hewitt Smithsonian Design Museum API.

Search the Cooper Hewitt collection for objects by keyword, period, type or role

Retrieve full metadata for a specific design object including credit lines and provenance

List exhibitions a person has appeared in or curated at the Smithsonian Design Museum

GET STARTED

Start building with Cooper Hewitt Smithsonian Design Museum API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Cooper Hewitt Smithsonian Design Museum API, keeping it validated and agent-ready. The Cooper Hewitt API exposes the Smithsonian Design Museum's collection of objects, people, exhibitions, periods, types and roles through a single REST endpoint dispatched by a method query parameter. Collection data (excluding images) is released under Creative Commons Zero, so agents can fetch and reuse object records, biographies, exhibition lists and image URLs freely. Authentication uses an access token passed as a query parameter, and responses are returned as structured JSON suitable for downstream cataloguing or RAG pipelines.

Use Cases

Patterns agents use Cooper Hewitt Smithsonian Design Museum API for, with concrete tasks.

★ Design History Research Assistant

Researchers and educators can query Cooper Hewitt for objects, makers and exhibitions to assemble citation-ready evidence for design history projects. The API dispatches every call through one root endpoint with a method parameter such as cooperhewitt.objects.getInfo, returning structured JSON that downstream RAG pipelines can chunk and index. Because collection metadata is CC0, results can be redistributed in derivative works without licensing friction.

Call cooperhewitt.objects.search with query 'Eames chair' and return the top five matching object IDs with their titles and dates.

Cultural Heritage Cataloguing

Catalogue platforms and aggregators can pull Cooper Hewitt records to enrich their own holdings with cross-referenced design objects. The dispatch pattern means a single base URL covers every method, simplifying integration for batch ingestion. Image URLs returned under CC0 can be cached locally for thumbnail rendering.

Fetch metadata for object ID 18382347 and extract title, accession number, credit line and primary image URL.

Exhibition Discovery for Education Tools

Learning apps focused on design education can surface relevant Cooper Hewitt exhibitions and the people involved with them when a learner asks about a designer or movement. The exhibitions and people methods return linked records, enabling navigation from a designer to their exhibitions and back to other contributors.

Look up the people record for 'Charles Eames' and list the IDs and titles of every Cooper Hewitt exhibition he has appeared in.

AI Agent Collection Browsing

An AI agent can answer natural-language questions about the Cooper Hewitt collection by translating intents into method names and dispatching them through Jentic. The agent receives validated input schemas for each method, so it can construct queries against periods, types and roles taxonomies without reading the docs site.

Use Jentic to search Cooper Hewitt for objects of type 'poster' from period '1960-1969' and return five results with titles and image URLs.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for cooper hewitt smithsonian design museum api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

Dispatch root that executes any Cooper Hewitt API method via the method query parameter

GET

Dispatch root that executes any Cooper Hewitt API method via the method query parameter

Why Jentic?

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

Credential isolation

Your Cooper Hewitt access token is stored once, encrypted, by your own Jentic One instance and injected as a 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 the Cooper Hewitt collection' or 'get museum object info', and Jentic returns the dispatch operation with its input schema and method-name guidance so the agent picks the right method without browsing the reference docs.

Time to first call

FAQs

Specific to using Cooper Hewitt Smithsonian Design Museum API through Jentic.

Why is there no official OpenAPI spec for Cooper Hewitt Smithsonian Design Museum API?

Cooper Hewitt does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cooper Hewitt Smithsonian Design Museum API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Cooper Hewitt Smithsonian Design Museum API use?

The API uses an access token passed as a query parameter on each call. Through Jentic the token is stored in the credential vault and injected at execution time, so the raw access token never enters agent context.

Can I search for objects by period or type with the Cooper Hewitt API?

Yes. The single dispatch endpoint accepts a method parameter such as cooperhewitt.objects.search with filters for period, type, role and free-text query, returning matching object IDs, titles, dates and image references.

Are the images returned by the Cooper Hewitt API free to use?

Collection metadata is released under Creative Commons Zero. Image rights vary per object, so check the rights field returned with each object record before redistributing image files.

How do I integrate the Cooper Hewitt Smithsonian Design Museum API with an agent through Jentic?

Run pip install jentic, then have the agent search Jentic with a query such as 'search Cooper Hewitt collection', load the returned operation schema, and execute it against the / dispatch endpoint with the chosen method name.

What rate limits apply to the Cooper Hewitt Smithsonian Design Museum API?

The OpenAPI spec does not declare formal rate limits. Treat the service as best-effort, back off on HTTP 429 responses, and cache object records locally where possible since collection metadata changes slowly.

Can I limit what my agent is allowed to do with the Cooper Hewitt Smithsonian Design Museum API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API routes every call through a single read-only dispatch endpoint where the collection method travels in the request, so you scope access by operation: allow only the specific collection reads the agent needs, such as searching objects or fetching an object record, and withhold the rest. Since the API is read-only, the approved set stays confined to the lookups you permit and cannot write or change any data.