Synthèse automatique

Interroge l’API 0xArchive avec curl pour obtenir des données de marché crypto historiques et actuelles sur Hyperliquid, Lighter.xyz et HIP-3.

Points forts

Couvre un large éventail de données : carnets d’ordres, trades, chandeliers, funding, open interest et liquidations.
Fournit des tableaux d’endpoints précis, des conventions de nommage par exchange et des aides pour les timestamps Unix en millisecondes.
Décrit un format de réponse homogène avec métadonnées, pagination par curseur et identifiant de requête.
Explique l’authentification par variable d’environnement et l’en-tête x-api-key.

Limites

Nécessite une clé API 0xArchive valide et un accès réseau ; sans elle, aucun endpoint ne fonctionne.
Le SKILL.md fourni semble tronqué : la section HIP-3 s’arrête au milieu d’un tableau, ce qui limite la couverture documentaire.
Ne détaille pas la gestion des erreurs, des quotas ou des limites de débit de l’API.

Quand l'utiliser

À utiliser lorsqu’un utilisateur veut explorer ou récupérer des données de marché crypto précises sur Hyperliquid, Lighter.xyz ou HIP-3.

Quand l'éviter

À éviter si l’utilisateur cherche des analyses de trading, des conseils financiers ou des données provenant d’autres exchanges non pris en charge.

Analyse de sécurité

Prudence

Score qualité84/100

The skill is essentially API documentation: read-only curl GETs to a documented crypto-data service using an env-provided key. No destructive commands, obfuscation, or data exfiltration to unexpected destinations were found, and the text contains no prompt-injection attempts. It lands in 'caution' because it grants Bash/network access and documents wallet-signature payment authorizations that, if executed without confirmation, would transfer USDC.

Points d'attention

•Requires Bash execution of curl commands against a third-party host (api.0xarchive.io) with the user's OXARCHIVE_API_KEY in request headers; legitimate but exposes the key to any logged shell output and to that host.
•Documents a web3/x402 payment flow that has the agent sign EIP-712 EIP-3009 USDC TransferWithAuthorization payloads (Base mainnet USDC contract) and submit them to /web3/subscribe — an autonomous run of this flow moves real funds. No explicit 'confirm with the user before signing/spending' guardrail is stated.
•References an accompanying implementation file scripts/web3_subscribe.py that is not included in the skill content, so behavior of that helper cannot be audited from this material.
•Metadata inconsistency: the YAML frontmatter declares allowed-tools: Bash, while the skill package's declared allowed-tools list is empty — reviewers should reconcile the actual granted capability.
•Skill relies on the Bash tool and outbound curl calls to api.0xarchive.io, sending the OXARCHIVE_API_KEY env var as a header on every request (legitimate, but grants the agent network access plus use of a stored credential).
•Documents an x402/EIP-3009 flow that has the agent construct and sign a USDC `TransferWithAuthorization` from the user's wallet on Base; if an agent followed this unattended it could authorize real payments. The instructions are explicit and gated on a 402 response, but this is a money-moving capability that warrants human awareness.
•References `scripts/web3_subscribe.py` for the paid-tier implementation, but no such file is included in the skill; agents may improvise wallet-signing code.
•Frontmatter declares `allowed-tools: Bash` while the catalog-level declared tools list is empty, so the declared permission surface is inconsistent.

Comment cette analyse est faite

Exemples

BTC funding history

Use 0xArchive to fetch BTC funding rate history on Hyperliquid for the last 7 days at a daily interval.

ETH candles on Lighter

Pull ETH 4-hour candles from Lighter for the past week and summarize the OHLCV data.

SOL liquidation volume

Show SOL liquidation volume on Hyperliquid over the last 24 hours, aggregated hourly.

name: 0xarchive version: 1.3.0 description: > Query historical crypto market data from 0xArchive across Hyperliquid, Lighter.xyz, and HIP-3. Covers orderbooks, trades, candles, funding rates, open interest, liquidations, and data quality. Use when the user asks about crypto market data, orderbooks, trades, funding rates, or historical prices on Hyperliquid, Lighter.xyz, or HIP-3. allowed-tools: Bash argument-hint: "query, e.g. 'BTC funding rate' or 'ETH 4h candles last week'" metadata: {"openclaw":{"requires":{"env":["OXARCHIVE_API_KEY"]},"primaryEnv":"OXARCHIVE_API_KEY"}}

