Inquiry and data privacy
Initial inquiries use the operator contact channel. A signed scope defines collection-data access, retention, publication boundaries, authorized reviewers, and deletion or return before any private source data is received.
Concierge pilot
Bring Meta Museum to your collection.
Managed Linked Art Launch Pilot
A fixed-scope onboarding path for collection teams that need a standards-compliant Linked Art API, public browse pages, and a monthly evidence packet without staffing a semantic-web buildout.
Pricing hypothesis: USD 0 evaluation for 10-25 public records; USD 3,500 fixed paid pilot for up to 500 records; implementation from USD 12,000; ongoing service from USD 1,250 monthly. Final scope and pricing stay manual until paid-pilot demand and delivery economics are validated.
Eligibility
Collection stewards need authority to share the proposed records, a named review owner, stable identifiers, and a documented public/private boundary.
Evidence limit
A conversation, draft scope, or sent invoice is not a paid pilot. Only reconciled invoice payment and delivery evidence may support a revenue claim.
One collection export
CSV, JSON, XML, or API-backed source data is mapped into reviewed Linked Art records.
First value in 7 days
The pilot targets a visible browse/search/API slice within the first working week.
Monthly evidence packet
Each pilot receives validation, rights, source, and launch-readiness evidence in a repeatable packet.
Manual invoicing first
No self-serve billing is required before the offer, scope, and support load are proven.
Honest status
A tested offer awaiting its first paid engagement.
Meta Museum currently has 0 paid pilots. The next qualifying evidence is a first signed pilot with a real invoice reference and delivered collection slice; an inquiry or draft scope does not count as revenue or customer proof.
Who it is for
Built for collection teams that need evidence before scale.
Small and mid-size museums
Teams with collection exports and a mandate to publish better public data without a dedicated semantic-web team.
Archives and digital humanities labs
Research groups that need source-backed records, provenance review, and API access for public scholarship.
Artist estates and foundations
Collection stewards that need rights-aware object pages, entity context, and reviewable publication workflows.
Pilot package
A bounded launch path, not an open-ended platform build.
Deliverables
- Linked Art data-quality reportA reviewed summary of mapped records, schema gaps, provenance risks, and rights/reuse flags.
- Hosted browse and API surfacePublic browse pages, provider/source context, record detail pages, and documented JSON endpoints.
- Human review queuesRights, provenance, reconciliation, annotation, and publication issues stay visible before public claims are made.
- Pilot evidence packetA monthly evidence packet covering imports, validation, public trust smoke checks, uptime samples, and unresolved risks.
Data prerequisites
- Source data exportA representative object export with stable identifiers, titles, dates, makers, rights text, and image references when available.
- Named review ownerOne collection-side owner who can answer mapping, rights, and provenance questions during onboarding.
- Publication boundaryA clear decision on what may be public, what needs review, and what must remain internal during the pilot.
Success metrics
The pilot is measured by first value, data quality, and review usability.
Activation
Pilot workspace contains imported, searchable records and at least one reviewed public collection slice within 7 days.
Data quality
Evidence packet shows validation trend, unresolved critical issues, and enrichment coverage for the pilot dataset.
Usability
Non-engineer reviewers can inspect records, rights flags, source context, and export/API outputs without routine developer help.
Support boundaries
Manual pilots first; self-serve waits for validated demand.
Included
One data source, one workspace, onboarding support, mapping review, monthly evidence, and bounded issue triage.
Deferred
Self-serve signup, automated billing, custom integrations, bulk migration guarantees, and tenant-specific feature development.