mitudrudutta commited on
Commit
e186190
·
1 Parent(s): 83eb290

docs: update README for clarity and conciseness in chargeback operations description

Browse files
Files changed (1) hide show
  1. README.md +13 -16
README.md CHANGED
@@ -1,27 +1,24 @@
1
- ---
2
- title: ChargebackOps
3
- sdk: docker
4
- app_port: 8000
5
- tags:
6
- - openenv
7
- ---
8
-
9
  # ChargebackOps
10
 
11
- A production-grade OpenEnv environment for merchant-side chargeback dispute operations. An AI agent acts as a dispute analyst — investigating evidence across internal systems, choosing whether to contest or concede, and maximizing financial recovery under deadline and step-budget pressure.
 
 
 
 
 
12
 
13
- Built for the [OpenEnv Hackathon](https://openenv.org/) Round 1 challenge.
14
 
15
  ## Why This Environment Matters
16
 
17
- Chargeback dispute handling is a real operations workflow that costs merchants **$125 billion annually**. Analysts must:
18
 
19
- - Parse reason codes and assess representment deadlines
20
- - Gather evidence from the right merchant systems while avoiding harmful artifacts
21
- - Decide whether to contest, accept, or refund — under time pressure
22
- - Prioritize cases in a multi-dispute queue by deadline urgency and financial impact
23
 
24
- This makes ChargebackOps a strong benchmark for tool-using agents. It tests retrieval, decision-making, prioritization, and operational restraint in a controlled environment with deterministic scoring.
25
 
26
  ## Architecture
27
 
 
 
 
 
 
 
 
 
 
1
  # ChargebackOps
2
 
3
+ ![Python](https://img.shields.io/badge/Python-3.10%2B-3776AB?logo=python&logoColor=white)
4
+ ![FastAPI](https://img.shields.io/badge/FastAPI-API-009688?logo=fastapi&logoColor=white)
5
+ ![OpenEnv](https://img.shields.io/badge/OpenEnv-Compatible-111827)
6
+ ![Docker](https://img.shields.io/badge/Docker-Ready-2496ED?logo=docker&logoColor=white)
7
+
8
+ ChargebackOps is an OpenEnv environment for merchant-side chargeback and dispute operations. The agent acts as a dispute analyst: it triages open disputes, retrieves evidence from merchant systems, decides whether to contest or concede, and resolves each case under deadline and step-budget pressure.
9
 
10
+ The repository is designed for agent evaluation rather than generic chat. It exposes a typed action space, deterministic state transitions, dense reward shaping, and programmatic grading so model behavior can be measured as operational performance.
11
 
12
  ## Why This Environment Matters
13
 
14
+ Chargeback dispute handling is a real operations workflow. Analysts must:
15
 
16
+ - interpret reason codes and response deadlines
17
+ - gather evidence from the correct internal systems while avoiding harmful artifacts
18
+ - decide whether to contest, accept, or refund
19
+ - prioritize multiple disputes by urgency, recoverability, and operational cost
20
 
21
+ That makes ChargebackOps a good benchmark for tool-using agents. It measures retrieval quality, decision quality, prioritization, and operational restraint in a controlled environment with deterministic scoring.
22
 
23
  ## Architecture
24