Detect Language MCP integration for AI agents.
Connect AI agents to Detect Language through 4 structured actions, including get account status, detect text, and detect texts. Review authentication, inputs…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Detect Language integration exposes
The Detect Language Agent App exposes 4 provider-backed actions for ai and data work. Its current contract lets an authorized agent get the current detect language account usage, limits, plan, and status, detect the language of a single text string with confidence scores, and detect languages for multiple text strings in one batch request. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Detect Language account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Detect Language capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_statusREADGet the current Detect Language account usage, limits, plan, and status.
detect_textREVIEWDetect the language of a single text string with confidence scores.
INPUTS: text
detect_textsREVIEWDetect languages for multiple text strings in one batch request.
INPUTS: texts
list_languagesREADList languages supported by Detect Language.
INPUT CONTRACTS
Know what the action needs before it runs.
detect_text
textOPTIONAL- The UTF-8 text to detect.
detect_texts
textsOPTIONAL- The UTF-8 texts to detect, preserving output order.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Status
Get the current Detect Language account usage, limits, plan, and status. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_statusVerify with List Languages
List languages supported by Detect Language. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_languagesSAFETY BOUNDARY
Operate Detect Language with explicit limits
- Authorize Detect Language with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Detect Language data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Detect Language rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Detect Language task completed successfully.
CONNECTION MODEL
API key
Detect Language uses this API key in the Authorization bearer header. Sign up and get the key from your Detect Language account: https://detectlanguage.com/users/sign_up.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Detect Language.