# Getstatus - Contract Execution Status

> Getstatus - Contract Execution Status is a paid API for AI agents from stablecrypto.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns the execution status of an Ethereum-compatible smart contract transaction given a transaction hash and chain ID

## Facts

- Endpoint: POST https://stablecrypto.dev/api/etherscan/transaction/getstatus
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/getstatus-contract-execution-status-ae400ae1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7AQ9e1SFfi7dGDiHdYI4y

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 getstatus-contract-execution-status-ae400ae1 -d '<json body>'
```

Example prompt: Can you check whether my smart contract transaction 0x4e3a12f8d9b7c1a5e2f0d8b3c6a9e4f1d7b2c5a8e3f0d9b6c3a7e2f1d8b5c4a on Ethereum mainnet (chain ID 1) succeeded or reverted?

## When to prefer this

Use this endpoint when you need to verify whether a specific smart contract transaction succeeded or reverted on an EVM-compatible chain (Ethereum, Polygon, Base, etc.). Prefer this over general transaction list endpoints when you already have the tx hash and just need a pass/fail execution status, not the full transaction history.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Unsupported chain ID returns an error or empty response
- Transaction not yet mined returns a pending or not-found status
- Network timeout or Etherscan API unavailability causes a 5xx error
- Transaction hash does not exist on the specified chain

## How this service works

Pay-per-request access to CoinGecko, DefiLlama, Alchemy, and Etherscan APIs. No auth, no subscriptions.

## Output

Returns the contract execution status for the specified transaction, indicating whether it succeeded or failed (reverted), sourced from Etherscan on the given EVM chain.

## Example request

```json
{
 "txhash": "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef",
 "chainid": 1
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "txhash": {
   "type": "string",
   "description": "Transaction hash"
  },
  "chainid": {
   "type": "number",
   "description": "EVM chain ID (1=Ethereum, 137=Polygon, 8453=Base, etc.)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/getstatus-contract-execution-status-ae400ae1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stablecrypto.dev](https://www.zero.xyz/host/stablecrypto.dev/llms.txt)