0xArchive API Skill

Name: Requête données marché crypto 0xArchive
Author: Skills Guide Bot

Query historical and real-time crypto market data from 0xArchive using curl. Three exchanges are supported: Hyperliquid (perps DEX), Lighter.xyz (order-book DEX), and HIP-3 (Hyperliquid builder perps). Data types: orderbooks, trades, candles, funding rates, open interest, liquidations, and data quality metrics.

Authentication

All endpoints require the x-api-key header. The key is read from $OXARCHIVE_API_KEY.

curl -s -H "x-api-key: $OXARCHIVE_API_KEY" "https://api.0xarchive.io/v1/..."

Exchanges & Coin Naming

| Exchange | Path prefix | Coin format | Examples | |----------|-------------|-------------|---------| | Hyperliquid | /v1/hyperliquid | UPPERCASE | BTC, ETH, SOL | | HIP-3 | /v1/hyperliquid/hip3 | Case-sensitive, prefix:NAME | km:US500, xyz:XYZ100 | | Lighter | /v1/lighter | UPPERCASE | BTC, ETH |

Hyperliquid and Lighter auto-uppercase the symbol server-side. HIP-3 coin names are passed through as-is.

Timestamps

All timestamps are Unix milliseconds. Use these shell helpers:

NOW=$(( $(date +%s) * 1000 ))
HOUR_AGO=$(( NOW - 3600000 ))
DAY_AGO=$(( NOW - 86400000 ))
WEEK_AGO=$(( NOW - 604800000 ))

Response Format

Every response follows this shape:

{
  "success": true,
  "data": [ ... ],
  "meta": {
    "count": 100,
    "request_id": "uuid",
    "next_cursor": "1706000000000"   // present when more pages exist
  }
}

Endpoint Reference

Hyperliquid (`/v1/hyperliquid`)

| Endpoint | Params | Notes | |----------|--------|-------| | GET /instruments | -- | List all instruments | | GET /instruments/{symbol} | -- | Single instrument details | | GET /orderbook/{symbol} | timestamp, depth | Latest or at timestamp | | GET /orderbook/{symbol}/history | start, end, limit, cursor, depth | Historical snapshots | | GET /trades/{symbol} | start, end, limit, cursor | Trade history | | GET /candles/{symbol} | start, end, limit, cursor, interval | OHLCV candles | | GET /funding/{symbol}/current | -- | Current funding rate | | GET /funding/{symbol} | start, end, limit, cursor, interval | Funding rate history | | GET /openinterest/{symbol}/current | -- | Current open interest | | GET /openinterest/{symbol} | start, end, limit, cursor, interval | OI history | | GET /liquidations/{symbol} | start, end, limit, cursor | Liquidation events | | GET /liquidations/{symbol}/volume | start, end, limit, cursor, interval | Aggregated liquidation volume (USD) | | GET /liquidations/user/{address} | start, end, limit, cursor, coin | Liquidations for a user | | GET /freshness/{symbol} | -- | Data freshness per data type | | GET /summary/{symbol} | -- | Combined market summary (price, funding, OI, volume, liquidations) | | GET /prices/{symbol} | start, end, limit, cursor, interval | Mark/oracle/mid price history |

HIP-3 (`/v1/hyperliquid/hip3`)

Coin names are case-sensitive (e.g., km:US500). No liquidation endpoints. Orderbook requires Pro+ tier.

| Endpoint | Params | Notes | |----------|--------|-------| | GET /instruments | -- | List HIP-3 instruments | | GET /instruments/{coin} | -- | Single instrument | | GET /orderbook/{coin} | timestamp, depth | Requires Pro+ tier | | GET /orderbook/{coin}/history | start, end, limit, cursor, depth | Requires Pro+ tier | | GET /trades/{coin} | start, end, limit, cursor | Trade history | | GET /trades/{coin}/recent | limit | Recent trades (no time range needed) | | GET /candles/{coin} | start, end, limit, cursor, interval | OHLCV candles | | GET /funding/{coin}/current | -- | Current funding rate | | GET /funding/{coin} | start, end, limit, cursor, interval | Funding history | | GET /openinterest/{coin}/current | -- | Current OI | | GET /openinterest/{coin} | start, end, limit, cursor, interval | OI history | | GET /freshness/{coin} | -- | Data freshness per data type | | GET /summary/{coin} | -- | Combined market summary (price, funding, OI) | | GET /prices/{coin} | start, end, limit, cursor, interval | Mark/oracle/mid price history |

