{"uid":"cap_eIqRjUPFzbJtdqUV3yOIV","slug":"base-transaction-details-c1f64d24","name":"Base Transaction Details","description":"Free stable Base transaction sample. The paid $0.006 API normalizes sender, recipient, ETH value, block placement, fee fields, calldata size, and method selector from one bounded read-only RPC call.","url":"https://appearing-clinics-show-wrote.trycloudflare.com/base-transaction-sample","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET"],"type":"string"},"queryParams":{"type":"object","required":[],"properties":{}}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object"}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"unprobed","priceSource":"registry","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"down","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"unknown","summary":"price unknown","primary":{"kind":"unknown","protocol":"x402","network":"base","amountUsd":null,"per":"call","confidence":"unknown"},"accepted":[{"kind":"unknown","protocol":"x402","network":"base","amountUsd":null,"per":"call","confidence":"unknown"}]},"paymentMethods":[{"uid":"pm_iiC_vXJA9eUSWeooQCrc1","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Fetches and normalizes key fields from a single Base network transaction, including sender, recipient, ETH value, block placement, fees, calldata size, and method selector.","exampleAgentPrompt":"Can you pull up the details for this Base transaction — who sent it, who received it, how much ETH was transferred, what the gas fee was, and which method was called?","exampleUseCases":[{"title":"Verify a Base payment was sent","prompt":"I need to confirm that this Base transaction actually sent ETH to the right wallet — can you look it up and tell me the sender, recipient, amount, and whether it was included in a block?"},{"title":"Debug a failed dApp interaction","prompt":"Something went wrong with a contract call on Base. Can you fetch the transaction details and tell me the method selector, calldata size, and fee fields so I can figure out what happened?"},{"title":"Audit Base transaction history for reporting","prompt":"I'm building a report and need the normalized details for a specific Base transaction — sender, recipient, ETH value, block placement, and fees — can you retrieve all of that?"}],"resultDescription":"Returns a normalized object containing the transaction sender address, recipient address, transferred ETH value, block number and placement, gas fee fields (gas price, gas used, etc.), calldata size in bytes, and the 4-byte method selector — all extracted from a single read-only RPC call against the Base network.","failureModes":["Transaction hash not found or not yet indexed — returns empty or error response","Invalid or malformed transaction hash — validation error","Base RPC node temporarily unavailable — upstream timeout","Transaction on a different network (e.g. Ethereum mainnet) not found on Base — no result","Rate limiting or quota exceeded on the underlying RPC provider"],"whenToPreferThis":"Use this endpoint when you need normalized, structured details about a specific Base (Coinbase L2) transaction in a single bounded call — especially when you need sender, recipient, ETH value, block placement, fee breakdown, calldata size, and method selector together without building your own RPC integration. Prefer this over raw RPC calls when you want clean, normalized output without parsing raw JSON-RPC responses. Choose this over the Base Transaction Receipt endpoint when you need input-side data (calldata, method selector, value) rather than execution outcomes (status, logs, gas used).","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T22:26:03.091Z","isFirstParty":false}