Access Policy

IRGO Feed serves Korean public company IR data to two distinct visitor types — humans (developers, analysts, retail investors) and AI agents (MCP clients, automated callers). This page makes the rules explicit for both. Last reviewed: 2026-05-17.

Section 1 — Human Access

For developers, financial analysts, and retail investors using IRGO Feed through a browser, REST API, or Claude Desktop with MCP installed under their own account.

1.1 Sign-up & API Key

A free API key is issued after a 60-second sign-up at irfeed.dev/#beta. No credit card is required for free-tier usage. The key is a Supabase anon key scoped to the IRFeed read-only API; it can be revoked and rotated from the user's account at any time.

1.2 Free tier — Top 10 Korean stocks, forever

The four baseline tools are free forever, with no per-call charges, for the following tickers (KRX codes):

TickerCompanyExchange
005930Samsung ElectronicsKOSPI
000660SK HynixKOSPI
005380Hyundai MotorKOSPI
373220LG Energy SolutionKOSPI
207940Samsung BiologicsKOSPI
035420NAVERKOSPI
035720KakaoKOSPI
068270CelltrionKOSPI
005490POSCO HoldingsKOSPI
105560KB Financial GroupKOSPI

1.3 Beyond the free tier — Tiered pricing

For the rest of KOSPI and KOSDAQ, IRFeed uses a tiered free model:

1.4 Payment rails

Pay.sh (agent payment marketplace, launched 2026-05-05), Coinbase x402 (HTTP-native agent payments), and Stripe (standard human card). Choice depends on caller type — see Section 2.5 for the agent-side billing trigger.

1.5 Rate limit

Default rate limit: 60 calls per minute per API key. Burst up to 120 calls/min is tolerated. For higher throughput, contact contact@irfeed.dev.

1.6 Data license

Converted Markdown + JSON output is released under CC BY 4.0 — free for commercial and non-commercial use with attribution. The original IR PDFs remain under the copyright of the issuing companies; verify investment decisions against original filings.

Section 2 — Agent Access

For autonomous AI agents (Claude, ChatGPT, Cursor, Cline, Continue, and any MCP-compatible client) that consume IRFeed tools on behalf of a user or another agent.

2.1 Four baseline read-only tools

The contract is locked under stable API. New tools may be added based on observed call patterns; existing tool signatures are not silently broken.

2.2 Authentication

stdio transport with environment variables IRFEED_SUPABASE_URL and IRFEED_SUPABASE_ANON_KEY. RLS enforces read-only on the agent path. No service-role token is ever passed through the MCP layer.

{
  "mcpServers": {
    "irfeed": {
      "command": "npx",
      "args": ["-y", "irfeed-mcp"],
      "env": {
        "IRFEED_SUPABASE_URL": "<from /#beta>",
        "IRFEED_SUPABASE_ANON_KEY": "<from /#beta>"
      }
    }
  }
}

2.3 Free-forever rules — what is never billed

The pricing engine reads three fields on every call and refuses to bill if any of these apply. This is enforced server-side; agent callers do not need to opt in.

2.4 Billing trigger (data delivery only)

The minimal predicate that triggers a $0.0001/call charge:

(tool_name IN ('get_filing', 'get_key_figures'))
  AND (http_status = 200)
  AND (payload_size > 256 bytes)
  AND (ticker NOT IN <free_tier_10>)
  AND (account_data_calls_so_far >= 100)

2.5 Canonical agent-facing URLs

PurposeURL
llms.txt (service summary)https://irfeed.dev/llms.txt
MCP server cardhttps://irfeed.dev/.well-known/mcp/server-card.json
Schema.org JSON-LDEmbedded in homepage
robots.txt (AI bot allow)https://irfeed.dev/robots.txt
npm packageirfeed-mcp
Source repokoreafintech/ir-feed

2.6 Rate limit for agents

Same as Section 1.5 (60 calls/min per API key, burst 120). The MCP layer does not add an artificial slowdown beyond this. Honest crawlers and well-behaved agents stay well inside the limit.

2.7 Data quality signals

Every get_filing response carries:

2.8 Abuse / fair use

Honest scraping for AI-assisted research is welcomed. Bulk re-distribution of the converted dataset without attribution, or attempts to circumvent the metering rules, may result in API key revocation. Contact us before doing anything unusual; we are happy to discuss licensing.

Section 3 — Shared resources

This policy is reviewed quarterly. Material changes are announced via the changelog section of llms.txt and on @IRAIFeed.