Lighter (`/v1/lighter`)

Same data types as Hyperliquid except: no liquidations. Adds granularity on orderbook history and /recent trades.

| Endpoint | Params | Notes | |----------|--------|-------| | GET /instruments | -- | List Lighter instruments | | GET /instruments/{symbol} | -- | Single instrument | | GET /orderbook/{symbol} | timestamp, depth | Latest or at timestamp | | GET /orderbook/{symbol}/history | start, end, limit, cursor, depth, granularity | Default granularity: checkpoint | | GET /trades/{symbol} | start, end, limit, cursor | Trade history | | GET /trades/{symbol}/recent | limit | Recent trades (no time range needed) | | GET /candles/{symbol} | start, end, limit, cursor, interval | OHLCV candles | | GET /funding/{symbol}/current | -- | Current funding rate | | GET /funding/{symbol} | start, end, limit, cursor, interval | Funding history | | GET /openinterest/{symbol}/current | -- | Current OI | | GET /openinterest/{symbol} | start, end, limit, cursor, interval | OI history | | GET /freshness/{symbol} | -- | Data freshness per data type | | GET /summary/{symbol} | -- | Combined market summary (price, funding, OI) | | GET /prices/{symbol} | start, end, limit, cursor, interval | Mark/oracle price history |

Data Quality (`/v1/data-quality`)

| Endpoint | Params | Notes | |----------|--------|-------| | GET /status | -- | System health status | | GET /coverage | -- | Coverage summary, all exchanges | | GET /coverage/{exchange} | -- | Coverage for one exchange | | GET /coverage/{exchange}/{symbol} | from, to | Symbol-level coverage + gaps | | GET /incidents | status, exchange, since, limit, offset | List incidents | | GET /incidents/{id} | -- | Single incident | | GET /latency | -- | Ingestion latency metrics | | GET /sla | year, month | SLA compliance report |

Web3 Authentication (`/v1`)

Get API keys programmatically using an Ethereum wallet (SIWE). No API key required for these endpoints.

| Endpoint | Params | Notes | |----------|--------|-------| | POST /auth/web3/challenge | address (wallet address) | Returns SIWE message to sign | | POST /web3/signup | message, signature | Returns free-tier API key | | POST /web3/keys | message, signature | List all keys for wallet | | POST /web3/keys/revoke | message, signature, key_id | Revoke a key | | POST /web3/subscribe | tier (build or pro), payment-signature header | x402 USDC subscription (see flow below) |

Free-tier flow: Call /auth/web3/challenge with wallet address → sign the returned message with personal_sign (EIP-191) → submit to /web3/signup with the message and signature → receive API key.

Paid-tier flow (x402):

