# Yield.xyz Get Action Status

> Yield.xyz Get Action 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-10-27).

Poll the status and transaction history of a specific yield action (enter/exit/manage) by its action ID, tracking it from CREATED through to SUCCESS or FAILED.

## Facts

- Endpoint: POST https://mcp.yield.xyz/x402/actions_get?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/yield-xyz-get-action-status-e2585ec3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5lZh125mT9v5Eid9fNw0C

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 yield-xyz-get-action-status-e2585ec3 -d '<json body>'
```

Example prompt: Check whether my Yield.xyz action with ID act_abc123xyz has completed — I need to know if it succeeded or failed and see any transactions that were created for it.

## When to prefer this

Use this endpoint after calling actions_enter, actions_exit, or actions_manage to track whether the action has completed. Prefer this over the transaction-level status endpoint when you need the overall action state and all associated transactions together, rather than the status of a single transaction hash.

## Known failure modes

- Invalid or unknown actionId returns 404 or error response
- Action still in CREATED/PENDING state — caller must continue polling
- Network or payment failure (x402 payment required, $0.001 USDC per call)
- Action ID from a different environment or wallet context returns not found

## How this service works

Get the status and transactions of a specific action by its ID (returned by actions_enter/exit/manage). Poll this to track an action from CREATED → SUCCESS/FAILED.

## Output

Returns the current lifecycle state (CREATED, SUCCESS, FAILED, etc.) of the specified action along with associated on-chain transactions, allowing the caller to determine whether the action has settled or is still pending.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "actionId": {
   "type": "string",
   "description": "Action ID from actions_enter/exit/manage"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "0b8e2c5a-…",
  "type": "STAKE",
  "intent": "enter",
  "status": "SUCCESS"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/yield-xyz-get-action-status-e2585ec3/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)