How Do I Find My CUSIP Number? Check These Places First
Where to actually find the CUSIP for a security you own, why mutual funds are different, and when a free SEC filings lookup can and cannot help.
- The fastest way to find a CUSIP you need is your brokerage account statement or trade confirmation, which lists it next to every position.
- A paper stock certificate prints its CUSIP on the face, alongside the certificate number and share count.
- Open-end mutual fund shares are explicitly excluded from the SEC's Official List of Section 13(f) Securities, so free EDGAR-based tools built on 13F data will not surface a mutual fund's CUSIP.
- A free SEC filings lookup can confirm which issuer a CUSIP belongs to, but it cannot produce a new CUSIP from a ticker or company name alone.
If you need the CUSIP for a security you already own, the fastest answer is almost never a public database. It is already printed on paperwork you have: your brokerage statement, a trade confirmation, or a stock certificate. Public SEC filings are a backup for a narrower case, confirming or looking up a CUSIP for a security you do not hold a statement for, and they only work one way.
This guide covers where your own CUSIP actually comes from, why a mutual fund is a different case entirely, and how far a free SEC filings lookup can take you when you do not have the paperwork in hand.
Check your account statement or trade confirmation first
Every position on a brokerage account statement, and every trade confirmation a broker sends after an order fills, is keyed to a CUSIP, because that is how US clearing and settlement systems identify securities internally. The CUSIP is usually printed in small text next to or below the security's name and ticker, sometimes labeled explicitly, sometimes just as a nine-character code. This is the most direct source because it is the exact CUSIP your custodian has on file for your specific position, not a lookup that has to match a name.
If you hold a paper stock certificate
A physical stock certificate prints its CUSIP on the face of the certificate itself, alongside the certificate number and the number of shares it represents. Specimen certificates filed as exhibits to SEC registration statements show this layout; it is standard across issuers, not specific to any one company. If you are holding a certificate from a company that has since merged, reincorporated, or done a stock split, check whether the CUSIP on an old certificate is still current. Corporate actions can retire a CUSIP and assign a new one to the surviving security, which is why some exchange offers explicitly warn holders not to assume an old certificate's CUSIP still matches the actively traded security.
Get this data as clean JSON
SecFeed turns SEC filings into structured data with one API call: GET /v1/mapping/cusip?cusip=037833100. 125 free calls to start.
For a mutual fund, the answer is different
If the security you are trying to find a CUSIP for is an open-end mutual fund share, not a stock or ETF, free EDGAR filings will not help. The SEC's own Form 13F guidance excludes open-end investment company shares, meaning mutual funds, from the Official List of Section 13(f) Securities, so they are never reported on a 13F holdings table. Since 13F data is the main free source EDGAR offers for CUSIP information, a mutual fund's CUSIP simply will not turn up there, no matter how the search is phrased. For a mutual fund, your account statement, trade confirmation, or the fund's own prospectus is the only practical free source. Closed-end funds and ETFs are different: both are Section 13(f) securities and do show up in 13F holdings tables, so an EDGAR-based lookup works for them the same way it works for ordinary stocks.
If you only have a ticker or company name, not a statement
This is the case a free SEC filings lookup is actually built for: you know the company, but you do not have a statement in hand and want to confirm or find the CUSIP it reports under. Schedule 13D and 13G cover pages and Form 13F holdings tables both require the CUSIP of the security being reported, so EDGAR ends up being a free, practical source, with one important limit.
The lookup only works one direction
A filings-based CUSIP tool, including SecFeed's own, matches a CUSIP to the issuer name and ticker reported alongside it in those filings. It cannot do the reverse on demand, generating a brand-new CUSIP purely from a ticker or company name, because the CUSIP itself is assigned by CUSIP Global Services, not by the SEC, and a filings-based tool only knows a CUSIP once some filer has already reported it. In practice this means: if a security has appeared in a 13F holdings table or a Schedule 13D or 13G, its CUSIP is there to find by issuer name. If it has not, there is nothing for a free filings lookup to return, however the company name is phrased.
A worked example
Confirming a CUSIP you already have is the direction this actually supports well. Here is a lookup for Apple's common stock CUSIP:
curl "https://secfeedapi.com/v1/mapping/cusip?cusip=037833100" \
-H "Authorization: Bearer YOUR_API_KEY"
[
{
"cusip": "037833100",
"issuerName": "APPLE INC",
"matches": [
{"cik": 320193, "name": "Apple Inc.", "ticker": "AAPL", "exchange": "Nasdaq"},
{"cik": 1418121, "name": "Apple Hospitality REIT, Inc.", "ticker": "APLE", "exchange": "NYSE"}
]
}
]
Note the second match. Issuer names in 13F filings are not always unique, so a CUSIP lookup by name alone can return more than one company with a similar name. The CUSIP itself, once confirmed against the right CIK and ticker, is unambiguous; the name match around it is not. See CUSIP Lookup: Find a Security's CUSIP From SEC Filings for the full field reference and /v1/mapping/cusip for the endpoint.
Where to look, by what you already have
| What you have | Where to find the CUSIP |
|---|---|
| A brokerage account statement or trade confirmation | Printed directly on the document, next to the position |
| A paper stock certificate | Printed on the certificate face, next to the certificate number |
| A stock or ETF, no statement in hand | EDGAR 13F holdings tables or Schedule 13D/13G, free, by issuer name |
| A closed-end fund | Same as a stock; it is a Section 13(f) security |
| An open-end mutual fund | Account statement or the fund's prospectus; not covered by 13F data |
| A bond | See Bond CUSIP Lookup, coverage depends on how it was offered |
Frequently asked questions
Does the SEC assign or maintain CUSIP numbers?
No. CUSIP numbers are issued and maintained by CUSIP Global Services on behalf of the American Bankers Association. The SEC requires certain filings to report a security's CUSIP, but does not assign the numbers itself.
Why can't I find my mutual fund's CUSIP on EDGAR?
Open-end mutual fund shares are explicitly excluded from the SEC's Official List of Section 13(f) Securities, so they are never reported in a Form 13F holdings table, which is the main free, filings-based source of CUSIP data. Check your account statement or the fund's prospectus instead.
Is the CUSIP the same as my account number?
No. A CUSIP identifies the security itself, the same for every investor who owns it. Your account number identifies your brokerage account, and is specific to you.
Can I look up a CUSIP by company name instead of ticker?
Yes, if the security has already appeared in a 13F holdings table or a Schedule 13D or 13G filing. Keep in mind issuer names in filings are not always unique, so confirm any match against the company's CIK and ticker before relying on it.
What if the CUSIP on an old certificate does not match what I find online?
Corporate actions like mergers, reincorporations, and some stock splits can retire a CUSIP and assign the surviving security a new one. If a certificate predates a corporate action, check with the company's transfer agent before assuming the old CUSIP is still current.
Get this data as clean JSON
SecFeed turns SEC filings into structured data with one API call: GET /v1/mapping/cusip?cusip=037833100. 125 free calls to start.
For information only, not investment advice. Data from public SEC filings; verify important figures on SEC.gov. See our AI Disclosure.