Online Resume Parser vs Resumly Developer API

Online Resume Parser is an API platform from HireLayer that turns CVs and job descriptions into structured JSON for candidate matching and ranking. Its five APIs handle CV extraction, job-criteria extraction, skills matching, candidate matching, and candidate ranking. Resume results can include contact details, experience, education, languages, skills, certifications, and interests. It accepts document, spreadsheet, presentation, text, and image files, with requests sent over HTTPS using an X-API-Key and an optional webhook callback. It is aimed at ATS and HR platforms, job boards, sourcing tools, staffing and recruitment agencies, and RPO providers. The site says files and extracted photos are stored in Paris, with AI processing in the EU; callers can set do_not_store_data to true, though it defaults to false. Free access includes 50 credits per month; Starter costs €24 a month, and Scale costs €89 a month. One-time credit packs are also available, starting at €29, paid once. Encoded requests must be under 6 MiB, and documents above 100,000 extracted characters return HTTP 422.

Resumly Developer API gives applications and AI agents access to resume, job-search, application, and interview-preparation operations. Its public API has 45+ endpoints, and a Python SDK is available through pip install resumly. Resume tools parse PDF and DOCX files, create tailored resumes and cover letters, rewrite resumes, translate documents into 40+ languages, and export PDF or DOCX. Job functions include saved searches, matched-job reads, and search refreshes; application tools cover server-side submission, tracking, and autopilot controls. The API also supports company research, interview-question generation, and feedback and scoring on answers. Listed integrations include LangChain, CrewAI, AutoGen, OpenClaw, the OpenAI Agents SDK, and MCP. Header-capable clients including Cursor, Claude Code, and VS Code can connect to the hosted MCP server; hosted Claude and ChatGPT require a separate OAuth rollout. Traffic uses TLS, API keys are stored as SHA-256 hashes and shown once, and public-scope keys are limited to /api/v1 endpoints. The prepaid wallet balance sets a spend cap, and failed operations are not billed. Free limits are 10 requests per minute and 200 per day; Max allows 120 per minute and 5,000 per day.