Self-service access
Build with hosted RPC, Subgraphs, and Substreams.
- Create an organization, add credits, and make your first request with an API key.
- Track service usage and manage your team’s access in one place.
Read chain state, query indexed entities, or stream blocks into your database with GraphOps RPC, Subgraphs, and Substreams.
JSON-RPC gRPC GraphQL Selected organizations GraphOps works with
Each service fits a different job. Many applications combine them, for example RPC for transactions and Subgraphs for the views users see.
Read chain state and submit transactions.
Build application views from indexed entities.
Backfill and stream data into your own systems.
Each solution follows one worked example, from the chain record to the decision your team makes.
Supply monitoring and holder applications for stablecoins and onchain assets.
40,000 USDC gap: 2 burns missed after a contract upgrade
Source transactions and event history for your monitoring and case systems.
Case REV-018: 2 evidence revisions kept
Balance reads and movement history for your treasury and reconciliation systems.
4 of 5 receipts matched to book entries
Build protocol dashboards, activity analysis, and historical reporting from entities or block streams.
15 transfers in one daily total, 4 mints and burns excluded
Support wallet interactions, product read views, and background event processing.
Five positions at block 1,100, health factor 3.00
Internal reporting integrations with technical and supplier evaluation.
2 report figures, each traced to block 1,100
Your team, API keys, usage and credits live in one organization. Every API key draws on the same credit balance, whichever service it calls.
Build with hosted RPC, Subgraphs, and Substreams.
Plan an integration around your product’s needs and operating constraints.