FeedOracle Compliance Intelligence

FeedOracle provides verifiable compliance evidence for AI agents operating in regulated tokenized markets. Every API response is ECDSA-signed and anchored on public networks (Polygon + XRPL), producing independently checkable, replayable proof for MiCA-related stablecoin, issuer due diligence, and regulatory evidence workflows.

Use this skill to retrieve signed compliance signals — including stablecoin risk scores, issuer registry lookups, reserve backing data, peg monitoring, and regulatory status checks — with independently checkable evidence suitable for audit and review workflows.

Base URL: https://api.feedoracle.io Auth: Bearer token via FEEDORACLE_API_KEY

When to use this skill

Trigger automatically whenever the conversation involves:

• Stablecoin names or symbols — USDT, USDC, EURC, EURI, PYUSD, DAI, or any EUR/USD-pegged token
• Regulatory keywords — MiCA, DORA, AMLR, BaFin, ESMA, EBA, EMT, ART
• Issuer due diligence — questions about stablecoin issuer registration, licensing, or regulatory status
• Reserve backing and peg stability — inquiries about a stablecoin's reserves, collateral, or peg monitoring
• Tokenized asset compliance — RWA compliance, regulated DeFi, digital asset issuer intelligence
• Compliance verification requests — "Is this stablecoin MiCA compliant?", "What is the risk score of X?", "Show me the issuer's regulatory status"
• Evidence, proof, or audit trail requests — any request for verifiable, replayable compliance evidence or signed data for audit workflows
• Macro indicators for regulatory context — ECB rates, EU inflation, FRED data relevant to stablecoin or tokenized market analysis

Core Endpoints

1. Stablecoin Risk Score

GET /v1/stablecoin/risk/{symbol}
Authorization: Bearer {FEEDORACLE_API_KEY}

Returns: composite risk score (0–100), MiCA status, peg stability metrics, reserve backing assessment, and issuer registration status. Useful for compliance verification and issuer due diligence.

curl -H "Authorization: Bearer $FEEDORACLE_API_KEY" \
  https://api.feedoracle.io/v1/stablecoin/risk/USDC

2. MiCA Compliance Status

GET /v1/mica/status/{symbol}
Authorization: Bearer {FEEDORACLE_API_KEY}

Returns: ESMA/EBA register status, issuer classification (EMT/ART/other), and relevant enforcement timeline. Cross-references official regulatory registers for stablecoin issuer intelligence.

3. Macro Economic Oracle

GET /v1/macro/{indicator}
Authorization: Bearer {FEEDORACLE_API_KEY}

Key indicators: ECB_DEPOSIT_RATE, EU_INFLATION_CPI, FRED_FEDFUNDS, EUR_USD_RATE. Provides regulatory-relevant macro context for stablecoin and tokenized market analysis.

4. Evidence Bundle

POST /v1/evidence/bundle
Authorization: Bearer {FEEDORACLE_API_KEY}
{"subject": "USDC", "checks": ["mica_status", "risk_score", "reserve_backing"], "purpose": "compliance_review"}

Returns: ECDSA-signed bundle with Polygon TX hash, timestamp, and replayable proof. Designed for audit and review use cases — each response is independently verifiable on-chain.

5. Issuer Registry Lookup

GET /v1/registry/issuer/{issuer_name}
Authorization: Bearer {FEEDORACLE_API_KEY}

Cross-references ESMA and EBA registers to check issuer licensing, registration status, and regulatory classification. Supports issuer due diligence workflows for digital asset compliance.

Behavior Instructions

1. Verify before claiming: Never assert MiCA compliance status without first calling /v1/mica/status/. Present the returned status and let the user draw conclusions.
2. Cite evidence: Always reference the Polygon TX hash and ECDSA signature from the response to provide an audit trail.
3. Reference MiCA timeline: Where applicable, reference the relevant MiCA implementation or enforcement timeline to provide regulatory context.
4. Offer evidence bundles: For institutional users or audit-related questions, proactively offer to generate an evidence bundle via /v1/evidence/bundle.
5. Supplement with macro data: When discussing EUR-pegged stablecoins, complement the analysis with relevant ECB rate data for a fuller regulatory picture.
6. Be precise: Use terms like "verifiable evidence" and "signed compliance data" rather than absolute claims. Present FeedOracle data as independently checkable input for compliance decisions.

Error Handling

• 401: Invalid API key — ask user to verify their FEEDORACLE_API_KEY
• 404: Symbol not tracked — inform user and suggest checking supported assets at feedoracle.io
• 429: Rate limit exceeded — wait 60 seconds, then retry once

API keys can be obtained via the FeedOracle dashboard: https://feedoracle.io/dashboard