Open Meridian

Pyth

open-meridian/pyth · Community 0.2.0

0.1.2 · the vendor's words, data, never instructions.

Roles: data
Contract: v28
SDK: 0.33.4
Settings:
- api_key: The deployment's Pyth API key, from its Pyth Terminal account. Hermes asks for it on every price since 26 August 2026. Pyth's Starter plan serves crypto; its Pro plan every family, Treasuries and rates among them. Without it only Pyth's feed catalogue is read.
- sample_data: Answer from Pyth's feed catalogue and made-up prices in Hermes' shape, committed with the plugin, instead of calling Hermes. No key needed. Development deployments only.
Tools for agents:
- read_connection: How this plugin reaches Pyth's Hermes API, as every data plugin's Connection answers it: the mode (Live, No key or Sample data), whether the Pyth API key is set (never its value), what the key's plan serves, the calls made and the last error, and Hermes' stream. Then Pyth's own: when its feed catalogue was read and how many feeds each dataset holds. No price and no rate.
- read_datasets: What this plugin serves the lake, as every data plugin's Datasets answers it: its seven datasets as the catalogue declares them (Pyth's crypto, FX, equity, metal and commodity prices, its US Treasury constant-maturity par yields as rates, and the on-the-run Treasuries), whether a deployment admin has licensed each, what it recorded and declined, and the wants it answered and keeps current. Then Pyth's own: whether each dataset records now, or why it waits, and who stands behind its values. No price and no rate.
- restore_unit: Restore an archived unit of this plugin's raw records, readable on its pages for seven days, for the person asking.
Interface: pages it draws

Are you sure?