Use Cases

How organizations integrate FeedOracle data into compliance and reporting workflows

Home → Docs → Use Cases

FeedOracle data supports specific regulatory and operational workflows. The following use cases illustrate typical integrations and clarify the responsibility allocation between FeedOracle and data consumers.

1MiCA Art. 66 Sustainability Disclosure

The Problem

Crypto-Asset Service Providers (CASPs) operating under MiCA must publish sustainability information for crypto-assets they support. This requires structured data on energy consumption, GHG emissions, and consensus mechanisms—updated regularly and traceable for regulatory review.

How FeedOracle Data Is Used

CASPs integrate the Disclosure API to retrieve structured sustainability reports:

GET /api/v3/disclosure/sustainability/{symbol}

Response includes: energy consumption (kWh), emissions (tCO₂e), renewable percentage, GHG scope breakdown, consensus mechanism, and source attribution. Temporal metadata enables audit trail reconstruction. DAP attestation provides cryptographic proof of data delivery.

User Responsibility: Validating data applicability to specific disclosure obligations. Filing disclosures with competent authorities. Maintaining records of data sources. Independent verification where required by regulators.

2CSRD / ESRS ESG Reporting

The Problem

Companies subject to CSRD must report environmental impacts across their value chain, including crypto-asset holdings. ESRS E1 requires disclosure of energy consumption and GHG emissions by category.

How FeedOracle Data Is Used

ESG teams retrieve sustainability indicators mapped to ESRS requirements:

GET /api/v3/disclosure/sustainability/{symbol}

Data mapping: Energy metrics align with ESRS E1-5, emissions data aligns with ESRS E1-6. Coverage spans 54+ networks with documented methodology. Quality levels clearly indicate "third-party verified" (7 networks) vs "calculated" (47 networks).

User Responsibility: Mapping FeedOracle indicators to specific ESRS disclosure requirements. Determining materiality thresholds. Preparing narrative disclosures. Coordinating with auditors and retaining evidence.

3Exchange Sustainability Transparency Pages

The Problem

Crypto exchanges increasingly publish sustainability data for listed assets. Users and institutional clients expect accurate, sourced data with clear update frequencies and methodology transparency.

How FeedOracle Data Is Used

Exchanges integrate bulk or per-symbol endpoints for dashboard population:

GET /api/v1/carbon/chains
GET /api/v1/carbon/chain/{symbol}

Display elements include: energy per transaction, Green Score, consensus type, renewable percentage. Source badges and last-updated timestamps enable transparent attribution.

User Responsibility: Presenting data accurately without implying FeedOracle endorsement. Displaying source attribution and timestamps. Updating data at appropriate intervals. Handling user inquiries about methodology.

4AI & Autonomous Agent Data Consumption

The Problem

Autonomous systems (trading algorithms, DeFi protocols, AI agents) require verifiable sustainability signals for decision-making. Traditional data sources lack machine-verifiable provenance, creating trust issues for automated workflows.

How FeedOracle Data Is Used

Agents consume any FeedOracle API with DAP attestation enabled:

GET /api/v3/disclosure/sustainability/{symbol}
GET /verify/{attestation_id}

Response includes attestation ID linking to on-chain Merkle proof. Agents verify data authenticity by checking attestation against smart contracts on Polygon, Base, Arbitrum, or Ethereum. JSON format with embedded attestation block enables fully automated verification.

User Responsibility: Implementing attestation verification logic. Defining decision thresholds and criteria. Logging data consumption for audit purposes. Handling verification failures gracefully.

Integration Support

For enterprise integrations, custom use cases, or technical questions: