neimo.

Compare a regulatory domain side-by-side across multiple markets. Accepts individual ISO country codes (US, JP, KR) or region aliases (EU, APAC, LATAM, MENA) which are automatically expanded to their member countries. For a global "which countries / where / globally" question, pass markets:["*"] to sweep EVERY market in the KB instead of a hand-picked list; pair it with a filter (e.g. filterType="eq", filterValue="15") so the matches stay focused. Returns one row per (market, field, column) triple from the gaming-social-media KB; multi-column fields (e.g. behavioral vs contextual advertising) produce multiple rows per market with the column name in `row.column`. Capped at 50 rows shared fairly across markets (round-robin per market, not an alphabetical slice). When metadata.truncated is true, metadata.returnedMarkets/omittedMarkets/partialMarkets report which markets are fully covered, dropped entirely, or only partially shown; never present a truncated comparison as complete — tell the user which markets were omitted and offer to query them in a follow-up batch. Optional numeric/text filters apply per column, so a market can pass on one column and be excluded on another (e.g. filterType="gt", filterValue="13" to find markets where an age threshold exceeds 13). When a filter is supplied, rows that did not satisfy it are returned in metadata.excludedRows (each with a reason such as "value 13 did not satisfy gt 13" or "value is not numeric", plus the column name); surface these to the user when relevant so they understand which (market, column) pairs were excluded and why. Use this when you need cross-jurisdictional differences for a specific regulatory topic.

compare_regulations

List all regulatory sections (domains) available for a given market in k-ID's knowledge base. Returns { sections: [{ sectionName, sectionKey, rowCount }, ...], metadata?: { message, didYouMean } }. Call this before lookup_regulation or compare_regulations when you are unsure what section names exist for a country: using an incorrect section name returns empty results. When the market is unknown, sections is empty and metadata.didYouMean lists likely intended ISO codes. Example output: { sections: [{ sectionName: "Age Thresholds", sectionKey: "age-threshold", rowCount: 5 }, ...] }.

discover_sections

Retrieve the full text content of a regulatory source URL. First checks k-ID's cache of pre-downloaded primary sources (laws, directives, government guidance). If not cached, fetches the page live, extracts the main content area (article/main), strips navigation and boilerplate, and returns clean text. Content is capped at ~4000 characters. Only supports HTML pages (not PDFs or binary files). Use this when other tools return reference URLs and you need to read the actual regulatory text, or when a user provides a URL and asks what it says.

fetch_source_content

Get a comprehensive regulatory overview of a single market by returning all data rows across every section in the gaming-social-media knowledge base for that country. For k-ID internal callers each row also carries `row.lastUpdated`, an ISO timestamp of the last published change to that row's values (null when unknown), so you can report how current each part of the profile is. Results are paged 50 rows at a time: when metadata.truncated is true, call again with offset=metadata.nextOffset to retrieve the remaining rows, or follow up with lookup_regulation on specific sections of interest. Use this for a high-level snapshot of a country's children's digital safety landscape including age thresholds, consent requirements, data protection rules, and enforcement status.

market_profile

Keyword (ILIKE) search across k-ID's structured knowledge base cells (description + details). Ranks rows by the number of distinct query keywords matched, then by content length, and returns up to 15 enriched rows. Each result includes the actual cell content, reference URLs, a 1-indexed rank field (1 = best match), and matchType="keyword". NOTE: despite the name, this tool does NOT use vector embeddings. For true semantic / meaning-based search, use search_primary_sources, which queries pgvector embeddings on downloaded primary source documents. Best for: enforcement actions and settlements (e.g. "FTC Fortnite COPPA settlement"), specific laws or company actions, cross-cutting queries where you don't know which section to look in. Prefer lookup_regulation for structured queries where you know the exact market and section.

search_kb_semantic

List the published edits to k-ID's structured knowledge base within a time window, sourced from the applied change log. Works for one market, several markets, or all markets at once (omit market/markets for everywhere). Each row is one edit event with `changedFields` saying exactly what changed: "value" means the regulatory answer itself changed (with `valueBefore` → `valueAfter`); "description"/"details"/"necessity" are annotation rewording; "citations" is citation attachment changes; "status"/"effectiveFrom" are lifecycle edits. Report changedFields honestly — an annotation or citation edit is NOT a change to the regulatory value. By default (scope "values") only value changes are returned; excluded edits are counted in metadata.annotationOnlyCount/citationOnlyCount/lifecycleOnlyCount, and scope "all" returns them too. `changeType` is create/update/delete (`valueBefore` null for creates, `valueAfter` null for deletes). Rows carry section, field, column, sub-jurisdiction, verification status, the publish `publishedAt` timestamp (newest first), and `effectiveFrom`/`pending` — when `pending` is true the change is published but only takes effect on the future `effectiveFrom` date. metadata.publishes lists publish events with their public change notes; metadata.perMarket reports per-market totals when the 50-row budget was shared round-robin across markets. Defaults to the last 30 days when no window is supplied. metadata.scanLimited means the window held more changes than could be scanned — narrow the window or markets; metadata.historyStartsAt appears when the window predates the change log, so earlier edits cannot be reported. Use this for "what changed / what is new" questions about k-ID's own structured data (e.g. "what changed everywhere last week?"); use lookup_legal_horizons for newsletter coverage.

lookup_recent_updates

Internal-only. Search k-ID's Legal Development Tracker (a.k.a. legal development timeline / legal horizon regulation events) for upcoming and recent regulatory developments per jurisdiction, with effective dates, tags, and structured sections (what it is, who it applies to, partner requirements, and what it means for sales/GTM, product, gaming clients, and social media clients). Returns an empty result for non-internal callers.

lookup_regulation_events

Query k-ID's structured knowledge base for a specific regulatory requirement in one market. Returns rows from the gaming-social-media KB matching the given section (domain) and optional subsection (field). When a field has multiple columns (e.g. behavioral vs contextual advertising thresholds), each column is returned as its own row with the column name in `row.column`. Each row contains the regulatory value, reference URLs, and verification status. k-ID internal callers additionally get `row.lastUpdated`: an ISO timestamp of the last published change to that row's values, null when unknown. An old lastUpdated means the value has not been re-published since then, not that it is wrong. Results are paged 50 rows at a time: when metadata.truncated is true, call again with offset=metadata.nextOffset to retrieve the remaining rows — never present a truncated page as the complete section. Returns empty if the section name is wrong; call discover_sections first to see what sections exist for a market. Use this when you need a specific fact (e.g. digital consent age, parental consent rules) for one country.

lookup_regulation

Query the US state laws database for children's privacy and online safety legislation. Covers state-level laws (e.g. California AADC, Texas HB 18, Utah Social Media Regulation Act) and federal laws (COPPA, KOSA). Returns law name, status (Active/Pending/Blocked/Challenged), effective date, key changes summary, age assurance requirements, targeted ad opt-out rules, privacy rights (access, deletion, correction, portability), DPIA requirements, and source URLs. Returns the complete untruncated list so you can count accurately. Accepts full state names ("California"), 2-letter codes ("CA"), or "FEDERAL"/"US" for federal laws. Omit the state parameter to return all laws across all states.

lookup_state_laws

Returns the full glossary of Market Insights metrics with display names and definitions. Use this to understand what each metric measures before calling lookup_market_insights. When responding to the user, include the relevant metric definition the first time each metric appears so they have the correct context for what the numbers mean. Weave it in naturally rather than dumping the full glossary.

get_metric_glossary