# mcp.yield.xyz Get Transaction Status

> mcp.yield.xyz Get Transaction Status is a paid API for AI agents from mcp.yield.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Returns the on-chain status of a single Yield.xyz transaction by its transaction ID, confirming whether it has landed or inspecting its constructed/unsigned state.

## Facts

- Endpoint: POST https://mcp.yield.xyz/x402/get_transaction
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-yield-xyz-get-transaction-status-eb38b197
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bs16ev_Kv_iL_Rv4S91mN

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 mcp-yield-xyz-get-transaction-status-eb38b197 -d '<json body>'
```

Example prompt: Can you check the on-chain status of my Yield.xyz transaction with ID txn_abc123xyz? I want to know if it's been confirmed yet.

## When to prefer this

Use this endpoint when you need to check the status of a specific, already-initiated Yield.xyz transaction (e.g., after broadcasting a stake or deposit). This is distinct from checking an action's overall status — use this when you have a specific transactionId from an action's transactions array and need granular per-transaction confirmation.

## Known failure modes

- Transaction ID not found — returns 404 or error if the ID does not exist in Yield.xyz's system
- Invalid transaction ID format — malformed string returns a validation error
- Transaction still pending — status may show unconfirmed if polled too soon after broadcast
- Network or provider outage — Yield.xyz backend may be temporarily unavailable
- Unauthorized — missing or invalid x402 payment header results in 402 or 401 error

## How this service works

Get the on-chain status of a single transaction by its Yield.xyz transaction ID — poll after broadcasting to confirm it landed, or inspect the constructed/unsigned transaction.

## Output

Returns the current status of the specified transaction — whether it is constructed/unsigned, pending, confirmed on-chain, or failed — along with transaction details such as hash, block info, and any relevant metadata associated with that Yield.xyz transaction ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "transactionId": {
   "type": "string",
   "description": "Transaction ID from an action's transactions[]"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "6b757454-…",
  "hash": "0xabc…",
  "type": "SUPPLY",
  "status": "CONFIRMED",
  "network": "base"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-yield-xyz-get-transaction-status-eb38b197/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp.yield.xyz](https://www.zero.xyz/host/mcp.yield.xyz/llms.txt)