Back to Browse
SignalHarness Base L1 Data Fee Analyzer
x402
SignalHarness Base L1 Data Fee Analyzer is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.015/call, status unknown (last checked 2026-09-13).
Analyzes L1 data fee components for Base network transactions given caller-supplied receipt or fee data
Price / call$0.015
Success—
StatusUnknown
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 structured analysis JSON containing L1 data fee amount, fee model type (e.g. 'supplied_receipt'), individual fee components (e.g. l1_fee), network context (accepted chain IDs, deposit transaction type, protocol family), and a list of any missing evidence. Also includes a top-level evidence scope field and analyzed network identifier.
Example use cases
Audit Base transaction L1 fee breakdown
“I have a Base mainnet transaction receipt that shows an L1 fee of 500 and I want to understand exactly how that was computed — can you analyze the L1 data fee components and tell me the fee model and any missing evidence?”
Validate OP Stack fee model for dApp
“Before we display fees to users in our dApp, I need to verify that the L1 data fee in this Base transaction receipt is correctly structured for the OP Stack fee model — can you break it down and flag anything unusual?”
Debug unexpected L1 fee on Base testnet
“We're seeing a higher-than-expected L1 data fee on Base Sepolia (chain 84532) for this transaction. Can you analyze the supplied receipt JSON and tell me which fee components are present and whether anything looks off?”
Technical details
Endpoint
POSThttps://signalharness.ai/api/agent/services/base_l1_data_fee_analyze/invokeWhen to prefer
Use this endpoint when you specifically need to decompose and audit L1 data fee components for Base network (OP Stack) transactions and you have the receipt or fee data available. Prefer it over generic gas estimation tools when you already have a transaction receipt and want to validate or explain the L1 fee calculation. Not suitable for estimating fees before transaction submission or for non-OP-Stack networks.
Side effects
- Missing or malformed request_json causes validation failure
- Caller supplies incorrect or incomplete protocol parameters — service cannot invent them
- Unsupported chain ID outside of Base mainnet (8453) or Base Sepolia (84532) may yield incomplete analysis
- Empty or minimal JSON input results in missing_evidence flags in the response
- Malformed receipt structure returns warnings rather than hard errors
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| request_json | string |
Output
Schema · Response
{
"type": "json",
"example": {
"replay": false,
"result": {
"warnings": [
"Caller must supply current protocol parameters; the service never invents them."
],
"service_id": "base_l1_data_fee_analyze",
"analysis_json": "{\"components\":{\"l1_fee\":\"500\"},\"fee_model\":\"supplied_receipt\",\"l1_data_fee\":\"500\",\"missing_evidence\":[],\"network_context\":{\"accepted_chain_ids\":[\"8453\",\"84532\"],\"deposit_transaction_type\":\"0x7e\",\"fee_model\":\"L2 execution plus caller-supplied L1 data/operator components\",\"protocol_family\":\"OP Stack\"}}",
"evidence_scope": "caller_supplied_data",
"analyzed_network": "base"
},
"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": "base_l1_data_fee_analyze",
"executionId": "example-execution",
"startedAtMs": 0,
"amountAtomic": "15000",
"resultSha256": "eeba997d0fd6897c71854234cc58b635640e3964d25ccc77ccc6c77ba6307884",
"serviceVersion": "1.0.0",
"settlementReference": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"artifacts": [],
"requestId": "example-request",
"executionId": "example-execution"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"