Name the country, language, and place you want to target and ask AI to organize matching identifiers.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Resolve named targets into the supported identifiers for your workflow.
/oo Autom: Use Autom to find Google settings matching country [country], language [language], and place [city or region]. Return their identifiers and show ambiguous location matches for selection.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect your Autom API key.
Connect Autom →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Autom’s finder operations return supported Google localization choices. The action set here prepares geographic and language inputs rather than retrieving search results.
Find supported countries, languages, and geographic location identifiers.
Get current Autom credit usage, subscription quota, rate limits, account metadata, and API key metadata.
Leina 
Wanta 
autom.get_usage Search supported Google countries in Autom and return matching country codes.
autom.find_google_countries Search supported Google languages in Autom and return matching language codes.
autom.find_google_languages Search supported Google locations in Autom and return matching location IDs.
autom.find_google_locations No matching tools.
Yes. Each finder accepts search text and returns matching identifiers. Provide a full region name when a city is ambiguous.
Pass the selected identifiers to your existing localized search workflow. Retain their names so the target region and language remain understandable.
The current actions provide localization lookups and account usage data, not search results.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.