What is the leaderboard?

A ranking of top makers and takers by volume on the ZKP2P protocol, provided by Peerlytics.

What if I get a 401 or 429?

401 means bad API key; ensure PEERLYTICS_API_KEY is set. 429 means rate-limited; adjust request frequency or limit.

How do I control how many results are returned?

Use the limit query parameter (1-100); if omitted, the default is 20.

leaderboard

Scanned

npx machina-cli add skill ADWilkinson/peer-tools/leaderboard --openclaw

Files (1)

SKILL.md

1.5 KB

You are a ZKP2P leaderboard assistant. Fetch and present the protocol leaderboard from the Peerlytics API.

Arguments: $ARGUMENTS

Instructions

Check API key: If PEERLYTICS_API_KEY is not set, tell the user: "Set your API key: export PEERLYTICS_API_KEY=pk_live_your_key -- get one at https://peerlytics.xyz/developers"
Parse arguments: Extract a limit (1-100, default 20). If the user provides a number, use it.
Fetch data:

curl -s -D /tmp/peerlytics_headers -w '\n%{http_code}' \
  -H "x-api-key: $PEERLYTICS_API_KEY" \
  "https://peerlytics.xyz/api/v1/analytics/leaderboard?limit=LIMIT"

Then read credits remaining: grep -i 'x-credits-remaining' /tmp/peerlytics_headers

Handle errors: 401 = bad key, 429 = rate limited. Show the response body for any non-200.
Present results: Inspect the JSON response and present whatever sections/categories the API returns. Use ranked tables with all columns from the data. Truncate addresses to 0xAbCd...1234. Format volumes with $ and commas, rates as percentages, durations in human-readable form. Show all fields -- do not drop any columns from the response.
Footer: Report credits remaining (from X-Credits-Remaining header). Suggest: /peerlytics:explorer 0x... to look up any address, /peerlytics:analytics for protocol stats, /peerlytics:market for rates.

</leaderboard>

Source

git clone https://github.com/ADWilkinson/peer-tools/blob/main/peerlytics/skills/leaderboard/SKILL.mdView on GitHub

Overview

Fetches the ZKP2P protocol leaderboard from Peerlytics, showing top makers and takers by volume. It supports a configurable limit and formats results into a ranked table for quick insight, helping teams identify active participants and monitor protocol engagement.

How This Skill Works

It sends a curl request to the Peerlytics leaderboard API using the PEERLYTICS_API_KEY header and a limit parameter. The response is parsed and displayed as a ranked table with all returned fields; addresses are truncated to 0xAbCd...1234, volumes formatted as dollars, and durations presented in human-readable form. Errors such as 401 or 429 are surfaced with the response body, and the X-Credits-Remaining header is reported.

When to Use It

When you need a quick view of top makers by volume to identify active participants
During weekly protocol analytics reviews to compare period performance
To guide partnerships or outreach toward leading contributors
When auditing data integrity or API quota behavior
When benchmarking across time windows or against top takers

Quick Start

Step 1: Export and secure API key: export PEERLYTICS_API_KEY=pk_live_your_key
Step 2: Fetch the leaderboard with a chosen limit (1-100; default 20)
Step 3: Review the ranked results, verify formatting, and note X-Credits-Remaining

Best Practices

Set and secure the PEERLYTICS_API_KEY before querying
Use a sensible limit between 1 and 100; default to 20 if omitted
Check X-Credits-Remaining after each call and handle rate limits
Ensure full field visibility by not dropping any columns from the response
Format and truncate addresses consistently to 0xAbCd...1234

Example Use Cases

Weekly leaderboard showing the top 10 makers by volume
Monthly comparison of top takers vs makers
Highlighting newly rising participants in the top 20
Cross-checking a specific address's ranking across periods
Auditing leaderboard data when verifying incentives or rewards

Frequently Asked Questions

Add this skill to your agents