78trust / 100
Disclosures By Ticker
by Korea Filings in Markets & finance
x402 APIPassing, checked 3 h ago
AI summaries for the most recent DART filings of a Korean ticker
GET
https://api.koreafilings.com/v1/disclosures/by-ticker- Price
- $0.025
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 225 ms
- 294 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
All checks passedSome failedAll failedNot checked
How to call it
GET https://api.koreafilings.com/v1/disclosures/by-ticker
Each call costs $0.025 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
Built from the input schema. Replace the values with your own.
GET https://api.koreafilings.com/v1/disclosures/by-ticker?ticker=exampleParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Max filings to return (1–50, default 5). Final price is 0.005 × limit USDC. Note: the agent is charged for limit, not for the actual row count returned. A ticker with fewer recent filings than limit still costs the full amount; pre-filter via the free /v1/disclosures/recent feed if budget is tight.… |
ticker | string | Yes | Six-digit KRX ticker (e.g. 005930 for Samsung Electronics). Resolve from a company name first via the free /v1/companies?q={name} endpoint. |
Example response
The provider's example. We can't check it without paying.
{
"chargedFor": 5,
"count": 1,
"delivered": 1,
"summaries": [
{
"actionableFor": [
"traders"
],
"eventType": "OTHER",
"generatedAt": "2026-04-24T09:00:00Z",
"importanceScore": 7,
"rcptNo": "20260424900874",
"sectorTags": [
"Capital Goods"
],
"summaryEn": "AI-generated English summary of the disclosure.",
"tickerTags": [
"095440"
]
}
],
"ticker": "005930"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.025.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.koreafilings.com/v1/disclosures/by-ticker?ticker=example'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://api.koreafilings.com/v1/disclosures/by-ticker?ticker=example' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.025 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.025" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.025 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.koreafilings.com%2Fv1%2Fdisclosures%2Fby-ticker
const res = await pay("https://api.koreafilings.com/v1/disclosures/by-ticker?ticker=example");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.025 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.025"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://api.koreafilings.com/v1/disclosures/by-ticker?ticker=example")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 226 ms | $0.025 |
| 7 h ago | Passed | 402 | 146 ms | $0.025 |
| 12 h ago | Passed | 402 | 325 ms | $0.025 |
| 16 h ago | Passed | 402 | 245 ms | $0.025 |
| 19 h ago | Passed | 402 | 237 ms | $0.025 |
Show 10 older checks
| 23 h ago | Passed | 402 | 222 ms | $0.025 |
| 27 h ago | Passed | 402 | 160 ms | $0.025 |
| 31 h ago | Passed | 402 | 225 ms | $0.025 |
| 35 h ago | Passed | 402 | 273 ms | $0.025 |
| 39 h ago | Passed | 402 | 216 ms | $0.025 |
| 42 h ago | Passed | 402 | 294 ms | $0.025 |
| 46 h ago | Passed | 402 | 176 ms | $0.025 |
| 2 days ago | Passed | 402 | 242 ms | $0.025 |
| 2 days ago | Passed | 402 | 189 ms | $0.025 |
| 2 days ago | Passed | 402 | 210 ms | $0.025 |