# Vextorium Token Position Surveillance

> Vextorium Token Position Surveillance is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-29).

Re-evaluates a held token position against current on-chain conditions, flagging liquidity drops, risk score changes, dangerous contract powers, honeypot patterns, and inflated volume with a CLEAN/DEGRADED/RISK verdict.

## Facts

- Endpoint: POST https://api.vextorium.com/token-vigilar-posicion-pago?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-token-position-surveillance-82b56735
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_55KEYsO9wj0Kk83O0VdiQ

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 vextorium-token-position-surveillance-82b56735 -d '<json body>'
```

Example prompt: Check my Solana token position for 0xABC123... — I entered with $50,000 liquidity and a risk score of 82. Tell me if it's still CLEAN or if there are any new alarms like honeypot patterns, dangerous mint/freeze powers, or a liquidity drop.

## When to prefer this

Use this endpoint when an agent or user already holds a token position and needs to continuously re-evaluate whether current on-chain conditions have deteriorated relative to their entry point. It is specifically designed for post-entry surveillance with comparative alarms (entry liquidity vs current, entry score vs current), making it more useful than a generic token analysis endpoint when the user has defined entry parameters. Prefer this over a one-time token scan when the goal is ongoing position risk monitoring, especially for detecting rug pulls, honeypots, or dangerous contract power activation after entry.

## Known failure modes

- Missing required token address returns validation error
- Invalid or unrecognized token address returns null/error response
- Unsupported network value returns enum validation error
- Entry liquidity or score not provided may limit comparative alarm accuracy
- Network congestion or RPC unavailability may cause timeout or incomplete data
- Token with no on-chain liquidity data may return null fields

## How this service works

Re-check a token you already hold against your entry: liquidity below 25% of entry, risk score drop, dangerous powers active (mint, freeze, pause...), honeypot pattern or inflated volume. Verdict CLEAN (LIMPIO), DEGRADED (DEGRADADO) or RISK (RIESGO) with the reason for each alarm. Pass your entry liquidity and score.

## Output

Returns a verdict of CLEAN (LIMPIO), DEGRADED (DEGRADADO), or RISK (RIESGO) plus: current token price in USD, current liquidity in USD, current risk score, a list of active alarms with reasons (e.g. liquidity below 25% of entry, risk score drop, dangerous powers detected, honeypot pattern, inflated volume), a warnings list, token symbol, network, and authenticity indicator.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "red": {
   "enum": [
    "solana",
    "base",
    "ethereum",
    "arbitrum",
    "optimism",
    "polygon"
   ],
   "type": "string"
  },
  "token": {
   "type": "string"
  },
  "puntuacion_entrada": {
   "type": "integer"
  },
  "liquidez_entrada_usd": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-token-position-surveillance-82b56735/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)