Museum data for AI agents

Pay per request.
Research on demand.

A museum-data API designed for autonomous agents. Search artworks, retrieve exhibits, find related works, browse collections and run live museum research — paid automatically with USDC.

View pricing Quick start

Simple pay-per-use pricing

No subscription. No credit card. Agents pay only for the data they actually use.

GET /museum-exhibit
$0.03
Detailed information about one museum work.
GET /museum-search
$0.05
Search museum data by artist, museum, period or type.
GET /museum-collection
$0.08
Paginated access to the available collection.
GET /museum-related
$0.10
Discover related works across the collection.
GET /museum-research
$0.50
Higher-value live museum research for agents.
eip155:8453
Base
Payments settle in USDC through x402.

Built for autonomous agents

The agent makes the request, receives a payment requirement, pays in USDC, and gets the data back.

Example: search 
GET /museum-search?artist=Vincent%20van%20Gogh
limit=5
offset=0

Returns structured museum records with source URLs and metadata.

Example: research 
GET /museum-research?q=Vincent%20van%20Gogh

Falls back to live The Met research when the local collection does not contain the query.

How payment works

1
Request

Your agent calls a protected museum endpoint.

2
Pay

x402 returns the payment requirement and the agent pays in USDC.

3
Receive

The API validates payment and returns structured museum data.

Data sources

The service currently combines a curated museum collection with public-domain records from The Metropolitan Museum of Art.

Curated collection

Selected Louvre and British Museum records with source links.

The Metropolitan Museum of Art

Public-domain records and live research search.

Payment destination

Payments settle to the service's Base USDC receiving wallet.

0x8480d766aec80e2cbc213bcd25f5d05e43702478

Why agents use this

Pay only when needed

Agents can buy one lookup or one research call instead of maintaining a subscription.

Machine-readable data

Responses are structured JSON instead of scraped pages.

Source-aware

Museum records include source URLs and provenance fields.

Start building

Connect an x402-compatible agent, point it at the API and pay only for successful data requests.

Check API health