Benzinga MCP integration for AI agents.
Connect AI agents to Benzinga through 4 structured actions, including get consensus ratings, list analyst ratings, and list earnings. Review authentication…
- 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 Benzinga integration exposes
The Benzinga Agent App exposes 4 provider-backed actions for finance and data work. Its current contract lets an authorized agent get benzinga consensus analyst ratings and price target data for a ticker, list benzinga analyst rating calendar events with optional date and symbol filters, and list benzinga earnings calendar events with optional date and symbol filters. 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 Benzinga account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Benzinga capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_consensus_ratingsREADGet Benzinga consensus analyst ratings and price target data for a ticker.
INPUTS: symbol
list_analyst_ratingsREADList Benzinga analyst rating calendar events with optional date and symbol filters.
INPUTS: symbol / dateFrom / dateTo / page / limit
list_earningsREADList Benzinga earnings calendar events with optional date and symbol filters.
INPUTS: symbol / dateFrom / dateTo / page / limit
list_news_channelsREADList Benzinga news channels that can be used to filter news feeds.
INPUT CONTRACTS
Know what the action needs before it runs.
get_consensus_ratings
symbolREQUIRED- The stock ticker symbol to query.
list_analyst_ratings
symbolOPTIONAL- The stock ticker symbol used to filter results.
dateFromOPTIONAL- The date in YYYY-MM-DD format.
dateToOPTIONAL- The date in YYYY-MM-DD format.
pageOPTIONAL- The 0-based page number to request.
limitOPTIONAL- The maximum number of records to request.
list_earnings
symbolOPTIONAL- The stock ticker symbol used to filter results.
dateFromOPTIONAL- The date in YYYY-MM-DD format.
dateToOPTIONAL- The date in YYYY-MM-DD format.
pageOPTIONAL- The 0-based page number to request.
limitOPTIONAL- The maximum number of records to request.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Consensus Ratings
Get Benzinga consensus analyst ratings and price target data for a ticker. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_consensus_ratingsVerify with List Analyst Ratings
List Benzinga analyst rating calendar events with optional date and symbol filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_analyst_ratingsSAFETY BOUNDARY
Operate Benzinga with explicit limits
- Authorize Benzinga with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Benzinga 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 Benzinga rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Benzinga task completed successfully.
CONNECTION MODEL
API key
Benzinga API key passed as the token query parameter. Create an account and manage API access from the Benzinga API dashboard: https://www.benzinga.com/apis/
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
- 4
- 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 Benzinga.