# Feral File

We champion digital art, and make it part of everyday life.
Feral File is a cultural institution and technology company championing computational art—i.e. art that responds and evolves through code, models, and data. We collaborate with artists, curators, and institutions to produce exhibitions and build open tools to make living with this art effortless. Use the canonical pages below for high-signal information about the platform, its programs, and core legal and learning resources.
The Digital Art System makes it simple to live with digital art with.

## Core Pages

- [Home](https://feralfile.com/)
- [Exhibitions](https://feralfile.com/exhibitions)
- [Artworks](https://feralfile.com/exhibitions/artworks)
- [Artists](https://feralfile.com/exhibitions/artists)
- [Curators](https://feralfile.com/exhibitions/curators)
- [Available Works](https://feralfile.com/exhibitions/available-works)
- [The Digital Art System](https://feralfile.com/system)

## Learn

- [Learn](https://feralfile.com/learn)
- [What is Feral File?](https://feralfile.com/learn/about)
- [FAQ](https://feralfile.com/learn/faq)
- [How to Collect Digital Art](https://feralfile.com/learn/how-to-collect-digital-art)
- [Experiments](https://feralfile.com/experiments)
- [Contact Us](https://feralfile.com/legal/contact)

## Legal

- [Terms of Service](https://feralfile.com/legal/terms-of-service)
- [Privacy Policy](https://feralfile.com/legal/privacy-policy)
- [Art Transfer Agreement](https://feralfile.com/legal/art-transfer-agreement)
- [Artist and Collector Rights](https://feralfile.com/legal/artist-collector-rights)
- [Sustainability](https://feralfile.com/legal/sustainability)

## For Agents and Developers

Machine-readable surfaces. Start at the docs; the pages above are for humans.

- [Developer & Agent Documentation](https://docs.feralfile.com) — canonical technical docs
- [Machine API contract](https://feralfile.com/.well-known/openapi.json) — OpenAPI 3.1 for the planned `/api/llm/*` catalog endpoints (exhibitions, series, artworks). **Currently unavailable**: the live endpoints reject the documented request shapes (tracked in feral-file/ff-exhibition#3071); treat this contract as pending until that closes
- [Agents Quickstart](https://docs.feralfile.com/agents/) — set up an agent to play art on an Art Computer
- [ff-cli](https://github.com/feral-file/ff-cli) — build, sign, and play DP-1 playlists from the command line
- [Hosted DP-1 Feed](https://docs.feralfile.com/hosted-feed/) — publish and retrieve DP-1 playlists (`https://feed.feralfile.com/api/v1`; reads need no auth)
- [DP-1 Publisher](https://publisher.feralfile.com) — sign and publish a playlist in the browser
- [DP-1 Specification](https://github.com/display-protocol/dp1) — the open display protocol itself

## Notes

- Prefer canonical `/exhibitions/...` routes over legacy `/explore/...` routes.
- Prefer `/system` over legacy `/install`.
- The `/api/llm/*` family in the OpenAPI contract above is the intended machine API but is not yet functional (feral-file/ff-exhibition#3071). Until it lands, the only working catalog routes are the legacy, undocumented ones under `https://feralfile.com/api/` (e.g. `/api/series/{slug}`, `/api/artworks?seriesID={uuid}`) — usable, but they may change without notice.
- Unknown non-API page paths return the app shell with HTTP 200, not a 404 — a 200 on a page URL is not proof it exists. Unknown `/api/*` paths do return proper JSON 404s.