What problem does it solve? Retrieving on-chain Boundless protocol data—proof requests, prover and requestor activity, staking positions, PoVW rewards, and delegations—requires knowing which indexer deployment serves which endpoints across multiple networks and environments, plus handling API keys, pagination styles, and rate limits correctly. ## Core Features & Use Cases - Dual Indexer Routing: Directs queries to the correct indexer type—market indexers on L2 chains (Base, Taiko, Sepolia) for market data, or ZKC indexers on Ethereum L1 for staking, PoVW, and delegation data. - Pagination and Rate-Limit Handling: Provides ready-to-use curl patterns for cursor-based and offset-based pagination, client-side time filtering, and backoff on HTTP 429/403 responses. - Address Labeling and Credentials: Reads network_secrets.toml for API keys and network_address_labels.json to annotate addresses with human-readable labels in output. - Use Case: Ask for a prover's market stats and staking info, and the Skill queries both the market indexer and the corresponding ZKC indexer, then presents labeled, formatted results. ## Quick Start Ask the assistant to show the latest proof requests and staking summary for a given address on Base prod using the indexer API.