POST /web3/subscribe with { "tier": "build" } → server returns 402 with payment.amount (micro-USDC), payment.pay_to (treasury address), payment.network.
Sign an EIP-712 TransferWithAuthorization (EIP-3009) on USDC Base:
- Domain: { name: "USD Coin", version: "2", chainId: 8453, verifyingContract: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913" }
- Type: TransferWithAuthorization(address from, address to, uint256 value, uint256 validAfter, uint256 validBefore, bytes32 nonce)
- Message: { from: <wallet>, to: <pay_to>, value: <amount>, validAfter: 0, validBefore: <now+3600>, nonce: <32 random bytes hex> }

Build x402 v2 payment payload:

{
  "x402Version": 2,
  "payload": {
    "signature": "0x<EIP-712 signature hex>",
    "authorization": {
      "from": "0x<wallet>",
      "to": "0x<pay_to from step 1>",
      "value": "<amount as string>",
      "validAfter": "0",
      "validBefore": "<unix timestamp as string>",
      "nonce": "0x<64 hex chars>"
    }
  }
}

Base64-encode the JSON and retry: POST /web3/subscribe with { "tier": "build" } and header payment-signature: <base64 payload> → receive API key + subscription.

Important: All authorization values (value, validAfter, validBefore) must be strings, not numbers. See scripts/web3_subscribe.py for a complete working Python implementation.

Common Parameters

| Param | Type | Description | |-------|------|-------------| | start | int | Start timestamp (Unix ms). Defaults to 24h ago. | | end | int | End timestamp (Unix ms). Defaults to now. | | limit | int | Max records. Default 100, max 1000 (max 10000 for candles). | | cursor | string | Pagination cursor from meta.next_cursor. | | interval | string | Candle interval: 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w. Default: 1h. For OI/funding: 5m, 15m, 30m, 1h, 4h, 1d. Omit for raw data. | | depth | int | Orderbook depth (number of price levels per side). | | granularity | string | Lighter orderbook resolution: checkpoint (default), 30s, 10s, 1s, tick. |

Smart Defaults

When the user does not specify a time range, default to the last 24 hours:

NOW=$(( $(date +%s) * 1000 ))
DAY_AGO=$(( NOW - 86400000 ))

For candles with no explicit range, default to a range that makes sense for the interval (e.g., last 7 days for 4h candles, last 30 days for 1d candles).

Pagination

When meta.next_cursor is present in the response, more data is available. Append &cursor=VALUE to fetch the next page:

# First page
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/trades/BTC?start=$START&end=$END&limit=1000"

# Next page (use next_cursor from previous response)
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/trades/BTC?start=$START&end=$END&limit=1000&cursor=1706000000000_12345"

Tier Limits

| Tier | Price | Coins | Orderbook Depth | Lighter Granularity | Historical Depth | Rate Limit | |------|-------|-------|-----------------|---------------------|------------------|------------| | Free | $0 | BTC only (HIP-3: km:US500 only) | 20 levels | -- | 30 days | 15 RPS | | Build | $49/mo | All | 50 levels | checkpoint, 30s, 10s | 1 year | 50 RPS | | Pro | $199/mo | All | 100 levels | + 1s | Full history | 150 RPS | | Enterprise | Custom | All | Full depth | + tick | Full history | Custom |

Error Handling

| HTTP Status | Meaning | Action | |-------------|---------|--------| | 400 | Bad request / validation error | Check params (missing start/end, invalid interval) | | 401 | Missing or invalid API key | Set $OXARCHIVE_API_KEY | | 403 | Tier restriction | Upgrade plan (e.g., non-BTC coin on Free tier) | | 404 | Symbol not found | Check coin name spelling and exchange | | 429 | Rate limited | Back off and retry |

Error responses return { "code": 400, "error": "description" }.

Example Queries

# List Hyperliquid instruments
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/instruments" | jq '.data | length'

# Current BTC orderbook (top 10 levels)
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/orderbook/BTC?depth=10" | jq '.data'

# ETH trades from the last hour
NOW=$(( $(date +%s) * 1000 )); HOUR_AGO=$(( NOW - 3600000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/trades/ETH?start=$HOUR_AGO&end=$NOW&limit=100" | jq '.data'

# SOL 4h candles for the last week
NOW=$(( $(date +%s) * 1000 )); WEEK_AGO=$(( NOW - 604800000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/candles/SOL?start=$WEEK_AGO&end=$NOW&interval=4h" | jq '.data'

# Current BTC funding rate
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/funding/BTC/current" | jq '.data'

# BTC open interest aggregated to 1h intervals (last week)
NOW=$(( $(date +%s) * 1000 )); WEEK_AGO=$(( NOW - 604800000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/openinterest/BTC?start=$WEEK_AGO&end=$NOW&interval=1h" | jq '.data'

# ETH funding rates aggregated to 4h intervals (last 30 days)
NOW=$(( $(date +%s) * 1000 )); MONTH_AGO=$(( NOW - 2592000000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/funding/ETH?start=$MONTH_AGO&end=$NOW&interval=4h" | jq '.data'

# HIP-3 km:US500 candles (last 24h, 1h interval)
NOW=$(( $(date +%s) * 1000 )); DAY_AGO=$(( NOW - 86400000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/hip3/candles/km:US500?start=$DAY_AGO&end=$NOW&interval=1h" | jq '.data'

# Lighter BTC orderbook history (30s granularity, last hour)
NOW=$(( $(date +%s) * 1000 )); HOUR_AGO=$(( NOW - 3600000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/lighter/orderbook/BTC/history?start=$HOUR_AGO&end=$NOW&granularity=30s&limit=100" | jq '.data'

# System health status
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/data-quality/status" | jq '.'

# SLA report for current month
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/data-quality/sla" | jq '.'

# BTC market summary (price, funding, OI, volume, liquidations in one call)
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/summary/BTC" | jq '.data'

# BTC data freshness (lag per data type)
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/freshness/BTC" | jq '.data'

# BTC price history (mark/oracle/mid) aggregated to 1h
NOW=$(( $(date +%s) * 1000 )); DAY_AGO=$(( NOW - 86400000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/prices/BTC?start=$DAY_AGO&end=$NOW&interval=1h" | jq '.data'

# BTC liquidation volume aggregated to 4h buckets
NOW=$(( $(date +%s) * 1000 )); WEEK_AGO=$(( NOW - 604800000 ))
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/hyperliquid/liquidations/BTC/volume?start=$WEEK_AGO&end=$NOW&interval=4h" | jq '.data'

# Data coverage for Hyperliquid BTC
curl -s -H "x-api-key: $OXARCHIVE_API_KEY" \
  "https://api.0xarchive.io/v1/data-quality/coverage/hyperliquid/BTC" | jq '.'

Du fichier au premier essai

Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.

Consulter la source et ses fichiers annexes

Ce téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.

1. Télécharger le fichier

Télécharger SKILL.md

Depuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.

Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.

mkdir -p '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/0xarchive-crypto-market-data-query-mmk3nhp4/download' --output '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md.part' && mv '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md.part' '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md'

2. Vérifier les prérequis

Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.

Outils déclarés par l’auteur (à vérifier dans votre agent) : Bash

Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.

Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.

3. Charger la skill

Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.

Claude Code

test -f '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md' && test -s '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/0xarchive' && cp -R '.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4' '.claude/skills/0xarchive'

OpenSkills

OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.

Installation officielle d’OpenSkills

openskills install './.skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4'

openskills read '0xarchive-crypto-market-data-query-mmk3nhp4'

La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.

Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.

openskills sync

Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.

4. Faire un premier essai

Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :

Lis .skill-downloads/0xarchive-crypto-market-data-query-mmk3nhp4/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.

Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.

Skills similaires

Créer des cartes interactives avec kepler.gl

Data & IA

Création de cartes interactives et export HTML autonome avec le package Python keplergl, à partir de données géospatiales (DataFrame, GeoJSON, CSV).

Claude CodeCursorCodexintermediateSûr 11,995

Skills Guide Bot

Optimisation de paramètres par agent

Data & IA

Guide d'optimisation de systèmes configurables avec objectif mesurable, via des essais bornés et une recommandation fondée sur des preuves.

Claude CodeCursorCodexintermediateSûr 45,609

Skills Guide Bot

Relance des visiteurs ICP

Data & IA

Identifiez les utilisateurs inscrits correspondant au profil client idéal mais qui n'ont pas activé, et rédigez des messages de relance personnalisés pour les réengager.

Claude CodeintermediateSûr 6,843

Skills Guide Bot

Requête données marché crypto 0xArchive

Recommandé pour

Synthèse automatique

Points forts

Limites

Analyse de sécurité

Exemples

0xArchive API Skill

Authentication

Exchanges & Coin Naming

Timestamps

Response Format

Endpoint Reference

Hyperliquid (/v1/hyperliquid)

HIP-3 (/v1/hyperliquid/hip3)

Lighter (/v1/lighter)

Data Quality (/v1/data-quality)

Web3 Authentication (/v1)

Common Parameters

Smart Defaults

Pagination

Tier Limits

Error Handling

Example Queries

Du fichier au premier essai

1. Télécharger le fichier

2. Vérifier les prérequis

3. Charger la skill

4. Faire un premier essai

Créer des cartes interactives avec kepler.gl

Optimisation de paramètres par agent

Relance des visiteurs ICP

Hyperliquid (`/v1/hyperliquid`)

HIP-3 (`/v1/hyperliquid/hip3`)

Lighter (`/v1/lighter`)

Data Quality (`/v1/data-quality`)

Web3 Authentication (`/v1`)