Faraday MCP integration for AI agents.
Connect AI agents to Faraday through 12 structured actions, including get account, get current account, and get dataset. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 12
- 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 Faraday integration exposes
The Faraday Agent App exposes 12 provider-backed actions for ai and data work. Its current contract lets an authorized agent retrieve a faraday account by id, retrieve the faraday account identified by the api key, and retrieve a faraday dataset by id. 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 Faraday account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Faraday capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADRetrieve a Faraday account by ID.
INPUTS: account_id
get_current_accountREADRetrieve the Faraday account identified by the API key.
get_datasetREADRetrieve a Faraday dataset by ID.
INPUTS: dataset_id
get_scopeREADRetrieve a Faraday scope by ID.
INPUTS: scope_id
get_targetREADRetrieve a Faraday target by ID.
INPUTS: target_id
get_traitREADRetrieve a Faraday trait by ID.
INPUTS: trait_id
list_accountsREADList Faraday accounts controlled by the API key.
list_datasetsREADList Faraday datasets available in the account.
list_scopesREADList Faraday scopes defined on the account.
list_targetsREADList Faraday targets defined on the account.
list_traitsREADList user-defined and Faraday-provided traits.
list_usagesREADList Faraday usage statistics for the account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_account
account_idREQUIRED- The Faraday account ID to retrieve.
get_dataset
dataset_idREQUIRED- The Faraday dataset ID to retrieve.
get_scope
scope_idREQUIRED- The Faraday scope ID to retrieve.
get_target
target_idREQUIRED- The Faraday target ID to retrieve.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Retrieve a Faraday account by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountVerify with Get Current Account
Retrieve the Faraday account identified by the API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_accountSAFETY BOUNDARY
Operate Faraday with explicit limits
- Authorize Faraday with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Faraday 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 Faraday rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Faraday task completed successfully.
CONNECTION MODEL
API key
Faraday API key used with the Authorization Bearer header. Create or manage API keys after signing in to Faraday: https://app.faraday.ai.
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
- 12
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
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 Faraday.