# Rocketlist > Rocketlist is a free job matching service for startup and tech roles. Candidates > build a profile (including importing a LinkedIn profile), and Rocketlist ranks > active jobs from its catalogue against that profile using a 0-100 match score > based on skills, experience, seniority, location, domain fit, role type, and > compensation. Job listings are refreshed from public company career pages and applicant tracking systems. Rocketlist is free for candidates: sign up, view matched jobs, save roles, and receive match updates at no cost. Measured 2026-08-29, the catalogue held 110,312 live, active, non-duplicate job listings across 4,967 companies. This file is static, so that is a dated measurement rather than a live count: GET /api/headline-stats for the current numbers. ## MCP server Rocketlist runs a public, read-only Model Context Protocol server. It needs no account, no API key and no OAuth. - Endpoint: https://rocketlist.ai/mcp - Transport: Streamable HTTP. POST JSON-RPC to that URL. The same URL also answers a GET as the older HTTP+SSE handshake, for clients that need it. - Discovery document: https://rocketlist.ai/.well-known/mcp.json - Rate limit: 60 requests per minute per IP. Over that the server answers HTTP 429 with a Retry-After header. Bursts are shaped at the proxy on top of that, and the proxy's 429 carries no Retry-After, so pace requests instead of spending the whole minute at once. Tools, all read-only and none of them personal: - search_jobs — search active postings by free text, skills, industry, city, remote-only, investor, company funding stage and years-of-experience range. - get_job — one job posting, by slug or by UUID. It resolves deactivated postings as well and does not flag them; GET /api/public/jobs/{id} returns a listing_closed field if you need to know. - search_companies — search hiring companies by name, investor or funding stage. Only companies with at least one active job are returned. - get_company — one hiring company by UUID, with up to ten of its most recent active jobs. Most hiring companies have fewer than ten. - hiring_stats: counts over every matching active job, not a sample: totals, the top cities, countries, companies, verticals, stages, work modes, categories and seniority levels, and published pay with sample sizes. There is a second, authenticated server at https://rocketlist.ai/mcp/private that reads a signed-in candidate's own matches and saved jobs. It requires a personal token created at /account/mcp and cannot be used anonymously. ## HTTP API The unauthenticated read endpoints are described at https://rocketlist.ai/openapi.json. Most of Rocketlist's API is per-user and returns 401 without a session, so that document is deliberately short. The MCP server above covers the same catalog with less bookkeeping. ## Key sections - /jobs — searchable job listing index - /jobs/[id] — individual job postings with full descriptions - /companies — companies hiring now, with funding, location, and team info - /startup-jobs and role/location hub pages (e.g. /software-engineer-startup-jobs, /remote-startup-jobs, /berlin-startup-jobs, /london-startup-jobs, /new-york-startup-jobs, /san-francisco-startup-jobs) — curated job listings by role and location - /faq — how matching works, sourcing, data handling, and pricing - /how-it-works — product walkthrough - /investors — investor-facing pages - /for-companies — information for companies wanting to hire through Rocketlist - /insights — data reports built from public sources, starting with the YC mortality report below - /yc-founders — searchable directory of Y Combinator founder profiles, built from the same snapshot as the YC mortality report - /founders-inc — searchable directory of Founders Inc portfolio founders, built the same way from f.inc's own public portfolio pages ## Y Combinator dataset Rocketlist publishes a Y Combinator dataset in two forms: a report at /insights/yc-mortality-table and a searchable founder directory at /yc-founders. Both are built from the same frozen snapshot, captured 2026-09-02: 6,201 YC companies from the public yc-oss.github.io company index, and 11,230 founder profiles harvested from the LinkedIn links Y Combinator renders in plain HTML on each of its own company pages (ycombinator.com/companies/). Those 11,230 people hold 11,513 founder-company roles, since a person who did YC more than once is one founder and several roles; per-person figures use 11,230 and per-company figures use 11,513. Founders are listed on 5,974 of the 6,201 companies (96.3% coverage); 269 people appear as founders of more than one YC company. No paid data source and no authenticated scraping went into either page: every row traces back to a URL any browser can load without signing in. The report carries per-chart caveats about what a cross-section (no history, today's value only) cannot support. One caveat applies to the whole dataset and is worth restating here: the region field on a company is that company's current location, not founder nationality. A founding team that relocated is counted where it operates today, not where it started, and the dataset draws no conclusion about where founders are from. Both pages carry schema.org Dataset JSON-LD under a CC BY 4.0 licence. The directory's CSV export (/api/yc-founders/export) is gated to signed-in accounts; the HTML directory and the report itself are open to anyone, including crawlers. ## Founders Inc dataset Rocketlist publishes a second accelerator dataset, built the same way as the Y Combinator one but NOT offered on the same licence terms, see the end of this section: a searchable directory of the Founders Inc (f.inc) portfolio at /founders-inc, captured 2026-09-04. It covers 335 founders across 192 portfolio companies in 8 industries. 295 list a LinkedIn profile and 234 list an X account; 30 list neither, recorded as an absence rather than filled in from elsewhere. 9 of the companies have a Rocketlist company page and link to it; the rest link to their Founders Inc page, because the Rocketlist catalog is job-driven and only holds companies that have posted a role. A portfolio company is matched to its Rocketlist company page by registrable website domain, never by name or slug. Both sides slugify a company name, so slugs agree often enough to be tempting and collide often enough to be wrong. Founders Inc renders its portfolio pages in the browser, so the served HTML carries no founder data at all. Each page is loaded in a headless browser before it is read, and the name, X handle and LinkedIn link are taken from one founder block on one company page, which is why a LinkedIn account and an X account are paired only because Founders Inc lists them on the same person. A person who founded more than one portfolio company is one row, with the other companies named on it. No paid data source and no authenticated scraping. The directory carries schema.org Dataset JSON-LD, deliberately with no licence declared. The YC dataset above is offered under CC BY 4.0; this one is not, because it is read off Founders Inc's own pages and Founders Inc reserves rights over that content. Rocketlist claims no redistribution right it was not granted, so it asserts none. Every row links back to the source page it came from. Its CSV export (/api/founders-inc/export) is gated to signed-in accounts; the HTML directory is open to anyone, including crawlers. These figures are reconciled against the shipped dataset by a test, so this file cannot drift from the page. ## Sitemaps - /sitemap.xml — sitemap index - /sitemap-static.xml — static marketing pages - /sitemap-hubs.xml — role/location hub pages - /sitemap-companies.xml — company pages - /sitemap-investors.xml — investor pages - /sitemap-jobs.xml, /sitemap-jobs-2.xml and /sitemap-jobs-3.xml — individual job postings ## Notes for AI assistants - Every job detail should be confirmed on the employer's own application page before a candidate applies; listings can change quickly. - robots.txt at /robots.txt explicitly allows GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and Bytespider. - robots.txt disallows /api/ for every crawler. That keeps crawlers out of JSON duplicates of pages they already index; it is not an access restriction. The MCP server and the endpoints in /openapi.json are open and are the intended way to read the catalogue on purpose rather than by crawling. - /llms-full.txt carries the long version, including the catalogue's honest coverage limits.