MetaDB

Apps and games

Search the Meta store, then open an app to pull its channels and build history. Nothing is stored — every result is what the store says right now.

App	Device	Channel	Price	Version	Build	Date	Dev build

Meta apps

Apps published by Meta.

App	Device	Channel	Price	Version	Build	Date	Dev build

Settings

Kept in this browser only. Nothing is sent anywhere but the store.

Access token

Store search and package lookups need a token belonging to a logged-in account. To get yours: sign in at secure.oculus.com, open your browser's developer tools, and under Application → Storage → Cookies copy the value of the oc_www_at cookie.

Leave it empty to fall back to the built-in public token, which can read public LIVE builds and nothing else. Treat your own token like a password — it signs in as you.

Account token

The oc_ac_at cookie, from the same place. This is the one downloads authenticate with — everything else uses the access token above. Without it, the Download buttons in a build history have nothing to sign with and will point back here instead.

Show app art in search results

Store results include cover art. Off by default, since it means loading an image per result straight from Meta's CDN.

Show the open in store button

The link out to the app's page on meta.com, in each expanded app. On by default.

Show the more app info button

Adds a button to each expanded app that fetches its binary manifest — package name, download size, target SDK, required OS version, permissions and hashes. This is the query a headset runs to work out what to install, so it needs a logged-in account token. Genres, rating and age rating are not here — Check this app brings those in with the build history.

Defaults

Headset Search order Build history order

What the pickers start on. Changing one on a list is just for that visit; these are what it goes back to.

Columns

Applies to both lists, except Price — Meta apps have none, so that column never shows there. Narrow screens still drop the secondary columns to fit, whatever is ticked here.

Relay URL

Required for checks to work from a browser. The store replies with Access-Control-Allow-Origin: https://facebook.com, so this page is refused the response no matter which token is used — that is decided by the page's address, not the token. This is why the same request succeeds in Insomnia or curl, which are not browsers. A relay is a small service you control that fetches the URL and passes it back. Put {url} where the target should go, or leave it off and it will be appended.

Running locally? Start node tools/relay.mjs in the project folder, then .

Data comes from the Meta store. Not affiliated with Meta.