DaData.ru MCP integration for AI agents.

Connect AI agents to DaData.ru through 5 structured actions, including suggest address, suggest bank, and suggest email. Review authentication, inputs, workf…

ACTION CONTRACTS
5
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 DaData.ru integration exposes

The DaData.ru Agent App exposes 5 provider-backed actions for data and location work. Its current contract lets an authorized agent suggest russian postal addresses from partial text using dadata's suggestions api, suggest russian banks from partial text using dadata's suggestions api, and suggest email addresses from partial text using dadata's suggestions api. 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 DaData.ru account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.

VERIFIED ACTION SAMPLE

Real DaData.ru capabilities.

Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.

suggest_addressREVIEW

Suggest Russian postal addresses from partial text using DaData's Suggestions API.

INPUTS: query / count / language

suggest_bankREVIEW

Suggest Russian banks from partial text using DaData's Suggestions API.

INPUTS: query / count

suggest_emailREVIEW

Suggest email addresses from partial text using DaData's Suggestions API.

INPUTS: query / count

suggest_fioREVIEW

Suggest Russian full names from partial text using DaData's Suggestions API.

INPUTS: query / count

suggest_partyREVIEW

Suggest Russian organizations and individual entrepreneurs from partial text using DaData's Suggestions API.

INPUTS: query / count

INPUT CONTRACTS

Know what the action needs before it runs.

suggest_address

queryREQUIRED
The address search text to send to DaData.
countOPTIONAL
The maximum number of suggestions to return.
languageOPTIONAL
The language for returned address suggestions.

suggest_bank

queryREQUIRED
The search text to send to DaData.
countOPTIONAL
The maximum number of suggestions to return.

suggest_email

queryREQUIRED
The search text to send to DaData.
countOPTIONAL
The maximum number of suggestions to return.

suggest_fio

queryREQUIRED
The search text to send to DaData.
countOPTIONAL
The maximum number of suggestions to return.

PROVIDER-SPECIFIC WORKFLOWS

Jobs this Agent App can support

Inspect Suggest Address

Suggest Russian postal addresses from partial text using DaData's Suggestions API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.

suggest_address

Verify with Suggest Bank

Suggest Russian banks from partial text using DaData's Suggestions API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.

suggest_bank

SAFETY BOUNDARY

Operate DaData.ru with explicit limits

  • Authorize DaData.ru with API key and grant only the provider access required by the selected actions.
  • The current action names appear read-oriented, but returned DaData.ru 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 DaData.ru rather than assuming unrestricted access.
  • After a call, inspect the structured result and execution record before reporting that the DaData.ru task completed successfully.

CONNECTION MODEL

API key

DaData API key used in the Authorization header with the Token prefix. Create or view it in your DaData profile at https://dadata.ru/profile/#info.

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
0
WRITE SIGNALS
0
HIGH IMPACT
0
REVIEW SIGNALS
5

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 DaData.ru.

Official DaData.ru website

ONE CONNECTION. REAL WORK.

Give your agent software it can use.

Connect through MCP or explore the Agent App catalog and choose only the capabilities your workflow needs.

EXPLORE AGENT APPS