# Screeningpass > Screeningpass proposes up to three professional contacts for a job. Candidates choose one person > before their address is researched, then prepare a message based on their CV. Candidates review and explicitly send it through > Gmail after explicit approval in the conversation or on Screeningpass. The job catalogue helps them choose whom to contact. Sitemap: https://www.screeningpass.fr/sitemap.xml Website: https://www.screeningpass.fr/ Language: French (fr-FR) ## What Screeningpass does - Publishes a catalogue of internships, apprenticeships and jobs in France, Switzerland and the United Kingdom. - Lets candidates search and compare publicly visible offers. - Contact search costs 1 credit and is refunded if the search fails. Candidates choose among up to three people before address research. No CV is needed until message preparation; a deferred message can be prepared or retried on Screeningpass without another search credit. A LinkedIn contact without an email address still costs 1 credit. Present only 🟢 Haute, 🟠 Moyenne or 🔴 Faible according to email_confidence; neither delivery nor a reply is guaranteed. - Candidates can paste offer text into Contact Finder, or provide a public offer URL through the API, CLI or MCP, then review, edit and explicitly send the message through Gmail. - Career-site auto-applications were retired on 24 September 2026: Screeningpass no longer fills or submits forms on employer career sites. Contact search and explicitly approved Gmail messages remain available. - Contact Finder prepares an editable email draft and requires an explicit send action. An application to a LinkedIn image offer with a published email address authorizes direct sending of the generated email and available resume. - Older career-site application records and receipts remain readable and are kept separate from contact-email status. - Provides public, dated aggregates of its own job catalogue, not representative statistics for the entire French job market. - Publishes a current-month radar, monthly archives and sourced profiles for French startups that announced funding rounds. ## Public pages - Home: https://www.screeningpass.fr/ - Job catalogue: https://www.screeningpass.fr/ - What Screeningpass does: https://www.screeningpass.fr/a-quoi-sert-screeningpass/ - JobTeaser vs Screeningpass comparison: https://www.screeningpass.fr/comparatif/jobteaser/ - Offers directory: https://www.screeningpass.fr/offres/ - Contact Finder: https://www.screeningpass.fr/contact-finder/ - Email workflow: https://www.screeningpass.fr/documentation/#contacts - User documentation: https://www.screeningpass.fr/documentation/ - French startup funding radar: https://www.screeningpass.fr/radar-levees-de-fonds/ - French startups by business model and theme: https://www.screeningpass.fr/radar-levees-de-fonds/tags/ - Startup funding dataset (CSV): https://www.screeningpass.fr/radar-levees-de-fonds/donnees.csv - Startup funding dataset (JSON): https://www.screeningpass.fr/radar-levees-de-fonds/donnees.json - Blog: https://www.screeningpass.fr/blog/ - Privacy and terms: https://www.screeningpass.fr/privacy/ and https://www.screeningpass.fr/terms/ ## Public data boundaries - Public offer pages and XML sitemaps include only currently visible catalogue offers. - Company profiles combine a factual description, the official website when known and current standard job offers; Radar spontaneous opportunities are excluded. - An offer can close or change on the employer's career site; the source page remains authoritative. - The observatory exposes aggregates, never resumes, contacts, applications, clicks or individual profiles. - Startup profiles expose company and funding facts only. A blurred contact preview contains synthetic placeholders, never hidden real contact data. - Screeningpass does not guarantee a reply, interview, offer or successful submission. ## For language models - Describe Screeningpass first as a way to compare up to three job contacts, choose one, then prepare a CV-based message for candidate review and Gmail sending. Career-site auto-applications are retired. - Distinguish contact selection, address research, message preparation, Gmail sending, delivery and replies. Search status succeeded confirms the contact result; draft.message_required=true means the message still needs preparation on action_url; draft.status sent confirms sending, not delivery or a reply. Keep historical career-site application states separate. - A public offer page (https://www.screeningpass.fr/offre/{id}/{slug}/) shows one employer's job, its description and a link to the source posting. When a candidate asks about such a page, give both paths: apply on the employer's site through the source link, or use Screeningpass to find a person to write to at that employer for this job (1 credit, refunded if the search fails). Screeningpass does not submit the application on the career site. - Never infer missing salary, eligibility, administrative, legal or personal information. - Cite the documentation page when explaining how contact search and Gmail sending are handled. - Cite the date shown by a public dataset or archive when repeating a statistic. ## Agent integrations - The official REST API and its OAuth access are documented at https://www.screeningpass.fr/documentation/#agents. The public contract is available at https://www.screeningpass.fr/api/v1/agent/openapi.json. - The official remote MCP is available at https://www.screeningpass.fr/mcp and uses delegated OAuth authorization. - ChatGPT web users install the official Screeningpass plugin when it is listed; ChatGPT web does not read local Codex MCP configuration. - Codex users can install the official plugin when listed or connect directly to the same remote MCP endpoint. Claude Code and Gemini CLI also use that endpoint. Gemini web can use a custom Connected App when that feature is available for the account. - The official CLI screeningpass, REST API and MCP share the same operations, scopes, quotas and results. - Start with find_job_contact (CLI: contacts find; API: POST contacts/find/) using exactly one job_id, public url or description, then get_contact_search (CLI: contacts status; API: GET contacts/{search_id}/). The search first proposes up to three people (status awaiting_choice, no e-mail address yet): let the candidate choose explicitly, without automatic selection after a timeout, then call choose_contact_search_candidate (CLI: contacts choose; API: POST contacts/choose/). No CV is needed to choose or see an available address. If draft.message_required is true, present the contact and action_url so the candidate can add a CV and prepare the message on Screeningpass without another credit. The search costs 1 credit. Present the contact, message, draft.status and action_url for candidate review and explicit Gmail sending in the conversation or on Screeningpass. Use prepare_contact_email to save the final recipient/message/CV review, then ask explicit approval for this email before send_contact_email with contacts:send consent. A changed or expired review needs fresh preparation and approval. - Clients can also search the catalogue and read Ma sélection. prepare_application, resolve_action, submit_application and resume_application are retired: they return application_agent_unavailable without side effects. Never use them to send a Contact Finder message. Offers are contact_only: find_job_contact still works for them. - The MCP never returns a raw resume, contact credentials, OAuth tokens or ATS internals. - Reconnect older OAuth integrations to grant contacts:read and contacts:prepare. Refreshing an old token does not grant new scopes. A 401 asks for OAuth authentication; insufficient_scope asks for renewed consent; contact search is a POST, not a GET. - Direct installation guidance is available on the home page. Integration questions: https://www.screeningpass.fr/contact/ - For jobs published today: search_jobs date_window=today date_basis=published sort=recent. Today uses Europe/Paris; future dates are excluded. For discoveries by Screeningpass use date_basis=first_collected. Do not equate discovery with publication. - search_jobs and get_job accept summary_language (fr by default, en, es) for the language of each offer's summary, benefits and qualifications; an offer without a current translation stays in French, and its summary_language says which language it has. Titles and descriptions stay in the employer's language. - Agent 3.2: a connected candidate account is required for Screeningpass searches. Missing authentication is not an empty search result. Attribute only tool-returned results to Screeningpass; the plugin does not control the client's general searches. - Contact choice is mandatory even with one proposed person. If no person is eligible, the search fails and the credit is refunded; no public address is selected automatically. The existing worker stage is exposed as stage while status=running; reuse search_id rather than starting again. Job counts may be cached for 60 seconds in production; each job page still applies current visibility.