Choosing your integration path
All paths serve the same eight production indices. Fresh signed rounds are a
licensed pull (partner token, metered per read); rounds older than 24 hours
and everything verification needs — anchor, keysets, registry, verifier kit —
stay open, because the signed round is a portable artifact and verification
uses public material only.
On-chain (EVM venues)
The signing domain omitschainId and verifyingContract, so the same signed
round verifies on any chain. At onboarding we deploy the publisher that
carries verified signed rounds on-chain at their official effective time and
build the consumer contract with you — so the value your contract reads is the
signed round itself. Until then, pull rounds over HTTPS from the
signed-rounds service.
Off-chain feed
If you post your own oracle price (an internal oracle, or a HIP-3 style deployer feeding an L1), pull the value from the versioned Mecone API and post it:value is the index level in its natural unit, with a wire-stable decimal
string beside the JSON number; a snapshot is explicitly live_indicative, so
settle against rounds/latest or the
signed rounds, not against it. The legacy
curl https://api.mecone.trade/api/markets/us-gdp (index_now) contract
remains unchanged for existing pilots. Full field reference: API.