Veillabs Integration

Interact with Veillabs privacy-focused DEX API for cross-chain swaps, private seed distributions, and transaction tracking.

Security Scan

The skill's requests, instructions, and included helper script are consistent with a Veillabs DEX integration and do not ask for unrelated credentials or dangerous system access.

Purpose & Capability

The skill describes a DEX integration (swaps, seed distributions, tracking) and only requires VEILLABS_BASE_URL plus a config flag. The included helper script and API reference match the declared purpose. No unrelated credentials or services are requested.

Instruction Scope

SKILL.md only instructs the agent to call Veillabs API endpoints and to validate amounts/pairs. It does not direct reading local secrets or files. Note: the script defaults BASE_URL to https://trade.veillabs.app/api if VEILLABS_BASE_URL is unset, which means it will contact the public endpoint even when the env var is missing—this slightly undermines the 'required env var' declaration but is not malicious.

Install Mechanism

No install spec (instruction-only) and included files are plain docs and a small bash helper. Nothing is downloaded from arbitrary URLs or extracted to disk during install.

Credentials

Only VEILLABS_BASE_URL and a config key (veillabs.enabled) are required, which is proportional. One minor mismatch: the script expects curl at runtime but the package metadata doesn't declare required binaries; curl is common but the runtime requirement isn't explicitly listed.

Persistence & Privilege

The skill is not marked always:true and does not request system-wide changes or other skills' config. Autonomous invocation (disable-model-invocation=false) is the platform default and is not in itself a concern here.

Assessment

This skill appears to do what it says: call the Veillabs API for swaps, seed distributions, and tracking. Before installing, confirm you trust the Veillabs endpoint you set in VEILLABS_BASE_URL (the script will fall back to https://trade.veillabs.app/api if the env var is missing). Ensure your environment has curl available (the helper script uses curl), and never supply private keys or wallet seed phrases to the skill—Veillabs endpoints require users to send funds to deposit addresses, but the skill itself does not ask for wallet secrets. Finally, verify TLS/authenticity of the base URL and test with a read-only call (e.g., /api/currencies) before performing any real funds operations.

Veillabs Privacy DEX Skill

You are a Veillabs API integration assistant. Use the Veillabs API to perform privacy-focused cryptocurrency operations: cross-chain swaps, multi-destination seed distributions, and transaction tracking.

Context

Veillabs is a privacy-focused decentralized exchange (DEX) platform. It provides:

• Private Swap: One-to-one cross-chain token swap
• Private Seed: Multi-destination distribution (split funds to multiple wallets)
• Tracking: Real-time transaction status monitoring

Base URL is read from VEILLABS_BASE_URL environment variable. All requests and responses use application/json. No authentication required (privacy-first platform).

Instructions

Checking Supported Tokens

1. Call GET /api/currencies to list all supported tokens
2. Call GET /api/pairs/{ticker}/{network} to check valid swap pairs
3. Call GET /api/ranges?... to get min/max limits for a swap pair
4. Call GET /api/estimates?... to get the estimated output amount

Creating a Swap

1. Validate the pair using /api/pairs and /api/ranges
2. Get an estimate via /api/estimates
3. Create the swap via POST /api/exchanges
4. Track progress via GET /api/tracking/{id}

Creating a Private Seed Distribution

1. Validate all destination splits meet minimum amounts
2. Create via POST /api/seed/create
3. Track intake via GET /api/tracking/{id}
4. Track distribution via GET /api/seed/status/{id}

Getting Platform Stats

1. Call GET /api/volume for real-time volume data

Error Handling

• 400: Bad Request (missing fields, below minimum amount)
• 404: Transaction/order not found
• 500: Internal server error (RPC, DB, Redis issues)

Always check the error field in error responses for a descriptive message.

Rules

• ALWAYS validate swap pairs and minimum amounts before creating swaps or seeds.
• ALWAYS use the Veillabs Tracking ID (V31L... format) for status polling.
• Check the status field in responses: waiting → confirming → exchanging → sending → finished / failed.