Compare Device Details
Search candidate devices, then read their specifications for comparison.
/oo AppleDB: Search AppleDB for “[device name]”. Read records [selected device keys] and compare their identifiers, processor, and release data.
Search by device name or build version, then inspect the records relevant to your hardware research.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Search candidate devices, then read their specifications for comparison.
/oo AppleDB: Search AppleDB for “[device name]”. Read records [selected device keys] and compare their identifiers, processor, and release data.
Read an identified OS build and summarize associated versions and devices.
/oo AppleDB: Read AppleDB operating system [OS name], build [build key], including sources. Summarize release details and compatible device records listed.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Use AppleDB without an account credential.
Connect AppleDB →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
AppleDB supplies device and operating-system build records. This integration searches those records and retrieves their details.
Search device names and identifiers or retrieve a record by key.
Search firmware calendar records and retrieve build metadata.
Get an Apple device record by its case-sensitive AppleDB key, such as iPhone17,1.
appledb.get_device Search AppleDB devices by name, key, identifier, model, board, or processor.
appledb.search_devices Get an Apple operating system build record by its AppleDB operating system name and build key.
appledb.get_os_build Search an AppleDB firmware calendar by version, build, device identifier, or release text; results are newest first.
appledb.search_os_builds No matching tools.
Search by name, identifier, model, board, or processor, then use the returned case-sensitive key to retrieve details.
Treat it as AppleDB metadata. Check the source and update context before using recorded signing information as a current status.
Results include total matches and a truncation flag. Ask the assistant to state the search coverage rather than treating a limited list as complete.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.