# HyperGrowth Hyperliquid FillShield

> HyperGrowth Hyperliquid FillShield is a paid API for AI agents from api.hyper-growth.xyz, paid per call via x402, $0.05/call, status down (last checked 2026-08-31).

Submits a protected order-fill request (buy or sell) on Hyperliquid with configurable urgency, position context, and autonomous execution policy for a given symbol or market.

## Facts

- Endpoint: POST https://api.hyper-growth.xyz/x402/hyperliquid-fillshield
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-08-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hypergrowth-hyperliquid-fillshield-3effc918
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wmT6HA9c6plnWIjFo6pqQ

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 hypergrowth-hyperliquid-fillshield-3effc918 -d '<json body>'
```

Example prompt: Use HyperGrowth FillShield to place a buy order on ETH-PERP for $500 notional with high urgency, and include my current position of $1200 and session drawdown of $80 so the fill protection policy can apply.

## When to prefer this

Use this endpoint when you need to execute a protected order fill on Hyperliquid with agent-native controls such as urgency classes, position context, drawdown awareness, autonomous reconciliation, and policy references — especially in agentic workflows where reliable fill execution and state management matter more than raw speed.

## Known failure modes

- Missing required fields (symbol or market_id, side, intent_notional_usd) returns validation error
- Invalid enum values for side or urgency_class return schema error
- Insufficient payment or missing x402 payment header returns 402 Payment Required
- Market unavailable or illiquid conditions may result in fill failure
- Async mode with wait_ms timeout may return pending status requiring reconciliation
- Idempotency key collision returns cached prior response

## How this service works

HyperGrowth separates the brand surface from the execution app so trade, predict, and agent-native SKU flows can scale without fragmenting the product.

## Output

A JSON response containing the fill or execution result, order status, reconciliation outcome, and any autonomous execution metadata for the submitted trade.

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hypergrowth-hyperliquid-fillshield-3effc918/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.hyper-growth.xyz](https://www.zero.xyz/host/api.hyper-growth.xyz/llms.txt)