YepAPI vs Semrush API

YepAPI charges by call or other metered use, with no subscription or monthly minimum. The pricing page lists Google SERP at $0.01 per call for 10 results, web scraping at $0.01 per call, and keyword overview from $0.03 per call. It also lists a $5 signup credit, no card required, and says failed calls are not charged. As traffic grows, the bill grows with calls and the endpoint prices you use.

Semrush pricing depends on the API. Standard API access has zero units included; live keyword data consumes 10 units per line and historical data 50. Unit packages contain 2 million to 20 million units, but prices are not published, and an eligible Semrush subscription is required. Trends Basic includes 10,000 requests monthly; Premium is available by custom quote. Local API access requires a Local Pro or Local Business subscription. Ask Semrush for the total cost of the API and any required subscription.

YepAPI presents a single API key and consistent JSON responses for SEO, SERP, scraping, social and e-commerce data, and 285 AI models. Its homepage shows POST endpoints such as /v1/seo/keywords/overview, /v1/serp/google and /v1/scrape. The docs link to an llms.txt; the homepage also lists an MCP server and agent skills. Claude Code, Cursor and Codex are named integrations. The vendor's site does not name SDKs or supported programming languages, so check the docs before choosing a client library.

Semrush separates its APIs by data and workflow, including SEO, Trends, Projects, Position Tracking, Local and Enterprise visibility. Its docs cover API keys and OAuth 2.0 access tokens, request construction, response processing, unit balances and troubleshooting. The documentation portal includes MCP setup guides for Claude, Microsoft Copilot, ChatGPT, Cursor, VS Code, Gemini, Perplexity, Lovable and Notion. The listed integration materials do not name SDKs or languages. Plan to build around the API’s endpoint and authorization requirements rather than assume a particular SDK.

Neither vendor publishes an open-source license, self-hosting option or data-export guarantee on the vendor's site. Both are presented as APIs that your application calls; the available integration details do not describe running either service in your own environment.

With YepAPI, a shared key and JSON response format span multiple endpoint types, but your code still depends on YepAPI’s endpoint names, schemas and pricing. With Semrush, API families expose Semrush-specific data and workflows, and some access depends on Semrush subscriptions or units. Moving between them is not a direct endpoint swap: expect to map different response fields and replace authentication and billing logic. Keep the data your application needs in your own storage, and confirm export and retention terms with the vendor before making either API a system of record.