Latest filings and news that DeepSearch's risk model flags as medium or high risk for s…
Latest filings and news that DeepSearch's risk model flags as medium or high risk for specific Korean listed companies (lawsuits, trading halts, capital raises, accounting issues, labor disputes…), each with the affected tickers, a risk title and summary (Kor…
by x402.deepsearch.com · discovered, not yet claimed by its owner · updated 2026-10-01
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Latest filings and news that DeepSearch's risk model flags as medium or high risk for specific Korean listed companies (lawsuits, trading halts, capital raises, accounting issues, labor disputes…), each with the affected tickers, a risk title and summary (Korean). Use ?level=HIGH for high-risk only. Good for daily portfolio monitoring.
Tags: bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-01
{
"level": "MEDIUM"
}{
"count": 1,
"events": [
{
"companies": [
{
"name": "KS인더스트리",
"riskLevel": "HIGH",
"riskTitle": "KS인더스트리, 소송 관련 주요사항보고서 정정 공시 — 재무적 손실 리스크 존재",
"ticker": "101000"
}
],
"publishedAt": "2026-10-01T14:14:34+09:00",
"title": "[기재정정]주요사항보고서(소송등의제기)",
"type": "disclosure",
"url": "https://dart.fss.or.kr/…"
}
],
"language": "ko",
"market": "KR",
"minLevel": "MEDIUM",
"packType": "risk-radar"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/41983.jsonfor the price and payment options. - Pay. Call
GET https://x402.deepsearch.com/v1/context/risk-radar. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.05 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.05 | 0xbECc987508AdF6696A3254beD485CC2D9493C8AD | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xbECc987508AdF6696A3254beD485CC2D9493C8AD",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "50000",
"amountUsd": 0.05,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl -X GET 'https://x402.deepsearch.com/v1/context/risk-radar'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATUREconst res = await fetch("https://x402.deepsearch.com/v1/context/risk-radar", {
"method": "GET"
});
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.request("GET", "https://x402.deepsearch.com/v1/context/risk-radar")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- x402.deepsearch.com
- Endpoint
- https://x402.deepsearch.com/v1/context/risk-radar
- Machine-readable
/resources/41983.json