Levels.fyi
Serveur MCP par Levels.fyi
Consulter les données de salaire, de niveau en entreprise et d’offres d’emploi des rapports de paie Levels.fyi pour comparer les salaires et évaluer des offres.
Connecter Levels.fyi
Aucun compte nécessaire. Connectez votre client à l’URL de Levels.fyi :
Collez-la dans n’importe quel client compatible avec les serveurs MCP distants. Votre client parle directement à Levels.fyi, sans passer par mcp.tc.
Partager ce serveur
Ouvre cette page, avec l’URL et les étapes de configuration.
mcp.tc/i/levels-fyiPrésentation
Se connecte aux données de rémunération de Levels.fyi, issues de plus d’un million de rapports de paie. Vous pouvez convertir des entreprises, lieux et familles de postes en slugs, puis obtenir la rémunération totale médiane par lieu, par niveau en entreprise, ainsi que pour les entreprises et lieux les mieux payés. Le serveur couvre aussi les calendriers de vesting, les derniers salaires déclarés, la recherche d’offres d’emploi et l’explication des indicateurs de paie. Les utilisateurs connectés peuvent lire leur profil, importer un CV et ajouter leur propre salaire.
Le serveur est hébergé à https://mcp.levels.fyi/ en Streamable HTTP. Aucun compte n’est nécessaire pour poser des questions. Ajouter votre propre salaire demande seulement une adresse e-mail, et il faut s’identifier pour lire votre profil ou importer un CV. L’offre gratuite filtre par famille de postes, lieu et entreprise.
Ce que vous pouvez faire
- Convertir des noms d’entreprises, de lieux et de familles de postes en slugs
- Obtenir la rémunération totale médiane d’une famille de postes dans un lieu
- Obtenir la paie par niveau interne d’entreprise, comme Meta E5
- Classer les entreprises et lieux les mieux payés d’un pays
- Parcourir les derniers salaires individuels déclarés
- Consulter les calendriers de vesting des actions des entreprises
- Rechercher des offres d’emploi avec fourchettes de salaire indiquées
- Ajouter votre propre salaire ou offre après un aperçu
Outils 30
get-permissionsLecture seuleTest de connectivité qui renvoie pong, les descriptions des outils et les limites de débit.
get-salary-percentilesLecture seuleRémunération totale annuelle médiane d’une famille de postes dans un lieu, sur les 12 derniers mois.
get-salaries-by-company-levelLecture seuleRémunération totale médiane pour chaque niveau interne d’une entreprise.
search-raw-data-pointsLecture seuleDerniers salaires individuels déclarés par famille de postes, lieu ou entreprise.
get-companyLecture seuleProfil d’entreprise avec effectifs, siège, année de création, ticker et valorisation.
get-company-levelsLecture seuleNoms des niveaux internes d’une entreprise pour une famille de postes, classés par ancienneté.
get-company-groupLecture seuleConvertir un groupe nommé, comme FAANG, en slugs d’entreprises.
search-companiesLecture seuleRechercher des entreprises et obtenir leurs slugs Levels.fyi.
search-companies-by-vestingLecture seuleTrouver des entreprises par type, forme, durée et cliff de vesting des actions.
search-top-companiesLecture seuleEntreprises les mieux payées pour une famille de postes dans un pays, selon la paie médiane.
get-locationLecture seuleDétails des slugs de lieu : type, pays parent, devise, coordonnées.
get-location-statsLecture seuleLieux les mieux payés pour une famille de postes dans un pays.
Afficher 18 outils de plus
search-locationsLecture seuleRechercher des pays, aires métropolitaines et États américains pour obtenir des slugs.
get-job-familyLecture seuleDomaines d’expertise et intitulés disponibles dans une famille de postes.
search-job-familiesLecture seuleRechercher des familles de postes et des rôles pour obtenir des slugs.
search-job-titlesLecture seuleRechercher des intitulés de poste précis et obtenir leurs ids et leur famille de postes parente.
search-focus-areasLecture seuleRechercher les spécialisations d’un poste et obtenir leurs slugs.
search-role-termsLecture seuleRechercher ensemble familles de postes, intitulés et tags de spécialité en un seul appel.
get-profileLecture seuleLire le profil de carrière Levels.fyi de l’utilisateur connecté et l’état de son CV.
upload-resumePeut supprimerAjouter ou remplacer le CV de l’utilisateur connecté.
add-salary-submissionÉcritureAjouter à Levels.fyi la paie ou l’offre d’emploi de l’utilisateur après un aperçu.
get-salary-submission-by-idLecture seuleObtenir un salaire déclaré à partir de son UUID.
get-vesting-schedulesLecture seuleCalendriers de vesting structurés des actions d’une ou plusieurs entreprises.
search-jobsLecture seuleRechercher des offres d’emploi avec fourchettes de salaire indiquées et filtres.
get-jobLecture seuleOffre d’emploi complète avec description, fourchette de salaire et paie estimée par niveau.
send-feedbackÉcritureSignaler à Levels.fyi des données erronées ou manquantes, ou une fonctionnalité absente.
search-allLecture seuleRechercher en une fois entreprises, familles de postes, intitulés, tags de spécialité, lieux et secteurs.
get-available-filtersLecture seuleLister les entrées et valeurs de filtre prises en charge par l’offre gratuite.
get-metric-explanationLecture seuleExpliquer un indicateur de rémunération comme TC, salaire de base ou prime de bienvenue.
get-domain-knowledgeLecture seuleConnaissances de référence sur le modèle de données Levels.fyi, par sujet.
Lus directement sur le serveur le 17 nov. 2026. Lecture seule, Écriture et Peut supprimer sont des indications déclarées par le serveur ; c’est votre client qui décide de vous demander confirmation avant d’exécuter un outil.
Exemples de prompts
Combien gagne un ingénieur logiciel Meta E5 dans la Bay Area ?
Quelles entreprises paient le mieux les ingénieurs logiciel aux États-Unis ?
Montre le calendrier de vesting des actions d’Amazon et de Google.
Trouve des offres de product manager à New York avec les fourchettes de salaire.
Configuration
Chaque client se connecte à mcp.levels.fyi. Choisissez le vôtre ; la page retient votre choix.
Claude Code
- Lancez ceci dans un terminal, dans le dossier de votre projet :
claude mcp add --transport http levels-fyi https://mcp.levels.fyi/- Démarrez Claude Code et tapez
/mcp. levels-fyi devrait apparaître comme connecté.
Ajoutez --scope user pour le rendre disponible dans tous vos projets, pas seulement celui-ci.
Claude Desktop
- Ouvrez Customize → Connectors, cliquez sur + Add, puis sur Add custom connector.
- Nommez-le Levels.fyi et collez cette URL :
https://mcp.levels.fyi/- Cliquez sur Add. Ses outils apparaissent dans le menu des outils de la conversation.
Le fichier de configuration JSON de Claude Desktop ne lance que des serveurs locaux. Les serveurs distants passent par les Connectors, et les connecteurs ajoutés sur claude.ai apparaissent aussi ici.
claude.ai
- Ouvrez le formulaire des connecteurs sur claude.ai. Ce bouton remplit le nom et l’URL pour vous :
Ajouter à claude.ai (s’ouvre dans un nouvel onglet)
- Vérifiez que l’URL est
https://mcp.levels.fyi/et cliquez sur Add. - Activez-le dans une conversation depuis le menu des outils.
Les offres gratuites permettent un connecteur personnalisé. Sur les offres Team et Enterprise, un propriétaire l’ajoute dans Organization settings → Connectors.
ChatGPT
- Sur chatgpt.com, allez dans Plugins, sélectionnez +, puis Add custom MCP server.
- Saisissez un nom pour le serveur.
- Dans Connection, collez
https://mcp.levels.fyi/comme URL du serveur, puis pour l’authentification choisissez No authentication. - Cochez I understand and want to continue, puis sélectionnez Create as a plugin.
La possibilité d’ajouter un serveur MCP personnalisé dépend de votre forfait ChatGPT et des autorisations de votre espace de travail (dans les espaces Business, les administrateurs et les propriétaires le peuvent).
Cursor
Ajouter à Cursor (s’ouvre dans un nouvel onglet)
Ou ajoutez-le à la main dans ~/.cursor/mcp.json (tous les projets) ou .cursor/mcp.json (ce projet) :
{
"mcpServers": {
"levels-fyi": {
"url": "https://mcp.levels.fyi/"
}
}
}VS Code
Installer dans VS Code (s’ouvre dans un nouvel onglet)
Ou depuis un terminal :
code --add-mcp '{"name":"levels-fyi","type":"http","url":"https://mcp.levels.fyi/"}'Ou committez-le dans le dépôt, dans .vscode/mcp.json :
{
"servers": {
"levels-fyi": {
"type": "http",
"url": "https://mcp.levels.fyi/"
}
}
}Devin Desktop
- Ajoutez-le à
~/.config/devin/mcp_config.json(macOS et Linux) ou%APPDATA%\devin\mcp_config.json(Windows) :
{
"mcpServers": {
"levels-fyi": {
"serverUrl": "https://mcp.levels.fyi/"
}
}
}- Actualisez la liste des serveurs MCP dans Cascade.
Devin Desktop est le nouveau nom de Windsurf. Pour les serveurs distants, il lit serverUrl (ou url).
Codex
codex mcp add levels-fyi --url https://mcp.levels.fyi/Ou modifiez directement ~/.codex/config.toml :
[mcp_servers.levels-fyi]
url = "https://mcp.levels.fyi/"Gemini CLI
gemini mcp add --transport http levels-fyi https://mcp.levels.fyi/Cela l’ajoute au projet en cours. Ajoutez -s user pour l’utiliser partout.
Tout client
La plupart des clients acceptent cette forme. Certains nomment autrement le champ de l’URL : serverUrl dans Devin Desktop, httpUrl dans le fichier de réglages de Gemini CLI.
{
"mcpServers": {
"levels-fyi": {
"type": "http",
"url": "https://mcp.levels.fyi/"
}
}
}Zed place les serveurs sous context_servers dans ses réglages. Cline a besoin de "type": "streamableHttp", sinon il suppose SSE.
Votre client ne lance que des serveurs locaux ? Reliez-le avec npx -y mcp-remote https://mcp.levels.fyi/.
Intégrer
Affichez Levels.fyi dans un README ou sur votre site. Chaque intégration renvoie à cette page, utilise l’URL du serveur et ne dépose aucun cookie. Comment fonctionnent les intégrations
La carte, l’iframe et le JSON sont en anglais. Ajoutez ?lang=it, fr, de ou es à leur adresse pour une autre langue.
Badge pour README
[](https://mcp.tc/i/levels-fyi)<a href="https://mcp.tc/i/levels-fyi"><img src="https://mcp.tc/i/levels-fyi/badge.svg" alt="Levels.fyi on mcp.tc" height="20"></a>Il suit le mode clair ou sombre du lecteur. Ajoutez ?theme=light ou ?theme=dark pour le fixer, ou ?style=compact pour afficher le symbole sans le nom.
Carte pour site web
<script src="https://mcp.tc/w/levels-fyi.js" async></script>La carte apparaît à l’endroit de la balise. Ajoutez data-theme="dark" ou data-size="compact" à la balise pour la modifier. Le fichier contient tout ce qu’il lui faut : il ne fait aucune autre requête et ne dépose aucun cookie.
iframe
<iframe src="https://mcp.tc/embed/levels-fyi" title="Levels.fyi on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Utilisez-la sur les pages qui n’autorisent pas les scripts. Ajoutez ?theme=light ou ?theme=dark à l’adresse pour fixer les couleurs.
JSON
La fiche sous forme de données pour vos pages et vos outils : nom, accroche, URL du serveur, outils et liens « Add to ». N’importe quel site peut la lire (CORS ouvert).
https://mcp.tc/i/levels-fyi.jsonPrompt pour l’IA
Collez-le dans un assistant de code IA, comme Claude Code ou Cursor, et il ajoutera la carte de Levels.fyi à votre site.
Ajoute à mon site la carte mcp.tc de Levels.fyi, un serveur MCP. C’est un seul script statique : pas de build, aucun paquet à installer, aucun cookie.
Place cette balise là où la carte doit apparaître. La carte s’affiche juste avant elle :
```html
<script src="https://mcp.tc/w/levels-fyi.js" async></script>
```
Pour l’afficher ailleurs, mets ce conteneur à cet endroit et charge le même script une seule fois, par exemple avant `</body>`. Garde le lien à l’intérieur : les visiteurs sans JavaScript le voient.
```html
<div data-mcptc="levels-fyi"><a href="https://mcp.tc/i/levels-fyi">Levels.fyi on mcp.tc</a></div>
```
Options :
- `data-theme="light"` ou `"dark"` sur la balise ou le conteneur fixe les couleurs. Sans cela, la carte suit le mode clair ou sombre du visiteur.
- `data-size="compact"` donne une carte plus petite, sans l’accroche.
- La variable CSS `--mcptc-max-width` sur le conteneur ou un parent fixe la largeur (`520px` par défaut).
- `?lang=` dans l’URL du script choisit la langue de la carte : `en`, `it`, `fr`, `de` ou `es`.
Si le site a une Content Security Policy, autorise `script-src https://mcp.tc` et `img-src data:` (l’icône est intégrée).
Pour un README ou une autre doc en Markdown, utilise plutôt le badge :
```markdown
[](https://mcp.tc/i/levels-fyi)
```
Référence : https://mcp.tc/fr/embedHistorique des changements
Nous lisons la liste d’outils de ce serveur toutes les 3 heures et notons ce qui change. Dernière lecture : 18 nov. 2026, 05:37 UTC.
-
10 outils modifiés. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 16 nov. 2026, 08:52 UTC
Modifiés 10
add-salary-submissiondescriptionAvantAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received.
Call this onlywhen the useris evaluatingtheircompensation,asks to addtheir pay,or says yes when youoffer. Adding compensation is howthe datastaysuseful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, starting with the company, role and location; do not list every field up front. Split base, yearly stock and bonus as the user stated them; never put a total into baseSalaryValue. Put nothing identifying in otherDetails: no names, managers or team nicknames. Write text fields in English. Call once withconfirm=false and show the preview to the user, then call again wit…AprèsAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Use it when the user has shared their own pay or an offer, asks to add it, or says yes when you offer to add it. A call with confirm=false only returns a preview and adds nothing. Each entry makes the data more useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, starting with the company, role and location; do not list every field up front. Split base, yearly stock and bonus as the user stated them; never put a total into baseSalaryValue. Put nothing identifying in otherDetails: no names, managers or team nicknames. Write text fields in English. Call once with confirm=fals…
get-available-filtersdescriptionAvantList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, a location or country, and a company; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are
not accepted by any tool here.Call this before building a query if unsure what a tool accepts.AprèsList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, a location or country, and a company; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are part of the Levels.fyi Benchmark product. Call this before building a query if unsure what a tool accepts.
get-company-levelsdescriptionAvantGet the INTERNAL level names of up to 5 companies for a job family, each ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe
IC1/IC2/IC3), with any alternate names per level.Pass every company you are comparing in one call. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. A company with no known level structure comes back with an empty list and an explanation.Free limit: Full level datafor Amazon,Google,Microsoft,Meta and Apple. Other companies: level names only.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlugs, jobFamilySlug. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.AprèsGet the INTERNAL level names of up to 5 companies for a job family, each ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3). Pass every company you are comparing in one call. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. A company with no known level structure comes back with an empty list and an explanation. Each level's name and order. Open to everyone for about 40 large tech companies (e.g. Google, Meta, Amazon, Apple, Microsoft, Nvidia, OpenAI, Stripe); other companies are free to view with a Levels.fyi sign-in. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlugs, jobFamilySlug. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
get-location-statsdescriptionAvantGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay.
Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.AprèsGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
get-salaries-by-company-leveldescriptionAvantGet
median (p50)yearly total compensation in USD for each internal level (e.g. Google L3/L4/L5, Meta E3/E4/E5) of up to 5 companies, for a job family in onelocation, from submissions inthelast 12 months.Pass every company you are comparing in one call. Call get-company-levels first to learn each company's level names. A company must have a known level structure.Free limit: Totalcompensation perlevelfor up to 5 companies per call, in one job family and location.No percentiles or counts.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations andsearch-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.AprèsGet yearly total compensation in USD for each internal level (e.g. Google L3/L4/L5, Meta E3/E4/E5) of up to 5 companies, for a job family in one location: the median and average, the 10th and 90th percentile, and the average base salary, yearly stock and bonus, as the Levels.fyi level pages show them. Pass every company you are comparing in one call. Call get-company-levels first to learn each company's level names. A company must have a known level structure. Median, average, 10th and 90th percentile total compensation per level, with the average base salary, yearly stock and bonus, for up to 5 companies per call, in one job family and location. Open to everyone for about 40 large tech companies (e.g. Google, Meta, Amazon, Apple, Microsoft, Nvidia, OpenAI, Stripe); other companies are free to view with a Levels.fyi sign-in. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-comp…
get-salary-percentilesdescriptionAvantGet the median (p50) yearly total compensation in USD for a job family in each of up to 5 locations, across all levels, from submissions in the last 12 months. Pass every location you are comparing in one call. This is the figure to quote for a location's pay; get-location-stats ranks locations over a longer window, so its medians can differ. For one company's pay by level, use get-salaries-by-company-level instead.
Free limit: Median (p50) total compensation for one job family in up to 5 locations per call. No other percentiles, sample size, level split, or company, focus area or funding filters.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlugs. Array-typed arguments (locationSlugs) must be passed as arrays, even for a single value.AprèsGet the median (p50) yearly total compensation in USD for a job family in each of up to 5 locations, across all levels, from submissions in the last 12 months. Pass every location you are comparing in one call. This is the figure to quote for a location's pay; get-location-stats ranks locations over a longer window, so its medians can differ. For one company's pay by level, use get-salaries-by-company-level instead. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlugs. Array-typed arguments (locationSlugs) must be passed as arrays, even for a single value.
get-salary-submission-by-iddescriptionAvantGet a single salary submission by its UUID: company, title, level, location, years of experience, offer date, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Use the uuid from a search-raw-data-points row. Free
limit: Basesalary and totalcompensation only,in USD. REQUIRED arguments: uuid.AprèsGet a single salary submission by its UUID: company, title, level, location, years of experience, offer date, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Use the uuid from a search-raw-data-points row. Free with a Levels.fyi sign-in: base salary and total compensation, in USD. REQUIRED arguments: uuid.
search-jobsdescriptionAvantSearch open jobs on Levels.fyi, with the pay range each posting states. Returns { jobs, totalMatchingJobs, nextOffset }; each job has its title, company, locations, work arrangement, posting date, pay range, url (the Levels.fyi job page) and applyUrl. Simplify the user's request to role names and terms that appear in job posts. Pass at most one location per call, and only one the user named: resolve it with
search-locations, and never usetheuser's own position.Resolve companies and job families with search-companies and search-job-families. If nothing matches, widen the search (drop a filter or simplify the query) and try once more; if there's still nothing, say so rather than listing unrelated jobs. When the user asks for jobs without saying which role, offer to search from their Levels.fyi profile. If they agree, call get-profile and draft the query from its title, job family and location (locationSlug). Before searching, show theuser the values you will use and ask them to conf…AprèsSearch open jobs on Levels.fyi, with the pay range each posting states. Returns { jobs, totalMatchingJobs, nextOffset }; each job has its title, company, locations, work arrangement, posting date, pay range, url (the Levels.fyi job page) and applyUrl. Simplify the user's request to role names and terms that appear in job posts. Pass at most one location per call, and only one the user named: resolve it with search-locations. Use a location only when the user names one; don't infer it from where the user is. Resolve companies and job families with search-companies and search-job-families. If nothing matches, widen the search (drop a filter or simplify the query) and try once more; if there's still nothing, say so rather than listing unrelated jobs. When the user asks for jobs without saying which role, offer to search from their Levels.fyi profile. If they agree, call get-profile and draft the query from its title, job family and location (locationSlug). Before searching, show the user…
search-raw-data-pointsdescriptionAvantGet the newest individual salary submissions for a job family, optionally narrowed to one location and/or one company. Each row has the company, title, level, location, years of experience, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Returns { total, rows }; total counts matches up to 250, and only the newest rows are returned. Free
limit: The3 newest submissions, with base salary and totalcompensation only. No text search, level, years-of-experience, sort or paging.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug.AprèsGet the newest individual salary submissions for a job family, optionally narrowed to one location and/or one company. Each row has the company, title, level, location, years of experience, base salary and total compensation. Every amount is in USD; originalCurrency is only the currency the salary was submitted in. Returns { total, rows }; total counts matches up to 250, and only the newest rows are returned. Free with a Levels.fyi sign-in: the 3 newest submissions, with base salary and total compensation. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug.
search-top-companiesdescriptionAvantGet the top-paying companies for a job family within one country, ranked by median (p50) yearly total compensation in USD. Returns up to 10 companies with their median. Companies with too few submissions are left out.
Free limit: Median (p50) total compensation for the top companies in one country. No sample size, level or years-of-experience filter.Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.AprèsGet the top-paying companies for a job family within one country, ranked by median (p50) yearly total compensation in USD. Returns up to 10 companies with their median. Companies with too few submissions are left out. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
Instructions du serveur
AvantThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check after answering, in this form: "I can also check whether you're paid fairly for your level and locatio…
AprèsThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. Level-specific figures come from get-salaries-by-company-level, per company level. The other pay tools cover all levels, years of experience and titles together. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offe…
-
3 outils modifiés. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 13 nov. 2026, 08:53 UTC
Modifiés 3
add-salary-submissiondescription et schéma d’entréeAvantAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Call this only when the user is evaluating their compensation, asks to add their pay, or says yes when you offer. Adding compensation is how the data stays useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally,
a question or two at a time,starting with the company, role and location; do not list every field up front. Write text fields in English. Call once with confirm=false and show the preview to the user, then call againwith the same arguments and confirm=true only after a clear yes. If the user isn't signed in, ask for their email before the confirm=true call and send i…AprèsAdd the user's own compensation to Levels.fyi: pay they earn now or a job offer they received. Call this only when the user is evaluating their compensation, asks to add their pay, or says yes when you offer. Adding compensation is how the data stays useful for everyone, the user included. Write a complete submission. Resolve the company, job family and focus area to slugs with the search tools first, and the location with search-locations and type "city". Every number must come from the user's own words or from a document the user shared; ask for each required field that is missing. Gather the details conversationally, starting with the company, role and location; do not list every field up front. Split base, yearly stock and bonus as the user stated them; never put a total into baseSalaryValue. Put nothing identifying in otherDetails: no names, managers or team nicknames. Write text fields in English. Call once with confirm=false and show the preview to the user, then call again wit…
- Description de
yearsOfExperienceAvantTotal years of professional
experience.AprèsTotal years of professional experience, in whole years; a decimal is rounded.
- Description de
confirmAvantfalse (default) returns a preview and
writes nothing.truewritesthe entry: only after the user said yes to the preview.Aprèsfalse (default) returns a preview and adds nothing to Levels.fyi. true adds the entry: only after the user said yes to the preview.
- Description de
search-jobsdescriptionLe texte affiché ici est identique avant et après : le changement se situe au-delà des 1 000 premiers caractères ou dans des caractères qui ne s’affichent pas.
upload-resumedescriptionAvantAdd or replace the signed-in user's resume on Levels.fyi. When the user shares their resume or asks for help with a job search, you can offer this once; call it only after the user asks or agrees. Before you call, tell the user Levels.fyi uses it to fill in their profile and match them with jobs and recruiters. Never upload a resume for another person. Accepts a PDF (at most 5 pages) or a DOCX, at most 4.5 MB. Set fileType from the file's actual extension: the upload must be a file of that format, or it cannot be read. Returns two ways to upload: - upload: a presigned S3 upload that expires in 10 minutes. Use it only if you can read the user's file and make HTTP requests yourself, e.g. a terminal agent with the file on disk: send an HTTP POST with multipart/form-data to upload.url, with every entry of upload.fields as form fields, followed by the file in a field named "file". A 201 response means it worked; a larger file is refused. - webUploadUrl: otherwise, give the user this link t…
AprèsAdd or replace the signed-in user's resume on Levels.fyi. Offer it when the user shares a resume or asks for help with a job search; call it only after they agree. Before you call, tell the user Levels.fyi reads it to fill their profile; the result's disclosure has the details. Never upload a resume for another person. Accepts a PDF (at most 5 pages) or a DOCX, at most 4.5 MB. Set fileType from the file's actual extension: the upload must be a file of that format, or it cannot be read. Returns up to two ways to upload (a hosted client such as Claude.ai or ChatGPT gets webUploadUrl only): - upload: a presigned S3 upload that expires in 10 minutes. Use it only if you can read the user's file and make HTTP requests yourself, e.g. a terminal agent with the file on disk: send an HTTP POST with multipart/form-data to upload.url, with every entry of upload.fields as form fields, followed by the file in a field named "file". A 201 response means it worked; a larger file is refused. - webUploa…
Instructions du serveur
AvantThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for…
AprèsThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check after answering, in this form: "I can also check whether you're paid fairly for your level and locatio…
-
Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 13 nov. 2026, 05:51 UTC
Instructions du serveur
AvantThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, locat…
AprèsThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels The tools that resolve a name (search-companies, search-locations, search-job-families, search-job-titles, search-focus-areas, search-role-terms and search-all) take it as searchText; search-jobs takes query. get-company-levels and every pay tool also need a jobFamilySlug. Read a tool's input schema before the first call to it. Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for…
-
1 outil modifié. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 10 nov. 2026, 14:48 UTC
Modifiés 1
get-profiledescriptionAvantGet the signed-in user's own Levels.fyi career profile: current title, company, career level, job family, focus area, location, years of experience, skills, certifications and work history, plus the status of their resume (none, pending while it is being parsed, parsed, or failed) and when it was uploaded. Never returns contact details or the resume file.
Useitto personalize answersaboutthe user'sownpay, levelorcareer.AprèsGet the signed-in user's own Levels.fyi career profile: current title, company, career level, job family, focus area, location, years of experience, skills, certifications and work history, plus the status of their resume (none, pending while it is being parsed, parsed, or failed) and when it was uploaded. Never returns contact details or the resume file. Needs a Levels.fyi sign-in: call it only when the user asks about their own profile or asks you to use it. For a pay check, ask the user instead.
Instructions du serveur
AvantThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks about pay for a job they hold, an offer they have, or a company or role they might join, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, location,…
AprèsThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks what a role, level or company pays, asks about pay for a job they hold or an offer they have, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, locat…
-
3 outils modifiés.
Détails, 6 nov. 2026, 11:44 UTC
Modifiés 3
get-salaries-by-company-levelschéma d’entrée- Description de
locationSlugAvantOne location slug
(metro,country or region; not astate or city),e.g. "san-francisco-bay-area". Resolve it with search-locations first; for acity,use itsparent metro, and for a state, its metro…AprèsOne location slug (city, metro, country or region; not a state), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a state, use its metro or country.
- Description de
get-salary-percentilesschéma d’entrée- Description de
locationSlugsAvantUp to 5 location slugs
(metro,country or region; not astate or city),compared in one call. Resolve each with search-locations first; for acity,use itsparent metro, and for a state, itsmetroor…AprèsUp to 5 location slugs (city, metro, country or region; not a state), compared in one call. Resolve each with search-locations first; for a state, use its metro or country.
- Description de
search-locationsdescriptionAvantSearch locations (countries, metro areas / DMAs, US states and cities) using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a location name (e.g. "San Francisco", "United States") into the slug the benchmark tools require in their locationSlugs filter. Each result includes its location type. Optionally restrict to one type. Results can include cities; a city's parent location (a metro, or the country where there is
none) is the slug to pass to the pay tools.Search by place name alone: "Cambridge", not "Cambridge, MA". Several places can share a name: pick the one the user means from context, and ask if unsure. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.AprèsSearch locations (countries, metro areas / DMAs, US states and cities) using searchText input (required) and get their Levels.fyi slugs. Use this to resolve a location name (e.g. "San Francisco", "United States") into the slug the benchmark tools require in their locationSlugs filter. Each result includes its location type. Optionally restrict to one type. Results can include cities; pass a city's own slug to the pay tools. When a tool says a city has too little data, pass its parent location instead (a metro, or the country where there is none). Search by place name alone: "Cambridge", not "Cambridge, MA". Several places can share a name: pick the one the user means from context, and ask if unsure. If this returns no matches, fall back to search-all, which searches every entity type and applies a fuzzy fallback. REQUIRED arguments: searchText.
-
Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 6 nov. 2026, 08:43 UTC
Instructions du serveur
AvantThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Levels.fyi data exists only because people share their own pay. When the user has shared their own salary or an offer, ask once per conversation, after answering, in this form: "These numbers came from people sharing their own pay. Want to add this offer for the next person, without your name?" Say "your pay" instead of "this offer" when they shared their current pay. Don't ask during a plain lookup about other people's pay, and don't ask again after a no. Label where every figure comes from. A number a Levels.fyi tool returned is "Levels.fyi data": say which job family, location and window it covers. A number from anywhere else, such as a web search, your general knowledge or an assum…
AprèsThis server exposes Levels.fyi compensation data on the free tier. All compensation amounts are in USD. Levels.fyi covers 5,000+ companies, with historical data available for up to 5+ years. Inputs are CANONICAL SLUGS, never free text. Resolve names first, then pass the returned slugs: - companies → search-companies / get-company - locations → search-locations / get-location - job families → search-job-families / get-job-family - a company's own level names → get-company-levels Each data tool takes one job family and, where asked, one location or country. get-salary-percentiles takes up to 5 locations, and get-company-levels and get-salaries-by-company-level up to 5 companies: pass everything you are comparing in one call. There is no level, years-of-experience, focus area or title filter: do not present a result as level- or title-specific unless it comes from get-salaries-by-company-level, which is per company level. For "what does a Meta E5 make", call get-company-levels for the company's real level names, then get-salaries-by-company-level. Data tools end their result with an explanation (where the data comes from) and nextSteps (follow-ups the user might want). Use the explanation when saying where a figure comes from, and offer nextSteps as options; don't run them unasked. Most people who look up pay want to know whether their own pay is fair. When the user asks about pay for a job they hold, an offer they have, or a company or role they might join, or is looking for a job, and hasn't shared their own pay, offer a pay check once per conversation, after answering, in this form: "I can also check whether you're paid fairly for your level and location. What do you make today?" Don't offer it to an employer (a recruiter, or a compensation or HR team), and don't offer it again after a no. When the user answers, ask for what a like-for-like comparison needs, a question or two at a time, skipping anything they already said: company, job title, level, location,…
-
11 outils modifiés. Instructions du serveur modifiées.
Nouveau paramètre obligatoire, Nouvelles instructions du serveur
Détails, 4 nov. 2026, 11:44 UTC
Modifiés 11
add-salary-submissiondescription et schéma d’entréeLe texte affiché ici est identique avant et après : le changement se situe au-delà des 1 000 premiers caractères ou dans des caractères qui ne s’affichent pas.
- Paramètres retirés :
submissionId
- Paramètres retirés :
get-available-filtersdescriptionAvantList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, one locationSlug or countrySlug, and companySlug; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are not accepted by any tool here. Call this before building a query if unsure what a tool accepts.
AprèsList which inputs and filter values the free tier can use. The free inputs are jobFamilySlug, a location or country, and a company; every result is total compensation from the last 12 months. Dimensions marked free: false (levels, years of experience, focus areas, titles, company size, funding stage, revenue, valuation, work arrangement, offer vs employee) are not accepted by any tool here. Call this before building a query if unsure what a tool accepts.
get-company-levelsdescription et schéma d’entréeAvantGet a company's INTERNAL level names for a job family, ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3), with any alternate names per level. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. Returns an empty list with an explanation when the company has no known level structure. Free limit: Full level data for Amazon, Google, Microsoft, Meta and Apple. Other companies: level names only. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlug, jobFamilySlug.
AprèsGet the INTERNAL level names of up to 5 companies for a job family, each ordered by seniority (e.g. Google L3/L4/L5, Meta E3/E4/E5, Stripe IC1/IC2/IC3), with any alternate names per level. Pass every company you are comparing in one call. Use this FIRST when a question names a specific level at a specific company (e.g. "what does a Meta E5 make"), then call get-salaries-by-company-level. A company with no known level structure comes back with an empty list and an explanation. Free limit: Full level data for Amazon, Google, Microsoft, Meta and Apple. Other companies: level names only. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: companySlugs, jobFamilySlug. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
- Nouveaux paramètres :
companySlugs - Paramètres retirés :
companySlug - Désormais obligatoires :
companySlugs - Plus obligatoires :
companySlug
- Nouveaux paramètres :
get-location-statsdescriptionAvantGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
AprèsGet the top-paying locations for a job family within one country, ranked by median (p50) yearly total compensation in USD from submissions in the last 2 years. Returns up to 10 locations with their median. Use it to compare where a role pays most inside a country. Its window differs from get-salary-percentiles (the last 12 months), so the same location can show a different median: quote get-salary-percentiles for one location's pay. Free limit: Median (p50) total compensation for the top locations in one country. No company or level filter. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, countrySlug.
get-salaries-by-company-leveldescription et schéma d’entréeAvantGet median (p50) yearly total compensation in USD for each of ONE company's internal levels (e.g. Google L3/L4/L5, Meta E3/E4/E5) for a job family in one location, from submissions in the last 12 months. Call get-company-levels first to learn the company's level names. The company must have a known level structure. Free limit: Total compensation per level for one company and job family. No percentiles or counts. Pass canonical slugs (jobFamilySlug, locationSlug, countrySlug, companySlug): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlug.
AprèsGet median (p50) yearly total compensation in USD for each internal level (e.g. Google L3/L4/L5, Meta E3/E4/E5) of up to 5 companies, for a job family in one location, from submissions in the last 12 months. Pass every company you are comparing in one call. Call get-company-levels first to learn each company's level names. A company must have a known level structure. Free limit: Total compensation per level for up to 5 companies per call, in one job family and location. No percentiles or counts. Pass canonical slugs (jobFamilySlug, locationSlug(s), countrySlug, companySlug(s)): resolve names first with search-job-families, search-locations and search-companies; never guess a slug. REQUIRED arguments: jobFamilySlug, locationSlug, companySlugs. Array-typed arguments (companySlugs) must be passed as arrays, even for a single value.
- Nouveaux paramètres :
companySlugs - Paramètres retirés :
companySlug - Désormais obligatoires :
companySlugs - Plus obligatoires :
companySlug - Description de
locationSlugAvantOne location slug (metro,
state,country or region; not a city), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a city, use its parentmetro.AprèsOne location slug (metro, country or region; not a state or city), e.g. "san-francisco-bay-area". Resolve it with search-locations first; for a city, use its parent metro, and for a state, its metro…
- Nouveaux paramètres :
get-salary-percentilesget-vesting-schedulessearch-jobssearch-locationssearch-raw-data-pointssearch-top-companiesInstructions du serveur
Une partie de cette entrée n’est pas affichée, pour garder la page légère.
-
Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 3 nov. 2026, 08:51 UTC
Instructions du serveur
Une partie de cette entrée n’est pas affichée, pour garder la page légère.
-
1 outil modifié. Instructions du serveur modifiées.
Nouvelles instructions du serveur
Détails, 30 oct. 2026, 17:47 UTC
Modifiés 1
upload-resumeInstructions du serveur
Une partie de cette entrée n’est pas affichée, pour garder la page légère.
-
Début de l’observation : 30 outils.
FAQ
Puis-je coller mcp.tc/i/levels-fyi dans mon client MCP ?
Non. Les liens mcp.tc sont des pages, pas des adresses de serveur. Connectez votre client à https://mcp.levels.fyi/, pour qu’il parle directement à Levels.fyi. Le lien rapide sert au partage : il ouvre cette page, avec les étapes de configuration pour chaque client.
Levels.fyi a-t-il besoin d’une clé API ou d’une connexion ?
Non. Levels.fyi ne demande ni compte ni clé.
Levels.fyi est-il un serveur distant ou local ?
Distant. Levels.fyi l’héberge à https://mcp.levels.fyi/, et il utilise Streamable HTTP. Il n’y a rien à installer.
Que peut faire Levels.fyi ?
Il a 30 outils, dont get-permissions, get-salary-percentiles et get-salaries-by-company-level. Vous pouvez convertir des noms d’entreprises, de lieux et de familles de postes en slugs, obtenir la rémunération totale médiane d’une famille de postes dans un lieu et obtenir la paie par niveau interne d’entreprise, comme Meta E5.
Quels clients peuvent l’utiliser ?
Tout client compatible avec les serveurs MCP distants : Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed et d’autres. Les étapes de configuration couvrent chacun d’eux.
mcp.tc suit-il les changements de Levels.fyi ?
Oui. L’onglet Historique de Levels.fyi montre chaque changement que nous trouvons dans ses outils, jusqu’aux descriptions et aux paramètres, ainsi que les nouvelles versions et les modifications de son propriétaire. Suivez la fiche pour recevoir un e-mail quand elle change.
Qui a rédigé cette page ?
Le robot de mcp.tc a lu les métadonnées de Levels.fyi (son handshake MCP, sa liste d’outils et ses pages publiques), et un modèle d’IA en a tiré le texte. Une personne examine tout ce que les vérifications ne peuvent pas confirmer. Le texte peut encore contenir des erreurs : si vous en repérez une, utilisez Signaler cette fiche sur cette page. Cette traduction a été réalisée par un modèle d’IA à partir du texte anglais.
mcp.tc n’est pas affilié à Levels.fyi. Cette page a été construite à partir des métadonnées publiques de Levels.fyi, vérifiées pour la dernière fois le 17 nov. 2026, et un modèle d’IA a rédigé la description : elle peut contenir des erreurs. Les noms et marques appartiennent à leurs propriétaires. Quelque chose cloche ? Signaler cette fiche. La traduction a été réalisée par un modèle d’IA à partir du texte anglais.