Lp Rebalance Check
by AirdropPulse in Onchain & crypto
GigaDex rebalance scenario comparison (Robinhood Chain) — side-by-side model of a position’s current range versus a same-width range recentered on the current price: probability-in-range at horizon, expected time-in-range share and capital-efficiency, plus static GIGA Protect / rebalance-cost considerations. Analytics only, not a recommendation to act.
https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check- Price
- $0.1
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 2 h ago, next any minute now
Reliability
Latest check failed 2 h ago: Amount "0.1" is not in atomic token units
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check
Each call costs $0.1 in USDC on Polygon, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check?horizon_days=14%2C+max+90&token_id=GigaDex+position+NFT+token+idParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
horizon_days | string | No | holding-period horizon in days for the scenario comparison (default: 14, max 90) |
token_id | string | No | required |
Example response
The provider's example. We can't check it without paying.
Example response, 30 lines
{
"considerations": [
"GIGA Protect: rapid liquidity add/remove cycling can forfeit campaign rewards — per official docs, avoid rapid rebalance cycles during points campaigns.",
"Rebalancing realizes any divergence loss and incurs gas + swap fees.",
"A recentered range restarts fee accrual position but does not recover forfeited time out of range."
],
"current_range": {
"capital_efficiency_x": 13.7,
"distance_to_lower_edge_pct": 2.6,
"distance_to_upper_edge_pct": 2.4,
"expected_time_in_range_share": 0.71,
"prob_in_range_at_horizon": 0.55,
"tick_lower": 104960,
"tick_upper": 110400
},
"current_tick": 107697,
"disclaimer": "Educational analytics… not investment advice.",
"method": "Side-by-side scenario comparison under zero-drift GBM on trailing realized vol; not a recommendation to act.",
"pair": "WETH/PONS",
"recentered_same_width": {
"capital_efficiency_x": 13.7,
"distance_to_lower_edge_pct": 3.1,
"distance_to_upper_edge_pct": 3,
"expected_time_in_range_share": 0.78,
"prob_in_range_at_horizon": 0.62,
"tick_lower": 105300,
"tick_upper": 110740
},
"token_id": "4821"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.1.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check?horizon_days=14%2C+max+90&token_id=GigaDex+position+NFT+token+id'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check?horizon_days=14%2C+max+90&token_id=GigaDex+position+NFT+token+id' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fairdroppulse.theaslangroupllc.com%2Fapi%2Flp%2Frebalance-check
const res = await pay("https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check?horizon_days=14%2C+max+90&token_id=GigaDex+position+NFT+token+id");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://airdroppulse.theaslangroupllc.com/api/lp/rebalance-check?horizon_days=14%2C+max+90&token_id=GigaDex+position+NFT+token+id")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Amount "0.1" is not in atomic token units | 402 | 185 ms | $0.1 |
| 5 h ago | Amount "0.1" is not in atomic token units | 402 | 202 ms | $0.1 |
| 10 h ago | Amount "0.1" is not in atomic token units | 402 | 204 ms | $0.1 |
| 16 h ago | Amount "0.1" is not in atomic token units | 402 | 167 ms | $0.1 |
| 21 h ago | Amount "0.1" is not in atomic token units | 402 | 211 ms | $0.1 |
Show 9 older checks
| 27 h ago | Amount "0.1" is not in atomic token units | 402 | 194 ms | $0.1 |
| 33 h ago | Amount "0.1" is not in atomic token units | 402 | 210 ms | $0.1 |
| 38 h ago | Amount "0.1" is not in atomic token units | 402 | 213 ms | $0.1 |
| 44 h ago | Amount "0.1" is not in atomic token units | 402 | 193 ms | $0.1 |
| 2 days ago | Amount "0.1" is not in atomic token units | 402 | 187 ms | $0.1 |
| 2 days ago | Amount "0.1" is not in atomic token units | 402 | 193 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 169 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 151 ms | $0.1 |
| 3 days ago | Amount "0.1" is not in atomic token units | 402 | 199 ms | $0.1 |