# Blockchain Money Map Partial Work Charge Boundary Tester

> Blockchain Money Map Partial Work Charge Boundary Tester is a paid API for AI agents from api.blockchainmoneymap.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-18).

Classifies whether a partial-work charge scenario is justified given facts about work status, charge policy, retry policy, and result completeness.

## Facts

- Endpoint: POST https://api.blockchainmoneymap.com/api/x402/x402-partial-work-charge-boundary-tester?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockchain-money-map-partial-work-charge-boundary-tester-abc066d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OZMDNjEtvvQ6ZuGtwB71n

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability blockchain-money-map-partial-work-charge-boundary-tester-abc066d9 -d '<json body>'
```

Example prompt: I need to classify a partial work charge scenario: the work status is 'timed out at 60% completion', the charge policy is 'charge on any non-zero result', the retry policy is 'no retry after timeout', and the result summary is 'partial data returned'. Can you run this through the charge boundary tester to see if the charge is justified?

## When to prefer this

Use this endpoint when you need a deterministic, policy-aware classification of whether charging an agent for partial or incomplete work is justified — especially in x402 micropayment contexts where charge boundary disputes arise due to timeouts, cancellations, or partial results. Prefer this over manual policy checks when you have structured facts about work completion and need a consistent, auditable classification.

## Known failure modes

- Missing required fields (work_status, charge_policy, retry_policy, result_summary) returns a validation error
- Invalid mode value other than 'classify' is rejected
- Malformed facts object with extra properties rejected due to additionalProperties:false
- Payment failure via x402 protocol results in 402 response before processing
- Overly long string fields exceeding 500-character limit are rejected

## How this service works

Classifies timeout, cancellation, partial result, retry, and charge-policy facts for paid work boundaries.

## Output

A JSON classification result indicating whether the described work-charge scenario falls within an acceptable charge boundary, based on the provided facts, policy, and optional reference facts about work completion status, retry and charge policies, and result availability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "classify"
   ]
  },
  "facts": {
   "type": "object",
   "required": [
    "work_status",
    "charge_policy",
    "retry_policy",
    "result_summary"
   ],
   "properties": {
    "work_status": {
     "type": "string",
     "maxLength": 500
    },
    "retry_policy": {
     "type": "string",
     "maxLength": 500
    },
    "charge_policy": {
     "type": "string",
     "maxLength": 500
    },
    "result_summary": {
     "type": "string",
     "maxLength": 500
    },
    "receipt_present": {
     "type": "boolean"
    },
    "timeout_present": {
     "type": "boolean"
    },
    "completion_percent": {
     "type": "number"
    },
    "cancellation_present": {
     "type": "boolean"
    },
    "support_path_present": {
     "type": "boolean"
    },
    "partial_result_present": {
     "type": "boolean"
    }
   },
   "additionalProperties": false
  },
  "policy": {
   "type": "object",
   "additionalProperties": true
  },
  "reference_facts": {
   "type": "object",
   "required": [
    "work_status",
    "charge_policy",
    "retry_policy",
    "result_summary"
   ],
   "properties": {
    "work_status": {
     "type": "string",
     "maxLength": 500
    },
    "retry_policy": {
     "type": "string",
     "maxLength": 500
    },
    "charge_policy": {
     "type": "string",
     "maxLength": 500
    },
    "result_summary": {
     "type": "string",
     "maxLength": 500
    },
    "receipt_present": {
     "type": "boolean"
    },
    "timeout_present": {
     "type": "boolean"
    },
    "completion_percent": {
     "type": "number"
    },
    "cancellation_present": {
     "type": "boolean"
    },
    "support_path_present": {
     "type": "boolean"
    },
    "partial_result_present": {
     "type": "boolean"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockchain-money-map-partial-work-charge-boundary-tester-abc066d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.blockchainmoneymap.com](https://www.zero.xyz/host/api.blockchainmoneymap.com/llms.txt)