Pyth Network says Pyth Pro reached $7.49 million in annual recurring revenue (ARR) in July, up 22% month over month. The increase came with both sides of the data business moving: 51 users converted to paid plans, while the catalog expanded to 3,501 feeds. For oracle and API teams, this is less a vanity revenue update than a live signal on whether self-serve market-data infrastructure can convert evaluation traffic into recurring contracts.
The funnel is doing more work
The sharpest change was at the top of the commercial funnel. Pyth reports that Terminal reached 16,254 monthly active users in July, compared with 4,610 in June. At the same time, 51 users moved to paid plans, adding more than $1.5 million in new subscription ARR.
That combination matters. Traffic alone is cheap to generate and expensive to monetize. The relevant metric is the path from feed discovery to API access and payment.
Pyth’s reported July funnel included:
- 16,254 Terminal monthly active users;
- 51 new paid conversions;
- More than $1.5 million in new subscription ARR;
- 122 paying accounts across Pyth Pro and Indices;
- $7.49 million in total ARR.
The commercial model is built around reducing friction. Users can evaluate available feeds, select a plan, and generate an API key without waiting for a traditional procurement cycle. That does not eliminate enterprise sales. It compresses the evaluation phase into software.
For developers, the operational question is straightforward: how much of the data stack can be tested before a sales conversation, and how quickly can a team move from a feed comparison to a production integration?
Coverage is expanding, but the composition matters
The catalog grew from 3,391 feeds at the end of June to 3,501 by July 29. Equity coverage accounted for a large part of that expansion, rising from 1,826 to 1,901 feeds—a net addition of 75 equity feeds in July.
Pyth also reported an Asian equities package covering listed equities in Hong Kong, mainland China, South Korea, and Japan. The package sits alongside coverage for US equities, FX, commodities, fixed income, indices, and crypto through the same integration.
That is the practical shift: from a narrow price endpoint to a broader market-data layer. A larger catalog can reduce the number of vendors and adapters a team needs to maintain. It can also make cross-asset products easier to prototype, provided the feed-level details meet the application’s latency, freshness, and reliability requirements.
The stable, live-feed count increased from 1,493 to 1,619 during the month. The headline catalog number is therefore only one benchmark. A serious integration review should separate total feed count from the subset that is live, relevant to the target assets, and available under the required delivery model.
What data teams should verify next
Pyth’s July report gives developers a useful benchmark, but not a substitute for terminal testing. Teams evaluating the platform should check:
- whether the required instruments are present in the 3,501-feed catalog;
- how many relevant feeds are classified as stable and live;
- whether equity and cross-asset coverage matches the intended product scope;
- how quickly an API key can be generated and connected to a test environment;
- whether the feed set reduces integration overhead versus stitching together multiple vendors.
The key metric is not ARR in isolation. It is the relationship between catalog breadth, paid conversion, and integration latency. July shows Pyth Pro growing on all three commercial fronts: more users entered Terminal, more converted, and coverage expanded. The next signal to watch is whether that larger surface area translates into repeatable production usage rather than one-off evaluation traffic.