API Documentation

What FeedOracle Is

FeedOracle is an independent data provider for RWA risk intelligence, compliance data, and sustainability indicators. We aggregate, structure, and deliver machine-readable data designed for disclosure and reporting workflows.

Core Function

• Aggregates sustainability data for 50+ blockchain networks
• Structures data for regulatory frameworks (MiCA, CSRD/ESRS)
• Provides cryptographic attestation via the DAP protocol
• Documents methodology, sources, and data quality transparently

What FeedOracle Is NOT

Responsibility Allocation

• FeedOracle: Delivers data as documented, maintains stated methodologies, provides signed evidence artifacts
• Data User: Validates suitability, ensures compliance, bears disclosure responsibility

Who Uses FeedOracle

FeedOracle APIs serve organizations requiring RWA risk scoring, compliance data, and sustainability indicators for compliance, reporting, and operational workflows.

Architecture

FeedOracle operates as a layered data infrastructure. For detailed documentation, see Architecture Overview.

Layer 5: EVIDENCE         ECDSA Signatures, Evidence Packs, Multi-Chain Anchoring
Layer 4: REGISTER EVIDENCE  MiCA Register Lookup, ISO 20022, Circuit Breaker, CCI Score
Layer 3: API GATEWAY      REST endpoints, authentication, rate limiting, OpenAPI 3.1
Layer 2: PROCESSING       Normalization, quality scoring, confidence calculation
Layer 1: DATA SOURCES     Blockchain RPCs, CCRI, DeFiLlama, GeckoTerminal, FRED, ECB, World Bank, Ankr

Authentication

Include your API key in the request header:

X-API-Key: YOUR_API_KEY

Auth Semantics

• Public (ignore X-API-Key): /api/v2/verify/*, /api/v2/snapshots/*, /api/v2/quality/status, /api/v2/l2/*
• Tier-gated (require key): /api/v2/webhooks*, /api/v2/exports*
• Enterprise-only: /api/v2/enterprise/pack

Note: Public endpoints ignore X-API-Key if provided. Do not send keys to public endpoints unless required by internal policy.

Clarification: Verification (reading existing attestations) is public. EPM generation (creating new Evidence Pack Manifests) is tier-limited — see Pricing.

Get your API key at /pricing.

Base URL

https://feedoracle.io

MCP Servers 3 SERVERS · 44 TOOLS

FeedOracle provides three Model Context Protocol (MCP) servers that give AI agents direct access to regulatory compliance, stablecoin operational risk, and macroeconomic intelligence. Any MCP-compatible client — Claude Desktop, Cursor, Windsurf, or custom agents — can connect instantly.

Compliance Server (18 tools)

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "feedoracle-compliance": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://feedoracle.io/mcp/sse"]
    },
    "feedoracle-macro": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://feedoracle.io/mcp/macro/sse"]
    },
    "feedoracle-risk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://feedoracle.io/mcp/risk/sse"]
    }
  }
}

Terminal (one-liner)

# Compliance Server (MiCA, DORA, evidence)
npx -y mcp-remote https://feedoracle.io/mcp/sse

# Macro Intelligence Server (FRED, yields, regime)
npx -y mcp-remote https://feedoracle.io/mcp/macro/sse

# Stablecoin Risk Server (7-signal scoring, 28+ tokens)
npx -y mcp-remote https://feedoracle.io/mcp/risk/sse

Compliance Tools (18)

Verdicts

Response Schema

Every tool returns a unified envelope with cryptographic signing:

{
  "schema_version": "2.1.0",
  "tool": "compliance_preflight",
  "request_id": "fo-d2e33f04f33f",
  "timestamp": "2026-02-20T11:57:51Z",
  "decision": "PASS",
  "reason_codes": ["ALL_CHECKS_PASSED"],
  "confidence": 1.0,
  "evidence": { ... },
  "sources": [{"registry": "...", "fetched_at": "..."}],
  "meta": {"ttl_seconds": 300, "data_freshness": "live", "jurisdiction_scope": "EU"},
  "signature": {"alg": "HMAC-SHA256", "sig": "...", "kid": "fo-hmac-v1"}
}

MCP Tier Availability

API Availability by Tier

Carbon Monitor API

MiCA Disclosure API (v3)

RWA Health Monitor

Macro Economic Oracle 54 ENDPOINTS

86 FRED series + 10 ECB series across 12 categories. Full Macro API Docs →

Verified Reports API

Evidence Report Generation 5 ENDPOINTS

Signed PDF evidence. SHA-256 + ECDSA + XRPL. Evidence Terminal

Carbon Data

{
  "count": 54,
  "timestamp": 1739836800,
  "chains": [{
    "symbol": "ETH",
    "chain": "Ethereum",
    "consensus": "Proof of Stake",
    "energy_twh_year": 0.0026,
    "co2_mt_year": 0.0013,
    "renewable_energy_percent": 52,
    "green_score": 85,
    "data_quality": "THIRD_PARTY_VERIFIED",
    "data_source": "CCRI"
  }]
}

Disclosure API v3 DAP

DAP - Disclosure Attestation Protocol NEW

Cryptographic proof of what data was delivered, when it was delivered, and that it has not been altered. Every API response is hashed, aggregated into Merkle trees, and anchored on-chain.

Blockchain Anchoring

Report hashes anchored as XRPL memo fields. Verify via xrpscan.com.

MOAT v2 Evidence NEW

Verify, Snapshots, Quality. Full docs →

Webhooks PRO+

Real-time events. Full docs →

S3 Exports PRO+

Export to your S3. Full docs →

L2 Intelligence NEW

Fee Oracle + Health. Full docs →

Enterprise Features ENTERPRISE

PDF Disclosure Reports (Professional+)

curl -H "X-API-Key: KEY" "https://api.feedoracle.io/api/v2/reports/mica-art66" -o report.pdf

Data Disclaimer

FeedOracle provides data for informational purposes to support regulatory disclosure obligations. This data does not constitute legal, financial, tax, or compliance advice.

Data Quality Levels

• Third-Party Sourced: Data obtained from established external providers (Cambridge CBECI, CCRI, DNV) who maintain independent data collection methodologies. "Verified" refers to source integrity, not audit or certification. Source attribution provided.
• Calculated: Data computed by FeedOracle using documented methodologies. Methodology available upon request.

User Responsibility

Data users are solely responsible for:

1. Validating data suitability for their specific use case
2. Ensuring compliance with applicable regulations
3. Accuracy of disclosures to competent authorities
4. Independent verification where required by their regulatory framework

Standard API Response Footer

{
  "legal": {
    "disclaimer": "Data provided for informational purposes only.",
    "responsibility": "User remains solely responsible for regulatory compliance.",
    "data_quality": "THIRD_PARTY_SOURCED | CALCULATED",
    "source": "Source attribution",
    "timestamp": "ISO 8601 timestamp",
    "terms": "https://feedoracle.io/terms.html"
  }
}

Language Guidelines

FeedOracle maintains strict language standards for legal and regulatory safety.

Forbidden Phrases

Allowed Alternatives

Use Cases

For detailed integration examples, see the Use Cases documentation.