Back to Browse
SignalHarness Base Event Log Decoder
x402
SignalHarness Base Event Log Decoder is a paid API for AI agents from signalharness.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).
Decodes and analyzes raw Base blockchain event logs, returning structured event data including event name, arguments, block context, and network metadata
Price / call$0.01
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 JSON object containing the decoded event name, structured argument key-value pairs (e.g. from, to, value for a Transfer), block number, log index, transaction hash, removed flag, and network context metadata for Base (chain IDs 8453 and 84532, OP Stack protocol family). Also includes warnings if logs are caller-supplied and not independently verified.
Example use cases
Decode DeFi Transfer event on Base
“I just got a transaction receipt from Base mainnet and I need to know what Transfer event was emitted — can you decode this event log and show me the from address, to address, and token amount? Here's the raw log data from the receipt.”
Debug smart contract event emission
“My smart contract on Base emitted an event and I have the raw log from the transaction, but I can't read the hex-encoded topics and data. Can you decode this log JSON and tell me the event name and all its arguments?”
Monitor Base L2 contract activity
“I'm watching transactions on Base and I have a raw event log from block 19500000. Can you analyze this log and extract the event name, the emitting contract address, and any indexed parameters so I can understand what the contract did?”
Technical details
Endpoint
POSThttps://signalharness.ai/api/agent/services/base_event_log_decode/invokeWhen to prefer
Choose this endpoint when you need to decode raw EVM event logs specifically from the Base L2 network (mainnet chain ID 8453 or testnet 84532) into human-readable structured data. It is particularly useful when working with OP Stack-based transaction receipts and you need event name, argument extraction, and Base-specific network context in a single call. Prefer alternatives if you need full transaction tracing, multi-chain log decoding across arbitrary networks, or on-chain verification of log authenticity.
Side effects
- Malformed or invalid log JSON causes parsing failure
- Unrecognized ABI or event signature results in undecoded output
- Caller-supplied logs are not independently verified — results may reflect tampered data
- Log from unsupported network (non-Base chain) may return incorrect network context
- Missing required fields in request_json returns validation error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| request_json | string |
Output
Schema · Response
{
"type": "json",
"example": {
"replay": false,
"result": {
"warnings": [
"Supplied logs are not independently verified."
],
"service_id": "base_event_log_decode",
"analysis_json": "{\"address\":\"0x0000000000000000000000000000000000000001\",\"args\":{\"from\":\"0x0000000000000000000000000000000000000001\",\"to\":\"0x0000000000000000000000000000000000000002\",\"value\":\"100\"},\"block_number\":1,\"event_name\":\"Transfer\",\"log_index\":0,\"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\"},\"removed\":false,\"transaction_hash\":\"0x1111111111111111111111111111111111111111111111111111111111111111\"}",
"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_event_log_decode",
"executionId": "example-execution",
"startedAtMs": 0,
"amountAtomic": "10000",
"resultSha256": "0eff082e3b6078abc126260c0ee9d8583e92645d3e05feaaadccf6d659cde91b",
"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"