#ReadAIrr Metadata Source

The current ReadAIrr app repo keeps the original Readarr book model and Goodreads-style identifiers, but it adds a configurable metadata source under Settings => Development.

Some inherited UI text, logs, API fields, and database values still say Goodreads or Readarr. That is expected in the current app code and should be treated as compatibility naming, not a separate service requirement. {.is-info}

#Default Behavior

If no metadata source is configured, the app uses:

https://api.bookinfo.pro

That is the Goodreads-compatible hosted service currently defined in ReadAIrr/App as MetadataSourceConfig.GoodreadsHosted. The current app checkout no longer treats a bundled rreading-glasses sidecar as the default metadata path.

The no-auth review app checked at http://192.168.0.228:8787 on 2026-05-10 still showed older advanced Development help text mentioning automatic self-hosted rreading-glasses and original Readarr metadata. If you see those labels, you are looking at a deployed build that has not caught up with the current App source.

#Metadata Source Options

The current UI options are:

UI option	Value used by the app
`Goodreads hosted`	`https://api.bookinfo.pro`
`Hardcover hosted`	`https://hardcover.bookinfo.pro`
`Custom rreading-glasses URL`	Any valid compatible URL, with `http://rreading-glasses:8788` shown as an example

Use the hosted Goodreads-compatible source for new installs unless you intentionally operate your own compatible metadata service. Use the custom option only when that service is managed outside ReadAIrr and is reachable from the ReadAIrr container or host.

#Testing a Metadata Source

From Settings => Development, use Test Metadata Source after choosing a preset or entering a custom URL. The test uses the unsaved value in the form, so you can verify a new source before saving it.

The current app code:

Treats a blank value as https://api.bookinfo.pro
Accepts HTTP/HTTPS URLs and the backend compatibility value readarr://metadata/original
Checks the author/3389 metadata route
Reports success or failure, response detail, response time, and HTTP status when available

When testing a custom URL, test reachability from the ReadAIrr runtime, not only from your workstation. In Docker, a URL such as http://rreading-glasses:8788 only works if you provide and network that service yourself.

#Custom Metadata URLs

Custom URLs must be valid HTTP or HTTPS URLs. The app trims a trailing slash and appends metadata routes internally.

Use a custom URL only when you run another compatible metadata service and know its route shape matches what ReadAIrr expects.

#Custom rreading-glasses

The current deploy/compose.yml in the App working tree does not create or update rreading-glasses containers. If you want to use rreading-glasses, deploy it separately, keep it updated separately, and point ReadAIrr at its full URL with Settings => Development => Custom rreading-glasses URL.

#Legacy Original Readarr Metadata

readarr://metadata/original still exists in backend validation and request-building code. Treat it as inherited compatibility plumbing, not a recommended ReadAIrr deployment path.