Chargeblast MCP integration for AI agents.
Connect AI agents to Chargeblast through 8 structured actions, including get alert, create credit request, and get order. Review authentication, inputs, work…
- ACTION CONTRACTS
- 8
- 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 Chargeblast integration exposes
The Chargeblast Agent App exposes 8 provider-backed actions for finance and data work. Its current contract lets an authorized agent fetch one chargeblast alert by identifier, create a chargeblast credit request for a rejected alert, and fetch one chargeblast order by identifier, including receipt and eligibility data. 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 Chargeblast account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Chargeblast capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_alertREADFetch one Chargeblast alert by identifier.
INPUTS: id
create_credit_requestWRITECreate a Chargeblast credit request for a rejected alert.
INPUTS: alertId / comments
get_orderREADFetch one Chargeblast order by identifier, including receipt and eligibility data.
INPUTS: id
list_alertsREADList Chargeblast alerts with optional alert-network filtering and pagination.
INPUTS: filter / page / per
list_deflection_logsREADList Chargeblast digital receipt and deflection lookup logs.
INPUTS: page / per / filter
list_merchantsREADList merchants in a Chargeblast account.
INPUTS: page / per
list_ordersREADList Chargeblast order identifiers with pagination.
INPUTS: page / per
update_alertWRITEAction one Chargeblast alert with an official reason code and optional expiration-time handling.
INPUTS: id / result / actionAtExpiration
INPUT CONTRACTS
Know what the action needs before it runs.
get_alert
idREQUIRED- The Chargeblast resource identifier.
create_credit_request
alertIdREQUIRED- The rejected Chargeblast alert identifier.
commentsOPTIONAL- Optional comments to include with the credit request.
get_order
idREQUIRED- The Chargeblast resource identifier.
list_alerts
filterOPTIONAL- The type of alerts to filter for. Official examples include RDR, CDRN, Ethoca, TC40, and SAFE.
pageOPTIONAL- The Chargeblast page number to request. Alerts, orders, and deflection logs start at page 0; merchants default to page 1 in the official API.
perOPTIONAL- The number of Chargeblast records to request per page.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Alert
Fetch one Chargeblast alert by identifier. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_alertControl Create Credit Request
Create a Chargeblast credit request for a rejected alert. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_credit_requestVerify with Get Order
Fetch one Chargeblast order by identifier, including receipt and eligibility data. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_orderSAFETY BOUNDARY
Operate Chargeblast with explicit limits
- Authorize Chargeblast with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 Chargeblast rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Chargeblast task completed successfully.
CONNECTION MODEL
API key
Chargeblast API key sent with the X-API-Key header. Get it from the Chargeblast developer settings page: https://app.chargeblast.com/settings/developer
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
- 6
- WRITE SIGNALS
- 2
- 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 Chargeblast.