Install Jentic One Beta

Connect the Chargeblast API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chargeblast API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchargeblast.io%2Fchargeblast-io" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fchargeblast.io%2Fchargeblast-io" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Chargeblast API.

Pull deflection logs from /api/v3/deflections/logs to audit which alerts were resolved before posting

Track outbound notifications and webhook callbacks via POST /api/v2/track

Manage order data with GET /api/v2/orders, individual lookups, and POST /api/v2/orders/upload bulk ingestion

List, retrieve, and update chargeback alerts via /api/alerts and /api/v2/alerts plus the alert/{id} variants

GET STARTED

Start building with Chargeblast API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Chargeblast API for, with concrete tasks.

★ Multi-Network Chargeback Deflection

Merchants enrolled across CDRN, Ethoca, and RDR pull alerts from /api/v2/alerts and decide whether to refund (deflect) or fight. The platform lets the merchant call POST /api/v2/credit-request/create to instruct the issuer to credit the cardholder, which prevents the dispute from progressing into a chargeback. Audit trails are pulled from /api/v3/deflections/logs.

Pull /api/v2/alerts with state=open, post /api/v2/credit-request/create for each over the deflection threshold, then verify with /api/v3/deflections/logs

Order Sync for Faster Resolution

POST /api/v2/orders/upload accepts a batch of completed orders so incoming alerts can be matched against the merchant's actual transaction record. Better matching reduces manual review time on the dispute desk and lets the merchant decide on credit-vs-fight in seconds rather than minutes.

POST /api/v2/orders/upload with the last 24 hours of orders and confirm via GET /api/v2/orders that the records are searchable

Merchant Onboarding into Alert Networks

Payment service providers and aggregators onboard merchants into the chargeback alert networks through POST /api/enroll_merchant. The endpoint registers the descriptors and the merchant identifier; POST /api/unenroll cleanly reverses enrollment when the merchant offboards. GET /api/merchants and /api/descriptors give the read-side view for reconciliation.

POST /api/enroll_merchant with merchant identifiers and descriptors, then verify via GET /api/merchants

Agent-Driven Dispute Operations via Jentic

An AI agent given a directive like 'deflect any open alert under $200 by issuing a credit' can resolve the workflow through Jentic. The agent searches Jentic for the list-alerts and credit-request operations, iterates the alerts, and issues the credit instructions, while the API key stays in your Jentic One instance.

Search Jentic for 'list chargeback alerts', filter to open alerts under $200, and post /api/v2/credit-request/create for each

Key Endpoints

17 endpoints — chargeblast is a chargeback alert and prevention tool that notifies merchants whenever a cardholder initiates a dispute, allowing the merchant to refund or contest before it becomes a chargeback.

METHOD

PATH

DESCRIPTION

GET

/api/v2/alerts

List chargeback alerts (v2)

POST

/api/v2/alerts/update/{id}

Update an alert outcome (v2)

POST

/api/v2/credit-request/create

Submit a credit request to deflect an alert

POST

/api/v2/orders/upload

Bulk upload merchant orders

GET

/api/v2/orders/{id}

Retrieve a single order by ID

GET

/api/v3/deflections/logs

Read deflection audit logs (v3)

POST

/api/enroll_merchant

Enroll a merchant into the alert network

GET

/api/v2/alerts

List chargeback alerts (v2)

POST

/api/v2/alerts/update/{id}

Update an alert outcome (v2)

POST

/api/v2/credit-request/create

Submit a credit request to deflect an alert

POST

/api/v2/orders/upload

Bulk upload merchant orders

GET

/api/v2/orders/{id}

Retrieve a single order by ID

GET

/api/v3/deflections/logs

Read deflection audit logs (v3)

POST

/api/enroll_merchant

Enroll a merchant into the alert network

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Chargeblast by hand means learning its X-API-Key header auth and attaching the key to every alert, order, and enrollment call yourself. Through Jentic you install once, import Chargeblast from the API Directory, store the key once, and your agent calls it.

Permission scoping

Chargeblast puts the alert and order ids in the URL path (/api/v2/alerts/update/{id}, /api/v2/orders/{id}), so a rule can pin your agent to a given alert or order and nothing else. You choose the operations it may call, so merchant enrollment or credit-request creation are not included unless you add them.

Credential isolation

Your Chargeblast API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list chargeback alerts' or 'submit a credit request', and Jentic returns the matching Chargeblast operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Chargeblast API through Jentic.

What authentication does the Chargeblast API use?

Chargeblast uses an API key in the X-API-Key header on every request. Through Jentic, the key is stored encrypted in your Jentic One instance and only injected server-side at execution time.

Can I deflect a chargeback by issuing a credit through the Chargeblast API?

Yes. POST /api/v2/credit-request/create with the alert ID and credit amount and Chargeblast forwards the credit instruction to the issuer. If accepted in time, the dispute is closed before it becomes a chargeback.

What is the difference between the v2 and v3 endpoints on this API?

The v2 endpoints handle alert listing, order upload, and credit-request creation. The v3 namespace currently exposes /api/v3/deflections/logs for the audit trail. Both versions share the same X-API-Key auth and base URL.

What are the rate limits for the Chargeblast API?

Chargeblast does not publish a fixed public rate limit. Real-time alert workloads should poll /api/v2/alerts at modest intervals and bulk-upload orders via /api/v2/orders/upload rather than per-order writes; back off on HTTP 429.

How do I bulk-upload orders for matching through Jentic?

Install jentic with pip install jentic, search for 'upload merchant orders for chargeback matching', load the schema for POST /api/v2/orders/upload, and execute. Run Jentic One, the self-hosted execution layer, for an agent API key.

Does the Chargeblast API expose deflection audit logs?

Yes. GET /api/v3/deflections/logs returns the history of alerts that were successfully deflected, suitable for compliance reporting and reconciliation against the merchant's chargeback ratio over time.

Can I limit what my agent is allowed to do with the Chargeblast API?

Yes. Because you run Jentic One yourself, your own rules decide which Chargeblast operations and credentials the agent may use. Since Chargeblast puts the alert and order ids in the URL path, such as /api/v2/alerts/update/{id} and /api/v2/orders/{id}, you can pin the agent to a specific alert or order and nothing else. You pick the operations it may call, so merchant enrollment via /api/enroll_merchant or credit-request creation via /api/v2/credit-request/create stay off limits unless you add them.

Chargeblast API

AI ReadinessFoundational (C+)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey17 EndpointsREST

For Agents

Track chargeback alerts, ingest orders for matching, request credits to deflect disputes, and manage merchant enrollment. Useful for fraud and dispute operations agents working across multiple alert generations.

Use for: Get the deflection log for the last week, List open chargeback alerts in the v2 namespace, Update an alert with a refund outcome, Upload a batch of completed orders for alert matching

Not supported: Does not handle payment authorisation, refund settlement on the acquirer side, or representment of already-posted chargebacks - use for pre-dispute alert deflection, order matching, and merchant enrollment only.

Chargeblast is a chargeback alert and prevention tool that notifies merchants whenever a cardholder initiates a dispute, allowing the merchant to refund or contest before it becomes a chargeback. This domain hosts an expanded set of v2 and v3 endpoints covering alert tracking, order ingestion, credit requests, deflection logs, and merchant enrollment. It is targeted at merchants and processors operating in card-not-present commerce who need to drive chargeback ratios down quickly.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

25%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

82%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Chargeblast API to your agent

Capabilities

Start building with Chargeblast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Chargeblast API

Jentic AI Readiness Score

Chargeblast API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness