Api Endpoint

Pocket Network

Korean listed-company disclosures from OpenDART: filings tagged original, correction or withdrawal, corrections linked to originals with term diffs, and a point-in-time view. GET /v1/corp?name=, /v1/filings, /v1/changes, /v1/asof with an 8-digit corp_code, or POST /v1/query with a question in Korean or English. Pay per request in USDC; no account, no API key.

Open interactive test console

Offering

Provider
agent.pocket.network
Method
POST
Offering type
Api Endpoint
Transport type
http
Category
Financial Analysis
Delivery
Not provided
Pricing model
Not provided
x402 version
2

Endpoint context

URL
https://agent.pocket.network/v1/dart-kr-events-v1
MIME type
application/json
First seen
2026-10-16T01:50:19.913Z
Last seen
Tags
Finance, dart-kr-events-v1, rest

Payment pricing

x402 payment terms are the authoritative price for calling this endpoint.

Payment option 1
0.005 USDC
Atomic price: 5000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Raw x402 terms
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "5000",
    "payTo": "0xF732ea490c5766071785a2310523f7fA2CEbB829"
  }
]

Observed health

Status
Reachable
Latest latency
418 ms
Average latency
658 ms
HTTP status
405
Last checked
Reachability
100% over 11 checks

Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.

Input schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "const": "http"
    },
    "method": {
      "type": "string",
      "enum": [
        "POST",
        "PUT",
        "PATCH"
      ]
    },
    "bodyType": {
      "type": "string",
      "enum": [
        "json",
        "form-data",
        "text"
      ]
    },
    "body": {
      "type": "object",
      "description": "The body of POST /v1/query. The GET routes take the same fields as query parameters: /v1/corp takes name or stock_code; /v1/filings takes corp_code with optional from and to; /v1/changes takes corp_code and since; /v1/asof takes corp_code, date and optional lookback_days (7-365, default 120).",
      "properties": {
        "question": {
          "type": "string",
          "description": "A question in Korean or English. Name the company, or pass corp_code, name or stock_code alongside it."
        },
        "corp_code": {
          "type": "string",
          "description": "8-digit DART company code (look it up with GET /v1/corp)."
        },
        "name": {
          "type": "string",
          "description": "Company name, e.g. 삼성전자."
        },
        "stock_code": {
          "type": "string",
          "description": "6-digit KRX stock code, e.g. 005930."
        },
        "since": {
          "type": "string",
          "description": "YYYYMMDD start date for changes."
        },
        "date": {
          "type": "string",
          "description": "YYYYMMDD date for the point-in-time view."
        }
      }
    }
  },
  "required": [
    "type",
    "method",
    "bodyType",
    "body"
  ],
  "additionalProperties": false
}

Output schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string"
    },
    "example": {
      "type": "object",
      "properties": {
        "portal": {
          "type": "object",
          "properties": {
            "provenance": {
              "const": "third-party-supplier"
            },
            "serviceId": {
              "const": "dart-kr-events-v1"
            },
            "schemaCheck": {
              "enum": [
                "passed",
                "undeclared",
                "unchecked"
              ]
            }
          },
          "required": [
            "provenance",
            "serviceId",
            "schemaCheck"
          ]
        },
        "data": {
          "type": "object",
          "description": "A JSON object tagged with its own `schema` (dart-corp/v1, dart-filings/v1, dart-changes/v1, dart-asof/v1, dart-answer/v1). POST /v1/query answers intent, status (OK or NEEDS_CLARIFICATION with a `missing` list) and the matching data."
        }
      },
      "required": [
        "portal",
        "data"
      ]
    }
  },
  "required": [
    "type"
  ]
}