Brandfetch MCP integration for AI agents.
Connect AI agents to Brandfetch through 2 structured actions, including get brand and get transaction info. Review authentication, inputs, workflows, and saf…
- ACTION CONTRACTS
- 2
- 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 Brandfetch integration exposes
The Brandfetch Agent App exposes 2 provider-backed actions for design & media and marketing work. Its current contract lets an authorized agent fetch a brandfetch brand profile from a domain, brand id, isin, or stock ticker identifier and resolve a raw transaction label into the corresponding brandfetch merchant brand profile. 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 Brandfetch account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Brandfetch capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_brandREADFetch a Brandfetch brand profile from a domain, Brand ID, ISIN, or stock ticker identifier.
INPUTS: identifier
get_transaction_infoREADResolve a raw transaction label into the corresponding Brandfetch merchant brand profile.
INPUTS: transactionLabel / countryCode
INPUT CONTRACTS
Know what the action needs before it runs.
get_brand
identifierOPTIONAL- The identifier to look up, such as a domain, Brand ID, ISIN, or stock ticker.
get_transaction_info
transactionLabelOPTIONAL- The raw merchant label from a payment or card statement.
countryCodeOPTIONAL- The ISO 3166-1 alpha-2 country code for the transaction.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Brand
Fetch a Brandfetch brand profile from a domain, Brand ID, ISIN, or stock ticker identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_brandVerify with Get Transaction Info
Resolve a raw transaction label into the corresponding Brandfetch merchant brand profile. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_transaction_infoSAFETY BOUNDARY
Operate Brandfetch with explicit limits
- Authorize Brandfetch with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Brandfetch 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 Brandfetch rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Brandfetch task completed successfully.
CONNECTION MODEL
API key
Brandfetch API key sent as a Bearer token. Create or view it in the Brandfetch developer dashboard: https://developers.brandfetch.com.
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
- 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 Brandfetch.