# SignalHarness Agent Trace Cost Report from Supplied Usage

> SignalHarness Agent Trace Cost Report from Supplied Usage is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.025/call, status unknown (last checked 2026-09-15).

Generates a cost analysis report for an AI agent trace by processing caller-supplied usage data and returning a structured analysis with warnings about data provenance.

## Facts

- Endpoint: POST https://signalharness.ai/api/agent/services/agent_trace_cost_report_from_supplied_usage/invoke
- Price: $0.025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signalharness-agent-trace-cost-report-from-supplied-usage-458e9ef9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jq1qqWHADJuVVvlmd4b2T

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 signalharness-agent-trace-cost-report-from-supplied-usage-458e9ef9 -d '<json body>'
```

Example prompt: Can you generate a cost analysis report for my agent trace using this usage data I collected: {"model":"gpt-4o","input_tokens":1500,"output_tokens":400,"calls":3}? I want to see the full breakdown and any warnings about the data.

## When to prefer this

Choose this endpoint when you have your own agent usage data or trace logs and want a structured cost report computed against them — especially useful when you cannot rely on server-side telemetry and need to submit usage records yourself. It is ideal for cost estimation, billing audits, and pre-deployment checks where the agent operator controls the input data. Not suitable when you need server-verified usage data or real-time live trace capture.

## Known failure modes

- Invalid or malformed JSON string in request_json field causes rejection
- Input JSON string exceeds 65536 character limit
- Submitted usage data does not conform to expected schema, triggering validation warnings
- Payment failure on x402 protocol results in 402 response with no analysis
- Empty or too-short request_json (minLength 2) rejected
- Result includes warning that caller-supplied data may not be trustworthy — analysis is only as good as the input

## How this service works

Explore 330 pay-per-call x402 API services and 27 agent-native digital products, with Base USDC pricing, secure Polar checkout, and free discovery.

## Output

Returns a JSON result containing a cost analysis under `analysis_json`, a list of warnings (notably that caller-supplied data should be verified), the `service_id` of the analyzed service, and an `evidence_scope` field indicating the data came from the caller. Also includes a receipt with payment details, network info (Base/eip155:8453), amount charged in atomic USDC units, and execution metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "request_json": {
   "type": "string",
   "maxLength": 65536,
   "minLength": 2
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "replay": false,
  "result": {
   "warnings": [
    "Verify the caller-supplied data before relying on this result."
   ],
   "service_id": "agent_trace_cost_report_from_supplied_usage",
   "analysis_json": "{\"example\":\"schema-valid caller-supplied data\"}",
   "evidence_scope": "caller_supplied_data"
  },
  "status": "succeeded",
  "receipt": {
   "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "usage": [],
   "status": "succeeded",
   "network": "eip155:8453",
   "artifacts": [],
   "endedAtMs": 0,
   "latencyMs": 0,
   "paymentId": "example-payment",
   "receiptId": "example-receipt",
   "requestId": "example-request",
   "serviceId": "agent_trace_cost_report_from_supplied_usage",
   "executionId": "example-execution",
   "startedAtMs": 0,
   "amountAtomic": "25000",
   "resultSha256": "3510f2ad8ae3c7a2b5808c1953864a2d6227aabaa6208c3944066aa66c256619",
   "serviceVersion": "1.0.0",
   "settlementReference": "0x0000000000000000000000000000000000000000000000000000000000000000"
  },
  "artifacts": [],
  "requestId": "example-request",
  "executionId": "example-execution"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signalharness-agent-trace-cost-report-from-supplied-usage-458e9ef9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from signalharness.ai](https://www.zero.xyz/host/signalharness.ai/llms.txt)