edgar_ticker_to_cik

Pack: edgar · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/edgar_ticker_to_cik for the schema, then POST the same URL with its arguments for the data.

The SEC CIK number for a stock ticker or company name, from EDGAR’s company list.

Tool description as the model sees it

Resolve a US stock ticker (e.g. “TSLA”) OR a company name (e.g. “Tesla”, “Apple Inc”) to the SEC’s 10-digit CIK identifier — required by every other SEC tool. Call THIS FIRST when you have a ticker/name and need to use edgar_company_concept, edgar_company_filings, edgar_company_facts, sec_8k_recent, or any other SEC-keyed tool. Returns {cik, cik_padded, company_name, ticker, matched_by}; when matched by name it also returns alternatives — up to 3 OTHER companies whose names also matched, one per distinct CIK, with the winner’s OWN share classes/tickers excluded (never listed as its own alternative). Use alternatives to tell a genuinely CONTESTED name match (a real rival company also matched) from a clean one (nothing else did). Cheap, no rate limit concerns. Most other tools also accept tickers/names directly and call this internally — only use it explicitly when you want the CIK as data. The response carries a next hint: the usual NEXT step after resolving is edgar_company_snapshot({ticker_or_cik}), which returns the recent filings list AND the headline XBRL financials in one call — do not chain edgar_company_filings then edgar_company_concept by hand to get that.

Parameters

NameTypeRequiredDescription
tickerstringnoREQUIRED (or one of its aliases ticker_or_cik / company). Stock ticker symbol (e.g., “AAPL”, “MSFT”, “TSLA”) or company name (e.g., “Apple”, “Microsoft”)
ticker_or_cikstringnoAlias for ticker — the spelling edgar_company_filings and edgar_insider_transactions use. A ticker or company name; this tool RESOLVES to a CIK, so passing a bare CIK has nothing to look up.
companystringnoAlias for ticker — use it when what you have is a company NAME (“Apple Inc.”) rather than a symbol. Same argument, same behaviour.

Example call

Arguments

{
  "ticker": "AAPL"
}

curl

curl -X POST https://gateway.pipeworx.io/edgar/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"edgar_ticker_to_cik","arguments":{"ticker":"AAPL"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('edgar_ticker_to_cik', {
  "ticker": "AAPL"
});

More examples

{
  "ticker": "TSLA"
}

Response shape

Always returns: ticker, cik, cik_padded, company_name

FieldTypeDescription
tickerstring | nullStock ticker symbol; null for a filer not on SEC’s current-listed list (delisted, bankrupt, never listed) resolved by name via matched_by “edgar_entity_search”
cikstringCompany CIK number
cik_paddedstringCIK padded to 10 digits with leading zeros
company_namestringOfficial company name
Full JSON Schema
{
  "type": "object",
  "properties": {
    "ticker": {
      "type": [
        "string",
        "null"
      ],
      "description": "Stock ticker symbol; null for a filer not on SEC's current-listed list (delisted, bankrupt, never listed) resolved by name via matched_by \"edgar_entity_search\""
    },
    "cik": {
      "type": "string",
      "description": "Company CIK number"
    },
    "cik_padded": {
      "type": "string",
      "description": "CIK padded to 10 digits with leading zeros"
    },
    "company_name": {
      "type": "string",
      "description": "Official company name"
    }
  },
  "required": [
    "ticker",
    "cik",
    "cik_padded",
    "company_name"
  ]
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the edgar pack
{
  "mcpServers": {
    "edgar": {
      "url": "https://gateway.pipeworx.io/edgar/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 30, 2026