Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+21 moreClaude CodeCursorCodex CLIMuseDots
Manus
Grok
Grok Bot+18 agentsExchange API Integration Diagnostics Agent
Diagnose exchange API failures, authentication errors, and rate limit issues with evidence-based fixes and tests.
$24.99
Exchange API Integration Diagnostics Agent
Example session with this skill installed
I'm getting 'Invalid Signature' errors on Binance REST API using Python. Here is my redacted request, the signing string I'm using, and the 401 response. We are using HMAC SHA256.
- Read your context and instructions
- Compiled the exchange api integration
I have analyzed the provided request logs and signing string for the Binance REST API. The discrepancy appears to be related to the parameter ordering in the canonical request string.
Exchange Diagnostic Report
| Category | Finding | Evidence |
|---|---|---|
| Environment | Binance REST API (Production) | User logs |
| Authentication | Signature Mismatch | Provided signature does not match calculated HMAC |
| Symptoms | HTTP 401 Unauthorized | API Error Code -1022 |
| Root Cause | Parameter Ordering | Query parameters are not alphabetized before signing |
| Severity | High | Blocks all authenticated requests |
Code Changes
import hmac
import hashlib
import time
from urllib.parse import urlencode
# FIX: Ensure parameters are sorted alphabetically and timestamp is current
def sign_request(params, secret):
query_string = urlencode(sorted(params.items()))
signature = hmac.new(
secret.encode('utf-8'),
query_string.encode('utf-8'),
hashlib.sha256
).hexdigest()
return signature
# Example usage
params = {
'symbol': 'BTCUSDT',
'side': 'BUY',
'type': 'LIMIT',
'timeInForce': 'GTC',
'quantity': 0.001,
'price': 60000,
'recvWindow': 5000,
'timestamp': int(time.time() * 1000)
}
# secret = 'REDACTED_LOCAL_KEY'
# sig = sign_request(params, secret)
Regression Tests
Alphabetical Sort Test: Verify that symbol=BTC&side=BUY and side=BUY&symbol=BTC produce the same signing string.
2. Timestamp Window Test: Verify timestamp is within the recvWindow of the Binance server time.
3. Empty Body Test: Ensure GET requests with no parameters do not append a trailing ? to the base string.
Next steps
- Verify your local system clock is synced with NTP to avoid
timestamperrors. - Run the Alphabetical Sort Test using the Binance HMAC SHA256 test vectors.
- Confirm your
recvWindowis set to at least 5000ms to account for network latency.
Connects securely to your tools. The creator never sees your data.
About this skill
Exchange API integrations are notoriously fragile due to non-standard signing algorithms, strict rate limits, and asynchronous order states. This skill provides a systematic diagnostic framework to identify why your exchange connection is failing and how to fix it without leaking sensitive credentials.
What it does
- Authentication debugging validates signing algorithms, parameter ordering, and body serialization against exchange-specific requirements.
- Rate limit analysis identifies 429 triggers, request weights, and burst patterns to recommend optimal backoff strategies.
- WebSocket health checks evaluates heartbeat behavior, subscription acknowledgments, and sequence number gaps.
- Order synchronization models lifecycle states to handle delayed or missing events and prevents duplicate order submission.
- Fix generation produces minimal, language-appropriate code patches and regression tests for specific integration failures.
How it works
- Intake where you provide sanitized exchange data, error codes, and redacted request/response logs.
- Analysis where the agent checks authentication, rate limits, timestamps, and WebSocket reliability.
- Hypothesis generation to explain the root cause based on evidence and exchange documentation.
- Reporting which delivers corrected code snippets, regression test cases, and a confidence assessment.
Frameworks & tools
Works with REST and WebSocket APIs across all major crypto and financial exchanges. Supports diagnostics for any programming language or library including CCXT, Web3.js, or native implementations in Python, Go, and Node.js.
Why this beats prompting it yourself
Generic LLMs often hallucinate exchange-specific signing rules or suggest unsafe retry logic. This skill follows a strict evidence-based workflow that enforces local verification and prevents credential leakage while prioritizing order-state reconciliation over simple retries.
Use cases
- Debugging "Invalid Signature" errors on new exchange integrations.
- Fixing race conditions in high-frequency order placement.
- Resolving WebSocket connection drops and missed execution events.
- Implementing robust rate-limiting and exponential backoff logic.
Known limitations
Does not perform live trading or execution. Cannot verify fixes without user-provided sanitized logs. Requires manual entry of exchange documentation links if specific endpoints are non-standard.
Requires sanitized logs; cannot access live accounts or private keys. Diagnostics are hypotheses until verified by the user in a sandbox environment.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 22 days ago
Permissions
No special permissions declared or detected