Mlkit Agent API
Android (Google)OfficialCreated by Google LLCDistributed by Android (Google)
- Skill
- Tool integration
- Data and AI
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The ML Kit GenAI Agent API enables developers to create autonomous agentic workflows directly on Android devices using Gemini Nano and AICore. This skill provides patterns for implementing conversational agents, managing multi-turn chat sessions within ViewModels, and integrating local tools via Android AppFunctions. It focuses on orchestrating reasoning loops, handling typed tool dispatch, and managing session persistence while ensuring proper error handling for on-device AI operations.
What it does
- Implements multi-turn conversational agents using AgentSession.
- Integrates local tools through Android AppFunction declarations.
- Supports ephemeral single-turn execution for quick tasks.
- Provides patterns for session lifecycle management in Android ViewModels.
- Handles GenAiException for robust error resilience.
- Enables advanced tool discovery and decorator patterns for custom logic.
When to use it
- When building conversational agents that require on-device reasoning.
- When you need to integrate local app functions as tools for an AI agent.
- When managing complex multi-turn dialogues that must persist across configuration changes.
- When performing one-off tasks like summarization or data formatting without session history.
Advantages
- Enables on-device agentic workflows without requiring cloud connectivity.
- Leverages standard Android AppFunctions for tool definitions.
- Provides structured lifecycle management for conversational sessions.
- Supports deterministic tool selection via greedy decoding.
Usage examples
- “How do I initialize an agent for a chat interface in an Android ViewModel?”
- The agent is initialized using Agent.builder, wrapped in an AgentRunner, and the session is managed within the ViewModel to ensure persistence and proper cleanup.
- “How can I register a local function as a tool for my agent?”
- Annotate the function with @AppFunctionDeclaration and enable AppFunctions in the Agent.Builder to allow the agent to discover and call the tool.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/android/mlkit-agent-api/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip mlkit-agent-api.zip -d .agents/skills
Documentation by Google LLC
Targeting AICore Developer Preview. This skill provides authoritative execution patterns and failure-prevention rules for on-device agentic workflows in Android apps.
1. Prerequisites and setup
Gradle dependencies
// app/build.gradle.kts
dependencies {
// Core ML Kit GenAI Agent API
implementation("com.google.mlkit:genai-agent:1.0.0-alpha1")
// Android AppFunctions dependency for on-device tool declarations
implementation("androidx.appfunctions:appfunctions:1.0.0-alpha13")
}[!IMPORTANT] Always use official SDK interfaces from
com.google.mlkit.genai.agent.*,androidx.appfunctions.*,com.google.mlkit.genai.prompt.*, andcom.google.mlkit.genai.common.*. Never declare local placeholder interfaces or fallback mocks.
2. Minimal agent and runner initialization
Configure an Agent with Agent.builder and wrap execution in AgentRunner:
import com.google.mlkit.genai.agent.Agent
import com.google.mlkit.genai.agent.AgentRunner
val agent = Agent.builder()
.setName("OnDeviceAssistant")
.setInstructions("You are a helpful on-device assistant.")
.build()
val runner = AgentRunner(agent)Agent.builderdefaults tomaxTurns = 10automatically to prevent infinite tool loops.AgentRunnerdefaults to greedy decoding (temperature = 0.0f) for deterministic tool selection and schema compliance.AgentRunner(agent)automatically resolves application context usingMlKitContextfor AppFunction execution in Android apps. An explicitAgentRunner(context, agent)overload is available for headless tests or custom context scopes.
3. Multi-turn chat and lifecycle (ViewModel)
AgentSession preserves conversational history in memory and is not
Parcelable . To preserve dialogue history across Android configuration
changes (such as screen rotation), retain session inside an AndroidX
ViewModel.
When executing single-turn ephemeral queries, managing concurrent multi-sessions, or requiring explicit RAM cleanup, you must follow the guidelines in Session lifecycle.
package com.example.app
import androidx.lifecycle.ViewModel
import androidx.lifecycle.viewModelScope
import com.google.mlkit.genai.agent.Agent
import com.google.mlkit.genai.agent.AgentRunner
import com.google.mlkit.genai.agent.AgentSession
import com.google.mlkit.genai.agent.textTokens
import com.google.mlkit.genai.common.GenAiException
import com.google.mlkit.genai.prompt.Content
import kotlinx.coroutines.flow.MutableStateFlow
import kotlinx.coroutines.flow.StateFlow
import kotlinx.coroutines.flow.asStateFlow
import kotlinx.coroutines.launch
class ChatViewModel : ViewModel() {
private val agent = Agent.builder()
.setInstructions("You are a helpful on-device assistant.")
.build()
private val runner = AgentRunner(agent)
private val session: AgentSession =
runner.getOrCreateSession("chat_session")
private val _uiState = MutableStateFlow<ChatUiState>(ChatUiState.Idle)
val uiState: StateFlow<ChatUiState> = _uiState.asStateFlow()
fun sendMessage(prompt: String) {
viewModelScope.launch {
_uiState.value = ChatUiState.Loading("")
try {
// Content.builder() required; runAsync takes Content
val content = Content.builder().text(prompt).build()
var fullResponse = ""
session.runAsync(content)
// Extension function requiring textTokens import
.textTokens()
.collect { token ->
fullResponse += token
_uiState.value = ChatUiState.Loading(fullResponse)
}
_uiState.value = ChatUiState.Success(fullResponse)
} catch (e: GenAiException) {
// Catch GenAiException to prevent app crashes on AI errors
val err = e.localizedMessage ?: "AI error (${e.errorCode})"
_uiState.value = ChatUiState.Error(err)
}
}
}
override fun onCleared() {
super.onCleared()
// Evict conversation session from RAM when ViewModel is destroyed
session.close()
}
}Essential lifecycle and coroutine rules
Contentobject :session.runAsyncandrunner.runSingleTurnAsyncrequire aContentobject. Always build it usingContent.builder().text(userPrompt).build().textTokensextension :textTokensis a Kotlin extension function onFlow<AgentEvent>. Always includeimport com.google.mlkit.genai.agent.textTokens.Session cleanup : Always invoke
session.closeinViewModel.onClearedto evict conversational RAM and cancel pending tasks.AgentEventstream : When collectingFlow<AgentEvent>directly instead oftextTokens, always includeimport com.google.mlkit.genai.agent.AgentEvent. Match againstAgentEvent.TextMessage(text, isPartial),AgentEvent.FunctionCall(name, args), andAgentEvent.FunctionResponse(name, response), and always include anelse -> {}branch inwhen (event)expressions (AgentEventis non-exhaustive for forward compatibility):import com.google.mlkit.genai.agent.AgentEvent
session.runAsync(content).collect { event -> when (event) { is AgentEvent.FunctionCall -> { _uiState.update { it.copy(activeToolStatus = "Tool started: ${event.name}") } } is AgentEvent.FunctionResponse -> { _uiState.update { it.copy(activeToolStatus = "Tool completed: ${event.name}") } } is AgentEvent.TextMessage -> { _uiState.update { it.copy(responseText = it.responseText + event.text) } } else -> {} // Required: AgentEvent is non-exhaustive for forward compat } }
4. Tool calling recipe
All tools used with Agent originate from Android AppFunctions
(@AppFunctionDeclaration), registered using the declarative path
(enableAppFunctions(true) or addAppFunctionIds(...)) or advanced discovery
(AppFunctionAgentTools.discover(...)).
When you need to restrict caller access levels for private in-app tools or wrap discovered AppFunctions with human-in-the-loop (HITL) confirmation decorators, you must consult Tools and functions.
Option A: Declarative AppFunctions path
Define tools declaratively in your app using AndroidX AppFunctions:
package com.example.app.tools
import androidx.appfunctions.AppFunctionDeclaration
import androidx.appfunctions.AppFunctionSerializable
@AppFunctionSerializable
data class CalendarEvents(val date: String, val events: List<String>)
class CalendarTools {
/**
* Fetches scheduled calendar appointments for a specific date in
* YYYY-MM-DD format.
*
* @param date Date string in YYYY-MM-DD format
*/
@AppFunctionDeclaration(isDescribedByKDoc = true)
fun fetch_calendar(
date: String
): CalendarEvents {
return CalendarEvents(
date = date,
events = listOf(
"Team Standup at 10:00 AM",
"Product Review at 2:00 PM"
)
)
}
}Enable AppFunctions on Agent.Builder and initialize AgentRunner:
import com.google.mlkit.genai.agent.Agent
import com.google.mlkit.genai.agent.AgentRunner
val agent = Agent.builder()
.setName("CalendarAssistant")
.setInstructions("You assist with calendar queries.")
// Automatically discovers AppFunctions in your app package
.enableAppFunctions(true)
// Optional: scope to specific function IDs or method names
.addAppFunctionIds("fetch_calendar")
.build()
val runner = AgentRunner(agent)AppFunction Contract : Tool methods take domain parameters directly (no framework context parameter required). Returns must be primitives or
@AppFunctionSerializabledata classes (Map<String, Any?>isn't supported for AppFunctions).Restricting Callers with
ACCESS_LEVEL_SELF: AppFunctions don't have to be public to external callers. To restrict execution strictly to your app's internal agent (blocking external system assistants and IPC callers), annotate with@OptIn(ExperimentalAppFunctionsApi::class)and@AppFunctionAccessLevel(level = AppFunctionMetadata.ACCESS_LEVEL_SELF, isCompatEnforcementEnabled = true).
Option B: Advanced discovery and decorator pattern
For inspecting, filtering, or decorating discovered AppFunctions (such as
Human-in-the-Loop confirmation wrappers using AgentTool(delegate)) before
registering with the agent:
import com.google.mlkit.genai.agent.Agent
import com.google.mlkit.genai.agent.AgentRunner
import com.google.mlkit.genai.agent.AgentTool
import com.google.mlkit.genai.agent.AppFunctionAgentTools
// Discover tools (optionally scoped to function IDs)
val discoveredTools = AppFunctionAgentTools.discover(
enabledAppFunctionIds = listOf("fetch_calendar")
)
// Optional: Wrap sensitive tools using AgentTool(delegate) decorator
class HitlConfirmationTool(
delegate: AgentTool,
private val onConfirm: suspend (
toolName: String,
args: Map<String, Any>
) -> Boolean
) : AgentTool(delegate) {
override suspend fun execute(args: Map<String, Any>): Map<String, Any?> {
if (!onConfirm(name, args)) {
return mapOf("status" to "CANCELLED_BY_USER")
}
return checkNotNull(delegate).execute(args)
}
}
val agent = Agent.builder()
.setName("CalendarAssistant")
.setInstructions("You assist with calendar queries.")
.addTools(discoveredTools)
.build()
val runner = AgentRunner(agent)[!WARNING] Mutual exclusivity : Configure AppFunctions using either the declarative path (
enableAppFunctions(true)onAgent.Builder) or the advanced path (AppFunctionAgentTools.discoverpassed toaddTools), but not both. Using both simultaneously triggers a warning and registers duplicate tool schemas.
Deprecated annotations (@Tool and @Param)
The legacy @Tool and @Param annotations in
com.google.mlkit.genai.schema.annotations.*, along with
AgentTool.fromAnnotatedObject, Agent.Builder.addTools(annotatedObject: Any), and standalone FunctionTool, have been deprecated or removed. All tools
added to Agent must originate from
@androidx.appfunctions.AppFunctionDeclaration using
Agent.Builder.enableAppFunctions(true) or AppFunctionAgentTools.discover.
5. Ephemeral single-turn execution
For one-off tasks where conversation history isn't needed (such as summarizing
text, formatting data, or answering standalone questions), invoke
runner.runSingleTurnAsync(content) directly:
import com.google.mlkit.genai.agent.AgentRunner
import com.google.mlkit.genai.agent.textTokens
import com.google.mlkit.genai.prompt.Content
import kotlinx.coroutines.flow.Flow
// Executes a single-turn query ephemerally without session persistence:
fun askQuickQuestion(runner: AgentRunner, question: String): Flow<String> {
val content = Content.builder().text(question).build()
return runner.runSingleTurnAsync(content).textTokens()
}runner.runSingleTurnAsync(content)automatically creates and evicts an ephemeral session upon Flow completion.Cleanup reference :
session.close: Releases session resources and cancels coroutines (call inViewModel.onCleared).session.deleteorrunner.deleteSession(sessionId): Permanently deletes the session from the runner.
6. Error handling and GenAiException reference
Runtime failures during on-device execution (such as model unavailability or
exceeding maximum turn limits) are emitted or thrown as GenAiException:
import com.google.mlkit.genai.common.GenAiExceptionKey error codes
GenAiException.ErrorCode.MAX_TURNS_EXCEEDED(-112): The agent exceededmaxTurns(default 10) without completing the reasoning loop.GenAiException.ErrorCode.NOT_AVAILABLE(8): The Gemini Nano model or AICore service isn't available on this device.GenAiException.ErrorCode.BUSY(9): System or AICore is busy, or battery or thermal quota has been reached.
Files
- ATTRIBUTION.mdAdded by AutoGineer962 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md13.8 KiB
- references/session_lifecycle.md3.0 KiB
- references/tools_and_functions.md11.9 KiB
references/tools_and_functions.md
This reference details patterns for registering and executing local tools with the ML Kit GenAI Agent API on Android (AICore Developer Preview).
1. Android AppFunctions (@AppFunctionDeclaration)
The primary declarative mechanism for defining on-device tools is Android
AppFunctions (androidx.appfunctions). AppFunctions provide a standardized
platform model for declaring typed in-app capabilities with automatic schema
generation.
1.1 Declaring an AppFunction
Annotate public methods with
@androidx.appfunctions.AppFunctionDeclaration(isDescribedByKDoc = true). Tool
parameter descriptions are extracted automatically from KDoc @param tags:
package com.example.ai.agent.tools
import androidx.appfunctions.AppFunctionDeclaration
import androidx.appfunctions.AppFunctionSerializable
@AppFunctionSerializable
data class CalendarEvents(
val date: String,
val events: List<String>,
)
class CalendarTools {
/**
* Fetches scheduled calendar events for a specific date in
* YYYY-MM-DD format.
*
* @param date Date string in YYYY-MM-DD format (for example, "2026-10-15")
*/
@AppFunctionDeclaration(isDescribedByKDoc = true)
fun fetch_calendar(
date: String
): CalendarEvents {
return CalendarEvents(
date = date,
events = listOf(
"Team Sync at 10:00 AM",
"Product Review at 2:00 PM"
)
)
}
}[!NOTE] AppFunction Parameter and Return Rules : 1. Parameters : Tool methods take domain parameters directly (such as
date). You don't need a framework context parameter. 2. Return Types : AppFunctions must return primitive types (String,Int,Boolean, and other primitives) or data classes annotated with@AppFunctionSerializable. ArbitraryMap<String, Any?>dictionaries aren't supported by the AppFunctions compiler.
1.2 Declarative path: whole-app discovery and scoping
For apps where all or specific AppFunctions must execute automatically when the model calls them:
import com.google.mlkit.genai.agent.Agent
import com.google.mlkit.genai.agent.AgentRunner
// 1. Configure the Agent with AppFunctions enabled
val agent = Agent.builder()
.setName("CalendarAssistant")
.setInstructions("You assist with calendar queries.")
// Automatically discovers AppFunctions in your app package
.enableAppFunctions(true)
// Optional: scope to specific function IDs or method names
.addAppFunctionIds("fetch_calendar")
.build()
// 2. Initialize the Runner
val runner = AgentRunner(agent)Scoping to Specific Functions : Use
.addAppFunctionId(id)or.addAppFunctionIds(listOf(...))to restrict the agent's available functions. Supply either the full identifier ("com.example.MyApp#createNote") or the short method name ("createNote").Context Resolution :
AgentRunner(agent)automatically resolves the application context usingMlKitContext.getInstance().applicationContext. An explicitAgentRunner(context, agent)overload is available for headless tests or custom context scopes.
1.3 Advanced path: programmatic discovery
When your app needs to inspect discovered AppFunctions, filter them, or decorate them (for example, adding Human-in-the-Loop confirmation dialogs) before registering them with the agent:
import com.google.mlkit.genai.agent.Agent
import com.google.mlkit.genai.agent.AgentRunner
import com.google.mlkit.genai.agent.AgentTool
import com.google.mlkit.genai.agent.AppFunctionAgentTools
// Suspending discovery scoped to calling app package on Dispatchers.IO:
// Overloads:
// - AppFunctionAgentTools.discover() (uses applicationContext)
// - AppFunctionAgentTools.discover(context)
// - AppFunctionAgentTools.discover(enabledAppFunctionIds)
// - AppFunctionAgentTools.discover(context, enabledAppFunctionIds)
val discoveredTools: List<AgentTool> = AppFunctionAgentTools.discover(
enabledAppFunctionIds = listOf("fetch_calendar")
)
val agent = Agent.builder()
.setName("CalendarAssistant")
.setInstructions("You assist with calendar queries.")
.addTools(discoveredTools)
.build()
val runner = AgentRunner(agent)[!WARNING] Mutual exclusivity guard : Use either the declarative path (
enableAppFunctions(true)oraddAppFunctionIdsonAgent.Builder) or the advanced path (AppFunctionAgentTools.discoverpassed toaddTools), but not both. Registering both emits a runtime warning and exposes duplicate tool schemas to the model.
1.4 Caller scoping and access levels
AppFunctions do not have to be public to the system or third-party assistants. In Android, access control is handled through caller access levels rather than manual caller identity checks (see Android AppFunctions caller scoping documentation).
By default (ACCESS_LEVEL_ANDROID_TRUSTED), platform-certified on-device
assistants holding android.permission.EXECUTE_APP_FUNCTIONS discover and
execute an AppFunction. However, for functions intended exclusively for your
app's internal agent (for example, querying private local databases, modifying
user preferences, or invoking transactional APIs), restrict caller access
using ACCESS_LEVEL_SELF:
import androidx.appfunctions.AppFunctionAccessLevel
import androidx.appfunctions.AppFunctionDeclaration
import androidx.appfunctions.ExperimentalAppFunctionsApi
import androidx.appfunctions.metadata.AppFunctionMetadata
class SecureAccountTools {
/**
* Updates an internal account setting. Restricted strictly to this app's
* agent.
*/
@OptIn(ExperimentalAppFunctionsApi::class)
@AppFunctionDeclaration(isDescribedByKDoc = true)
@AppFunctionAccessLevel(
level = AppFunctionMetadata.ACCESS_LEVEL_SELF,
isCompatEnforcementEnabled = true,
)
fun update_preference(
key: String,
value: String
): Boolean {
// Only your app's in-process agent invokes this function
return true
}
}Access level hierarchy
| Access level | Constant | Scope and permissions |
|---|---|---|
| Self Only | AppFunctionMetadata.ACCESS_LEVEL_SELF (100) | Restricted strictly to the host app itself. External assistants, system surfaces, and other apps cannot discover or invoke the function over IPC. |
| System | AppFunctionMetadata.ACCESS_LEVEL_SYSTEM (200) | Restricted to privileged system callers holding android.Manifest.permission#EXECUTE_APP_FUNCTIONS_SYSTEM (for example, Launcher, Recents) and self. |
| App Trusted | AppFunctionMetadata.ACCESS_LEVEL_APP_TRUSTED | Restricted to explicit agent package names declared in your application's manifest. |
| Android Trusted (Default) | AppFunctionMetadata.ACCESS_LEVEL_ANDROID_TRUSTED (300) | Open to platform-certified on-device assistants holding EXECUTE_APP_FUNCTIONS, system callers, and self. |
[!NOTE] HITL Interception and Platform IPC : When an AppFunction is invoked externally by a system assistant over IPC, the request routes directly to your app's
AppFunctionService, completely bypassing any in-processHitlConfirmationToolwrappers. To require sensitive operations to run through your confirmation UI, restrict the AppFunction toACCESS_LEVEL_SELFso that only your in-app agent invokes it.
2. Decorator pattern and human-in-the-loop (HITL)
Sensitive tools---such as financial transfers, data deletion, or outbound
communication---MUST NOT execute autonomously without user consent. The Agent
API provides built-in support for the Decorator pattern on AgentTool.
2.1 Tool delegation
All tools registered with Agent must originate from Android AppFunctions
(validated at construction time). AgentTool provides a public delegating
constructor AgentTool(delegate: AgentTool, name: String = delegate.name, description: String = delegate.description) that wraps an underlying
AppFunction tool discovered using AppFunctionAgentTools.discover (or another
decorator wrapping one).
2.2 Implementing a confirmation wrapper
import com.google.mlkit.genai.agent.AgentTool
/**
* Decorator tool that intercepts execution to prompt for user confirmation.
*/
class HitlConfirmationTool(
delegate: AgentTool,
private val onConfirm: suspend (
toolName: String,
args: Map<String, Any>
) -> Boolean
) : AgentTool(delegate) {
override suspend fun execute(args: Map<String, Any>): Map<String, Any?> {
// 1. Request user confirmation before invoking the sensitive tool
val confirmed = onConfirm(name, args)
if (!confirmed) {
return mapOf(
"status" to "CANCELLED_BY_USER",
"message" to "The user declined to confirm this action."
)
}
// 2. Delegate to the underlying tool execution
return checkNotNull(delegate).execute(args)
}
}2.3 Wrapping discovered AppFunctions
val allTools = AppFunctionAgentTools.discover(context)
val configuredTools = allTools.map { tool ->
if (tool.name == "deleteCalendarEvent" || tool.name == "sendInvites") {
HitlConfirmationTool(tool) { name, args ->
showUserConfirmationDialog(name, args)
}
} else {
tool
}
}
val agent = Agent.builder()
.setName("SafeAssistant")
.addTools(configuredTools)
.build()
val runner = AgentRunner(agent)3. Automated orchestration loop
Unlike manual function calling where the app must parse raw function call
responses and manually craft follow-up turns, AgentRunner handles the complete
loop internally:
The model analyzes user prompt context and decides to invoke a tool.
AgentRunneremitsAgentEvent.FunctionCall(name, args).AgentRunnerexecutes the corresponding AppFunction tool.AgentRunneremitsAgentEvent.FunctionResponse(name, response).AgentRunnerfeeds the response back into inference until the model emitsAgentEvent.TextMessage(text, isPartial)ormaxTurnsis reached.import com.google.mlkit.genai.agent.AgentEvent
session.runAsync(content).collect { event -> when (event) { is AgentEvent.TextMessage -> appendText(event.text) is AgentEvent.FunctionCall -> showToolProgress("Running ${event.name}...") is AgentEvent.FunctionResponse -> showToolProgress("Completed ${event.name}") else -> {} // Required: AgentEvent is non-exhaustive for forward compat } }
4. Deprecated and removed tool patterns
The annotations @Tool and @Param from package
com.google.mlkit.genai.schema.annotations.*, reflection-based registration
using AgentTool.fromAnnotatedObject and
Agent.Builder.addTools(annotatedObject: Any), and dynamic FunctionTool
have been deprecated or removed. All tools added to Agent must be backed by
Android AppFunctions.
Migration guide
Legacy pattern (@Tool) | AppFunctions pattern (@AppFunctionDeclaration) |
|---|---|
@Tool(description = "...") | @androidx.appfunctions.AppFunctionDeclaration(isDescribedByKDoc = true) |
@Param(description = "...") | KDoc @param tags or AppFunctions metadata |
Agent.builder().addTools(MyTools()) | Agent.builder().enableAppFunctions(true) |
AgentTool.fromAnnotatedObject(instance) | AppFunctionAgentTools.discover(context) |
Migrate existing code to @androidx.appfunctions.AppFunctionDeclaration
with Agent.Builder.enableAppFunctions(true) and AgentRunner(agent)
for declarative registration, or AppFunctionAgentTools.discover for
custom filtering and decoration.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Google LLC
- Publisher
- Android (Google) (Official)
- Distributed by
- Android (Google)
- Source
- android/skills · device-ai/mlkit-agent-api · commit bf68e2d
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE.txt)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google LLC or Android (Google).
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download mlkit-agent-api.zip