Find a public dataset you can query before writing an integration. You can check what a Subgraph indexes, explore its schema, preview real records, and leave with a query endpoint. You need membership in a GraphOps organization.
Find a dataset
In the platform, open Subgraphs → Discover, search by name, and filter by indexed network.
To look up a Subgraph you already know, paste its Graph Network Subgraph ID or a Deployment CID into the same search box and apply it. The page offers Explore Subgraph or Explore deployment for that identifier, even when it is not among the popular datasets. A Deployment CID must belong to a Subgraph published on The Graph Network, or to your organization's Managed Subgraphs or Endpoint Aliases. Newly published deployments are available after the next daily catalog refresh.
Choose a dataset
The catalog ranks datasets by Query popularity over seven complete UTC days:
- The most popular dataset scores 100. A score of 50 means half its recorded query fees. Searching, filtering and changing pages keep the same scale. Bars use a logarithmic display so less popular datasets are easier to compare; their lengths are not direct percentages.
- IDs sharing the same current Deployment CID appear in one row. Popularity combines their published version histories, counting each historical deployment once in that row.
- The row uses the name and Graph Network Subgraph ID with the highest individual popularity. Expand its identifier list to explore another ID; searching matches all member names and IDs.
- Popularity does not count unique queries or guarantee that the data fits your application.
- A failed refresh leaves the previous dated catalog available.
Discovery includes public datasets that meet the platform's curation eligibility requirements. Datasets whose current deployment manifest is unavailable are omitted until a later refresh can include them.
Read the metadata
Open a Subgraph in the deployment explorer. Subgraph metadata summarizes what you need before querying it, derived from the deployment's manifest:
- its Graph Network Subgraph ID, current Deployment CID and indexed network;
- the block it indexes from, its data sources and templates, and the contracts it reads;
- its triggers, such as event, call or block handlers;
- its declared query history: full history, recent blocks only, or a fixed number of blocks;
- declared features such as full-text search, and the base deployment and block when it is grafted;
- its manifest spec and mapping API versions, and its source repository when published.
Facts the manifest does not declare are left out.
Explore the schema
Under Schema and sample data, the schema relationship map starts with compact
nodes and connections. Its default focus is a queryable entity with the most distinct related
entities; incoming relationships and useful fields break ties. For example, the Uniswap schema
starts at Pool.
- Hover over a type to highlight its direct relationships; unrelated types fade.
- Check Show fields in the map's header to display entity fields and enum values.
- Choose Related types to focus on the selected type and its neighbors, or All types to show the complete schema.
- Drag to pan. Pinch on a touchscreen or trackpad to zoom, or use Ctrl + scroll, the zoom buttons or Fit.
- Search by type, field or description to find the data you need.
- Select a type to focus its relationships, or click a relationship field's type to refocus on that entity. Reduced-motion preferences move immediately.
Type signatures show nullability (!) and lists ([]). Connections show required references
(1), optional references (0..1) and lists (0..*); lists may be empty even when their type is
required.
Choose a type's eye icon or Details to open a dialog with full field
descriptions, enum values and sample previews, and to navigate to related entities. The dialog
header shows entity annotations beside the type name, such as Token @entity or
GraphNetwork @entity(immutable: false). These come from the deployment's authoring schema. An
annotation without arguments stays as declared; the explorer does not infer defaults. Close the
dialog to return to the diagram.
Preview sample records
In a type's dialog, choose scalar and enum fields, including lists, or Select all, then choose Preview records in the dialog's fixed footer. There is no field-count limit.
- Open a related entity to preview its own records. Expand list or JSON scalar cells to inspect their values.
- Scroll through the JSON or generated query and copy it to start your integration. Their scrollbars are hidden; keyboard, mouse and touch scrolling remain available.
- Check the query metadata: Deployment CID, indexed block number, UTC block timestamp and block hash. A schema without a block timestamp shows it as unavailable.
- A sample contains at most five records and represents one pinned deployment, not the complete dataset. The current deployment of a Graph Network Subgraph ID is refreshed after the next UTC midnight. Links to a Deployment CID continue to inspect that version.
Schemas and sample results are reused for the same Deployment CID. Choosing the same entity and fields returns the original records and block metadata, even after reloading the page. Field order does not change the cached sample. Previews help you inspect the dataset; use a query endpoint to read current indexed records in your application.
GraphOps funds these previews. The default limit is 60 upstream requests per organization per hour, with a shared global daily limit. Cached schemas and samples use no requests. An uncached schema uses one request; a new sample uses one more, reusing the cached schema. If a limit is reached or the deployment is unavailable, retry after the limit resets or the service recovers. If the explorer reports that no indexer is serving the deployment, follow the indexing coverage checks before retrying.
Get an endpoint
Choose Get query endpoint on a catalog row or in the deployment explorer:
- Check the identifier the wizard selects. From a Subgraph, it selects the Graph Network Subgraph ID, so your endpoint follows the publisher's current version. From a Deployment CID, it selects that exact deployment.
- Supply a saved API key, or create one if you are an Owner or Developer. Viewers and billing admins can browse and preview but cannot create keys.
- Copy the endpoint and authentication instructions into your application. Queries through that endpoint use your organization's normal billing.
Closing the wizard returns you to the catalog or detail page you started from, with its catalog filters preserved.
Explore your own resources
You can also choose Explore deployment from a Managed Subgraph version's actions, or explore an Endpoint Alias from its row actions:
- Version links, and Endpoint Aliases that target a Deployment CID or a Managed Subgraph, inspect that Deployment CID. The endpoint wizard selects a Deployment CID endpoint.
- An Endpoint Alias that follows a Graph Network Subgraph ID opens Explore Subgraph for that ID's current version.
The return link takes you back to the originating Subgraphs page.