Skip to main content

​
Subgraphs on Amoy

Kuest maintains a collection of read-only subgraphs on Polygon Amoy so builders can analyze activity without running archival nodes. Public endpoints are not listed in the docs anymore; contact [email protected] if you need access.
You can query any subgraph with GraphQL over HTTPS. Set the content-type: application/json header and post a JSON payload containing a query field plus optional variables.

​
Access

We share subgraph endpoints privately so we can keep indexing stable and consistent with production data. Reach out to [email protected] with your use case and preferred network.

​
Example query

curl -X POST "$SUBGRAPH_URL" \
  -H 'content-type: application/json' \
  -d '{
    "query": "{ wallet (id: \"0xabc...\") { id realizedPnL unrealizedPnL } }"
  }'
The response follows the GraphQL specification, so you can rely on strongly typed schemas, pagination via first/skip, and reusable fragments.

​
Monitoring and pagination tips

  • Most Kuest subgraphs expose meta { block { number } }. Poll this to ensure your backend is ingesting a sufficiently fresh block height.
  • When syncing historical data, paginate by deterministic fields such as timestamp or blockNumber. This avoids skipping data if the indexer reorders IDs.
  • Use field-level filters (e.g., where: { condition_in: [...] }) to stay within the default 100-item limit and reduce response latency.

​
When to use the Data API instead

If you need curated aggregates, such as leaderboard snapshots or normalized mark prices, our RESTful Data API includes caching. Subgraphs remain the better choice when you need raw, verifiable on-chain events or want to power your own analytics warehouse.