Jobs and employers
Open postings with their full text, the employers behind them, and a changes feed that keeps a copy in sync, with dates a backtest can trust.
CompaniesSEC EDGARBy any name
A private borrower has no ticker and no filings of its own. It is a line in its lenders' schedules, spelled a little differently by each, often under a holding company named nothing like the business. The registry joins those lines into one company with one slug, the one every BDC book uses. Ask for any name: one we do not hold yet is searched for on EDGAR, and its lenders read.
Legal, trade and former names, from BDCs' 10-Qs and 10-Ks and EDGAR's own records.
$ pdatum companies resolve "Acme Midco, LLC" Acme Midco, LLC: acme-buyer-inc $ pdatum companies request "Zeta Holdings, LLC" no company we hold is named Zeta Holdings, LLC search: queued, asked 2026-10-14 16:20 Follow it with: pdatum companies resolve "Zeta Holdings, LLC" $ pdatum companies get acme-buyer-inc --json \ | jq -c '.held_by[] | {lender, book, first_as_of}' {"lender":"acme-capital","book":"direct","first_as_of":1664496000} {"lender":"zeta-lending","book":"direct","first_as_of":1703980800}
Illustrative: Acme, Zeta and the lenders are invented.
The questions the registry is built to answer, and the call that answers each.
resolve answers matched with the company's
slug, ambiguous with every candidate and never a choice
between them, or unknown. Case and spacing aside, a name
matches or it does not.
POST it. EDGAR's full text search finds the BDCs whose 10-Qs and 10-Ks write the name down, and each one we have not read is read. The request lists them, and says when it is done.
Every record lists the lenders that have reported holding the
company. One company's held_by gives each lender and book,
and the first and last quarter it was reported.
Always. When two companies turn out to be one, the slug folded away answers with the company it went into, and no other company is ever given it.
One company. The API reference has every parameter and an example of each.
company every
book table carries, and the name it reads best under.legal, the entity
that owes a security; trade, the name it goes by; or
former. Each with where and when we first read it.How the data behaves, in brief. The front page lists every source we read, and the API reference has the rest.
similar names to choose from.Open postings with their full text, the employers behind them, and a changes feed that keeps a copy in sync, with dates a backtest can trust.
The contracts and grants federal agencies have awarded any company you name, from USAspending.gov: how many, how much, from which agencies, and when the work ends.
Every loan a business development company reports each quarter, from its SEC filings, and how every other lender we read marks the same loan.
The layoff and closure notices states publish under the WARN Act, read every day and served in one shape: the employer, the place, how many people and when, linked to the companies lenders hold.
Franchisors' registrations and exemption notices with the states, every Texas filing back to 1985, with their brands, dates and status, linked to the companies lenders hold.
Every private capital raise a company has reported to the SEC on Form D since 2008: how much it offered, how much it sold and to how many investors, linked to the companies lenders hold.
Keys are issued by hand while the API is young. Write to pdatum@pearachute.com and say what you are building and which companies you need.