Repository navigation
docs(subgraphs): add the GraphOps Platform as a Subgraphs provider #1133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
chriswessels
wants to merge
1
commit into
graphprotocol:main
Choose a base branch
from
graphops:docs/add-graphops-subgraphs-provider
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,152 @@ | ||
| --- | ||
| title: GraphOps Platform | ||
| sidebarTitle: GraphOps | ||
| description: Query Subgraphs on The Graph Network through the GraphOps Platform with a GraphOps API key, paid with credits by card, with no GRT or wallet needed. | ||
| --- | ||
|
|
||
| The GraphOps Platform serves GraphQL queries for Subgraphs on The Graph Network to applications that pay with a GraphOps API key and credits, with no GRT or wallet required. It is for teams that want one account and one bill for Subgraphs, RPC, and Substreams, and for teams that want guaranteed indexing and query capacity with [Managed Subgraphs](https://docs.graphops.xyz/subgraphs/managed-subgraphs?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=intro-managed-subgraphs). | ||
|
|
||
| This page describes a gateway that an independent team operates. GraphOps sets its own pricing, terms, and support. For the canonical gateway, see [Subgraph Studio](/subgraphs/providers/subgraph-studio/introduction/). For all gateways, see [Subgraph Providers](/subgraphs/providers/overview/). | ||
|
|
||
| ## Overview | ||
|
|
||
| | Operator | [GraphOps](https://graphops.xyz/?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=overview-home) | | ||
| | :-- | :-- | | ||
| | Network | The Graph Network | | ||
| | Status | Endorsed by The Graph Foundation | | ||
| | Sign up | [platform.graphops.xyz](https://platform.graphops.xyz/auth/register?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=overview-register) | | ||
| | Endpoint | `https://subgraphs.graphops.xyz/v1/subgraphId/<SUBGRAPH_ID>` or `https://subgraphs.graphops.xyz/v1/deploymentCID/<DEPLOYMENT_ID>` | | ||
| | Authentication | API key with Subgraphs access, as a bearer token in the `Authorization` header, or in the path | | ||
| | Payment methods | Card or Link, billed in US dollars, with an invoice for every payment. Enterprise volume can be invoiced and paid afterwards, by other payment methods and in other currencies, including EUR. [Contact GraphOps](https://graphops.xyz/contact/?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=overview-contact-payment) to arrange it. | | ||
| | Support | Live support is available in the [platform](https://platform.graphops.xyz/organizations/current/overview?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=overview-support&support=open), the [contact form](https://graphops.xyz/contact/?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=overview-contact), and live service status is at [status.graphops.xyz](https://status.graphops.xyz/). Platform Support is available 24/7, with escalation to an engineer from 09:00 to 17:00 GMT on weekdays. GraphOps engineers are on-call 24/7 to respond to service disruption. | | ||
| | Indexer transparency data | [Indexer Portal](#indexer-portal) and [For Indexers](#for-indexers) | | ||
|
|
||
| ## About GraphOps | ||
|
|
||
| GraphOps builds and operates onchain data infrastructure. It has worked on The Graph as a core developer since 2022, on Indexer tooling and network operations, and runs RPC, Subgraphs, and Substreams services from one platform. | ||
|
|
||
| ## How the GraphOps Platform Works | ||
|
|
||
| 1. Your application sends a GraphQL query to `https://subgraphs.graphops.xyz/v1/`, identifying the Subgraph by Deployment ID, Subgraph ID, or an [Endpoint Alias](https://docs.graphops.xyz/subgraphs/guides/manage-aliases?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=how-it-works-manage-aliases), and authenticates with your GraphOps API key. | ||
| 2. GraphOps checks the key, resolves the identifier to a Deployment ID, and records the query against your organization's credit balance. | ||
| 3. The GraphOps Platform selects an Indexer on The Graph Network that serves the deployment and forwards the query. GraphOps pays that Indexer in GRT with TAP receipts from its own escrow. | ||
| 4. The response returns to your application unchanged. | ||
|
|
||
| You pay GraphOps in credits, by card or another payment method. You do not need GRT, a wallet, or escrow balance of your own. | ||
|
|
||
| ## Pricing | ||
|
|
||
| Queries use credits from your organization's balance: 50 credits per query, plus 1,500,000 credits per GiB of response data. Monthly plans range from 100M to 10B credits, with every additional credit costing less. You can also buy top-ups or pay as you go. | ||
|
|
||
| [Managed Subgraphs](https://docs.graphops.xyz/subgraphs/managed-subgraphs?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=pricing-managed-subgraphs) need a monthly plan. They accrue indexing charges hourly, based on attached time, entity count, and storage, whether or not they receive queries. Queries to Managed Subgraphs are free of charge. | ||
|
|
||
| See [GraphOps pricing](https://graphops.xyz/pricing/?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=pricing-pricing) for plan prices and [Subgraph usage and limits](https://docs.graphops.xyz/subgraphs/usage-and-limits?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=pricing-usage-and-limits) for current rates. | ||
|
|
||
| ## Sign Up and Get an API Key | ||
|
|
||
| 1. [Create an account](https://platform.graphops.xyz/auth/register?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=sign-up-register) and verify your email. | ||
| 2. Create or join an organization. | ||
| 3. Choose monthly credits or buy a top-up. | ||
| 4. Create an API key with Subgraphs access, and store it in your secret manager. The platform shows the key only when you create or rotate it. | ||
|
|
||
| You can [limit a key](https://docs.graphops.xyz/platform/api-keys?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=sign-up-api-keys-limit-a-key#limit-a-key) to specific Subgraphs, Endpoint Aliases, and website origins. See [Subgraph authentication](https://docs.graphops.xyz/subgraphs/authentication?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=sign-up-authentication). | ||
|
|
||
| ## Query a Subgraph | ||
|
|
||
| Query by Subgraph ID to follow the versions its owner publishes on The Graph Network: | ||
|
|
||
| ```bash | ||
| curl "https://subgraphs.graphops.xyz/v1/subgraphId/<SUBGRAPH_ID>" \ | ||
| -H "Authorization: Bearer $GRAPHOPS_API_KEY" \ | ||
| -H "Content-Type: application/json" \ | ||
| --data '{"query": "{ _meta { deployment block { number } hasIndexingErrors } }"}' | ||
| ``` | ||
|
|
||
| Query by Deployment ID (starting with `Qm`) to stay on one exact version: | ||
|
|
||
| ```bash | ||
| curl "https://subgraphs.graphops.xyz/v1/deploymentCID/<DEPLOYMENT_ID>" \ | ||
| -H "Authorization: Bearer $GRAPHOPS_API_KEY" \ | ||
| -H "Content-Type: application/json" \ | ||
| --data '{"query": "{ _meta { deployment block { number } hasIndexingErrors } }"}' | ||
| ``` | ||
|
|
||
| `_meta` returns the deployment that answered and its latest indexed block, so both requests work for any Subgraph. GraphQL reports query problems in an `errors` array, often with HTTP status `200`, so check for `errors` as well as the status code. See [Query your first Subgraph](https://docs.graphops.xyz/subgraphs/getting-started?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=query-getting-started) and [Troubleshooting](https://docs.graphops.xyz/subgraphs/troubleshooting?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=query-troubleshooting). | ||
|
|
||
| For the difference between the two IDs, see [Subgraph ID vs Deployment ID](/subgraphs/querying/subgraph-id-vs-deployment-id/). | ||
|
|
||
| ### Publish a Subgraph | ||
|
|
||
| Every Subgraph deployment you query or deploy through GraphOps is available on The Graph Network. GraphOps also allocates to every Managed Subgraph as an Indexer on The Graph Network. Applications can query its deployment through any gateway, not only through GraphOps, and the indexing and query capacity that comes with a Managed Subgraph serves queries from all of them. | ||
|
|
||
| To have GraphOps ensure indexing and query capacity for a Subgraph, deploy it as a Managed Subgraph with the [GraphOps CLI](https://docs.graphops.xyz/subgraphs/guides/deploy-your-subgraph?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=publish-deploy-with-graphops-cli#deploy-with-the-graphops-cli) or [Graph CLI](https://docs.graphops.xyz/subgraphs/guides/deploy-your-subgraph?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=publish-deploy-with-graph-cli#deploy-from-graphops-platform). | ||
|
|
||
| GraphOps does not automatically publish Subgraph IDs, which give a Subgraph a stable identity on The Graph Network across version upgrades. To publish a Subgraph ID onchain, use [Subgraph Studio](/subgraphs/providers/subgraph-studio/introduction/), then query it through GraphOps by Subgraph ID or Deployment ID. To give consumers a stable endpoint that you can move to a new deployment without using onchain Subgraph IDs, use an [Endpoint Alias](https://docs.graphops.xyz/subgraphs/guides/manage-aliases?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=publish-manage-aliases). | ||
|
|
||
| ## Supported Networks | ||
|
|
||
| Queries reach Subgraphs on every network The Graph Network serves. Managed Subgraphs are available on a smaller set of networks. See [GraphOps supported networks](https://graphops.xyz/networks/?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=networks-networks-page) and [Subgraph networks](https://docs.graphops.xyz/subgraphs/networks?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=networks-networks). | ||
|
|
||
| For chain support on The Graph Network, see [Supported Networks](/supported-networks/). | ||
|
|
||
| ## Additional Services | ||
|
|
||
| - **Endpoint Aliases**: A query URL your organization names, such as `/v1/alias/orders`, that lets an application switch Subgraph versions without changing its endpoint. See [Manage Endpoint Aliases](https://docs.graphops.xyz/subgraphs/guides/manage-aliases?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=services-manage-aliases). | ||
| - **Managed Subgraphs**: GraphOps keeps a Subgraph indexed for your organization. A new version indexes as Next while the Current version keeps serving, and a Managed Subgraph can follow the versions its owner publishes on The Graph Network. See [Develop and release a Subgraph](https://docs.graphops.xyz/subgraphs/guides/develop-and-release?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=services-develop-and-release). | ||
| - **AI agents**: Agent skills and MCP servers for AI agents. See [GraphOps for AI agents](https://docs.graphops.xyz/ai-agents?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=services-ai-agents). | ||
|
|
||
| ## Support | ||
|
|
||
| Live support in the [GraphOps Platform](https://platform.graphops.xyz/organizations/current/overview?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=support-platform&support=open) for existing customers, and on the website and the [contact form](https://graphops.xyz/contact/?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=support-contact) for everything else. Service status is at [status.graphops.xyz](https://status.graphops.xyz/). GraphOps engineers are on-call 24/7 to respond to service disruption. | ||
|
|
||
| For questions about The Graph Network, use [The Graph Discord](https://discord.gg/graphprotocol). | ||
|
|
||
| ## For Indexers | ||
|
|
||
| As an endorsed gateway, the GraphOps Platform publishes the transparency data that The Graph Foundation asks every endorsed gateway to publish. The data is public and needs no credentials: | ||
|
|
||
| | Data | Where | | ||
| | :-- | :-- | | ||
| | Current gateway version, with minimum indexer-service and graph-node versions | [Constraints](https://indexer-portal.graphops.xyz/constraints), or `https://subgraph-gateway-indexer-qos.graphops.xyz/v1/version`. The history of changes is in the [Changelog](https://indexer-portal.graphops.xyz/changelog) | | ||
| | Blocklist of Indexers and POIs per deployment | [Constraints](https://indexer-portal.graphops.xyz/constraints), or `https://subgraph-gateway-indexer-qos.graphops.xyz/v1/blocklist` | | ||
| | Per-Indexer QoS data (attempts, outcomes, latency) | The [Indexer Portal](#indexer-portal), or `https://subgraph-gateway-indexer-qos.graphops.xyz/v1/indexers` | | ||
|
|
||
| To accept paid queries from the GraphOps Platform, add every GraphOps sender to `tap.sender_aggregator_endpoints` in the configuration file that indexer-service and tap-agent share, keep any senders you already accept, and restart both services: | ||
|
|
||
| | Gateway ID (sender address) | Aggregator endpoint | | ||
| | :------------------------------------------- | :------------------------------------------------- | | ||
| | `0xDD6a6f76eb36B873C1C184e8b9b9e762FE216490` | `https://tap-aggregator-arbitrum-one.graphops.xyz` | | ||
| | `0xd46b87020AB3E8B4E5A64EC7c0e3496142c5CA1B` | `https://tap-aggregator-arbitrum-one.graphops.xyz` | | ||
| | `0x382411dE4eaed896E289E6b57B3F48A766980e1F` | `https://tap-aggregator-arbitrum-one.graphops.xyz` | | ||
|
|
||
| ```toml | ||
| [tap.sender_aggregator_endpoints] | ||
| 0xDD6a6f76eb36B873C1C184e8b9b9e762FE216490 = "https://tap-aggregator-arbitrum-one.graphops.xyz" | ||
| 0xd46b87020AB3E8B4E5A64EC7c0e3496142c5CA1B = "https://tap-aggregator-arbitrum-one.graphops.xyz" | ||
| 0x382411dE4eaed896E289E6b57B3F48A766980e1F = "https://tap-aggregator-arbitrum-one.graphops.xyz" | ||
| ``` | ||
|
|
||
| [Set up your indexer](https://indexer-portal.graphops.xyz/setup) in the Indexer Portal always lists the current senders, and the gateway's version requirements are on [Constraints](https://indexer-portal.graphops.xyz/constraints). | ||
|
|
||
| ## Indexer Portal | ||
|
|
||
| The [GraphOps Indexer Portal](https://indexer-portal.graphops.xyz/) is a public, read-only view of how the GraphOps Platform observes each Indexer. It needs no sign-in and reads the same QoS data as the API above. | ||
|
|
||
| - **[Indexers](https://indexer-portal.graphops.xyz/):** every Indexer the gateway sent queries to in a time range, ranked by attempts, failures, acceptance rate, p95 latency, reported lag, or estimated receipt fees. Find an Indexer by address or ENS name. | ||
| - **Indexer pages:** an Indexer's acceptance rate, latency, and reported lag, each ranked against the median Indexer, with its deployments, its failures by cause, and any deployments the blocklist bars it from. | ||
| - **[Distribution](https://indexer-portal.graphops.xyz/distribution):** how accepted queries and fees are spread across Indexers, gateway-wide or for one deployment, with concentration measures such as the Nakamoto coefficient. | ||
| - **[Constraints](https://indexer-portal.graphops.xyz/constraints):** what the gateway requires now: minimum indexer-service and Graph Node versions, the thresholds an Indexer can act on, and the blocklist. | ||
| - **[How selection works](https://indexer-portal.graphops.xyz/selection):** which Indexers the gateway can select for a query, and what makes an eligible Indexer more likely to be chosen. | ||
| - **[Set up your indexer](https://indexer-portal.graphops.xyz/setup):** the TAP senders to configure, the versions to run, and how to check your Indexer once it serves queries. | ||
| - **[Changelog](https://indexer-portal.graphops.xyz/changelog):** gateway changes that affect how Indexers are selected, measured, and paid, with what to do about each. | ||
|
|
||
| The Indexers, Indexer, and Distribution views filter by time range and chain, and link to an exact range so you can share what you see. To suggest an improvement to the portal, use Provide feedback. | ||
|
|
||
| > [!NOTE] Indexers can get direct support from GraphOps through Get support in the Indexer Portal sidebar, which opens a live chat with the GraphOps team. Use it for questions about your results, selection, blocklist rules, or TAP payments from the GraphOps Platform. | ||
|
|
||
| ## Related | ||
|
|
||
| - [Subgraph Providers](/subgraphs/providers/overview/) | ||
| - [Choosing a Gateway](/subgraphs/querying/choosing-a-gateway/) | ||
| - [Subgraph Gateway docs](/gateways/subgraphs/overview/) | ||
| - [GraphOps Subgraphs docs](https://docs.graphops.xyz/subgraphs?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=related-subgraphs-docs) | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to avoid using "canonical gateway". I'd suggest removing that line completely and referencing the overview page or calling it "The Graph Foundation's gateway" or "the Foundation's gateway".