API Plan Finder
REMOTE · PLANS.INTOPERSON.COM
Compare API plans on 42 conditions with cost: scraping, SERP, search, browser, email, TTS, STT, docs
Available components
+1 this week
73 73 Trust /100
Last scanned (5 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Web Scraping
Trust breakdown (7 categories)
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13025 tokens (~2170/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Changelog
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1853 → 2170 ▼ functional
- Resource “Plan comparison card” was removed ▼ functional
- The server no longer declares the “resources” capability functional
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_conditions” rewrote its description, which is the text the model reads security
- Tool “cost_scenarios” rewrote its description, which is the text the model reads security
- Tool “get_details” rewrote its description, which is the text the model reads security
- Tool “relax_conditions” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “verify_answer” rewrote its description, which is the text the model reads security
- 20 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_conditions” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Server version: 0.1.3 → 0.1.4 functional
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “cost_scenarios” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “verify_answer” rewrote its description, which is the text the model reads security
- Schema quality: 1217 → 1824 ▼ functional
- Schema quality: 1217 → 1686 ▼ functional
- Server version: 0.1.2 → 0.1.3 functional
- Server version: 0.1.1 → 0.1.2 functional
- “check_conditions” added an optional parameter “min_pages_per_doc” cosmetic
- “check_conditions” added an optional parameter “monthly_document_pages” cosmetic
- “check_conditions” added an optional parameter “needs_batch_discount” cosmetic
- “check_conditions” added an optional parameter “needs_table_extraction” cosmetic
- “cost_scenarios” added an optional parameter “min_pages_per_doc” cosmetic
- “cost_scenarios” added an optional parameter “needs_batch_discount” cosmetic
- “cost_scenarios” added an optional parameter “needs_table_extraction” cosmetic
- “relax_conditions” added an optional parameter “min_pages_per_doc” cosmetic
- “relax_conditions” added an optional parameter “needs_batch_discount” cosmetic
- “relax_conditions” added an optional parameter “needs_table_extraction” cosmetic
- “search” added an optional parameter “min_pages_per_doc” cosmetic
- “search” added an optional parameter “monthly_document_pages” cosmetic
- “search” added an optional parameter “needs_batch_discount” cosmetic
- “search” added an optional parameter “needs_table_extraction” cosmetic
- “check_conditions” added an optional parameter “max_overage_usd_per_1k” cosmetic
- “check_conditions” added an optional parameter “min_log_retention_days” cosmetic
- “check_conditions” added an optional parameter “min_sending_domains” cosmetic
- “check_conditions” added an optional parameter “monthly_audio_hours” cosmetic
- “check_conditions” added an optional parameter “monthly_characters” cosmetic
- “check_conditions” added an optional parameter “monthly_emails” cosmetic
- “check_conditions” added an optional parameter “needs_batch” cosmetic
- “check_conditions” added an optional parameter “needs_commercial_use” cosmetic
- “check_conditions” added an optional parameter “needs_dedicated_ip” cosmetic
- “check_conditions” added an optional parameter “needs_diarization” cosmetic
- “check_conditions” added an optional parameter “needs_inbound” cosmetic
- “check_conditions” added an optional parameter “needs_korean” cosmetic
- “check_conditions” added an optional parameter “needs_no_min_billing” cosmetic
- “check_conditions” added an optional parameter “needs_no_training” cosmetic
- “check_conditions” added an optional parameter “needs_streaming” cosmetic
- “check_conditions” added an optional parameter “needs_voice_cloning” cosmetic
- “cost_scenarios” added an optional parameter “max_overage_usd_per_1k” cosmetic
- “cost_scenarios” added an optional parameter “min_log_retention_days” cosmetic
- “cost_scenarios” added an optional parameter “min_sending_domains” cosmetic
- “cost_scenarios” added an optional parameter “needs_batch” cosmetic
- “cost_scenarios” added an optional parameter “needs_commercial_use” cosmetic
- “cost_scenarios” added an optional parameter “needs_dedicated_ip” cosmetic
- “cost_scenarios” added an optional parameter “needs_diarization” cosmetic
- “cost_scenarios” added an optional parameter “needs_inbound” cosmetic
- “cost_scenarios” added an optional parameter “needs_korean” cosmetic
- “cost_scenarios” added an optional parameter “needs_no_min_billing” cosmetic
- “cost_scenarios” added an optional parameter “needs_no_training” cosmetic
- “cost_scenarios” added an optional parameter “needs_streaming” cosmetic
- “cost_scenarios” added an optional parameter “needs_voice_cloning” cosmetic
- “relax_conditions” added an optional parameter “max_overage_usd_per_1k” cosmetic
- “relax_conditions” added an optional parameter “min_log_retention_days” cosmetic
- “relax_conditions” added an optional parameter “min_sending_domains” cosmetic
- “relax_conditions” added an optional parameter “needs_batch” cosmetic
- “relax_conditions” added an optional parameter “needs_commercial_use” cosmetic
- “relax_conditions” added an optional parameter “needs_dedicated_ip” cosmetic
- “relax_conditions” added an optional parameter “needs_diarization” cosmetic
- “relax_conditions” added an optional parameter “needs_inbound” cosmetic
- “relax_conditions” added an optional parameter “needs_korean” cosmetic
- “relax_conditions” added an optional parameter “needs_no_min_billing” cosmetic
- “relax_conditions” added an optional parameter “needs_no_training” cosmetic
- “relax_conditions” added an optional parameter “needs_streaming” cosmetic
- “relax_conditions” added an optional parameter “needs_voice_cloning” cosmetic
- “search” added an optional parameter “max_overage_usd_per_1k” cosmetic
- “search” added an optional parameter “min_log_retention_days” cosmetic
- “search” added an optional parameter “min_sending_domains” cosmetic
- “search” added an optional parameter “monthly_audio_hours” cosmetic
- “search” added an optional parameter “monthly_characters” cosmetic
- “search” added an optional parameter “monthly_emails” cosmetic
- “search” added an optional parameter “needs_batch” cosmetic
- “search” added an optional parameter “needs_commercial_use” cosmetic
- “search” added an optional parameter “needs_dedicated_ip” cosmetic
- “search” added an optional parameter “needs_diarization” cosmetic
- “search” added an optional parameter “needs_inbound” cosmetic
- “search” added an optional parameter “needs_korean” cosmetic
- “search” added an optional parameter “needs_no_min_billing” cosmetic
- “search” added an optional parameter “needs_no_training” cosmetic
- “search” added an optional parameter “needs_streaming” cosmetic
- “search” added an optional parameter “needs_voice_cloning” cosmetic
- “check_conditions” reworded the description of “needs_no_training” cosmetic
- “cost_scenarios” reworded the description of “needs_no_training” cosmetic
- “relax_conditions” reworded the description of “needs_no_training” cosmetic
- “search” reworded the description of “needs_no_training” cosmetic
- “relax_conditions” reworded the description of “negotiable” cosmetic
- Tool “search” changed its title: Find web data API plans by conditions → Find API plans by conditions cosmetic
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 7209 → 8525 ▼ functional
- Schema quality: good → excellent functional
- Server version: 0.1.0 → 0.1.1 functional
- New tool “verify_answer” functional
- “check_conditions” added an optional parameter “captcha_solving” cosmetic
- “check_conditions” added an optional parameter “min_session_minutes” cosmetic
- “check_conditions” added an optional parameter “monthly_browser_hours” cosmetic
- “check_conditions” added an optional parameter “persistent_profiles” cosmetic
- “check_conditions” added an optional parameter “proxies_included” cosmetic
- “check_conditions” added an optional parameter “session_recording” cosmetic
- “cost_scenarios” added an optional parameter “captcha_solving” cosmetic
- “cost_scenarios” added an optional parameter “min_session_minutes” cosmetic
- “cost_scenarios” added an optional parameter “persistent_profiles” cosmetic
- “cost_scenarios” added an optional parameter “proxies_included” cosmetic
- “cost_scenarios” added an optional parameter “session_recording” cosmetic
- “relax_conditions” added an optional parameter “captcha_solving” cosmetic
- “relax_conditions” added an optional parameter “min_session_minutes” cosmetic
- “relax_conditions” added an optional parameter “persistent_profiles” cosmetic
- “relax_conditions” added an optional parameter “proxies_included” cosmetic
- “relax_conditions” added an optional parameter “session_recording” cosmetic
- “search” added an optional parameter “captcha_solving” cosmetic
- “search” added an optional parameter “min_session_minutes” cosmetic
- “search” added an optional parameter “monthly_browser_hours” cosmetic
- “search” added an optional parameter “persistent_profiles” cosmetic
- “search” added an optional parameter “proxies_included” cosmetic
- “search” added an optional parameter “session_recording” cosmetic
- “relax_conditions” reworded the description of “negotiable” cosmetic
Diagnostics
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://plans.intoperson.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=intoperson.com | CN=YE2,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 56acdc397e032f4141cd5a30ad58e1bc038 |
| SANs: *.intoperson.com, intoperson.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of plans.intoperson.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| intoperson.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://plans.intoperson.com/mcp | Verified | 200 | |
| http (plaintext) | http://plans.intoperson.com/mcp | Inconclusive | 405 |
MCP tools
· 6 exposed
· ~12,471 tokens
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tool
Tokens
check_conditions Check plans against conditions ~3,204
Call this right before choosing or buying an API plan: it returns, for each plan, whether it meets every condition, the monthly cost, and the official sentence behind each verdict. Use this when: the user names specific plans (by name, id or pricing-page URL) and wants to know whether they meet the workload and conditions, or which plan of the same product is the cheapest that does. Do not use this when: the user has no plans in mind yet (use search). Call it right before you choose or buy a tool or plan; format "brief" returns a short answer. Check specific plans, given by plan id, plan name or pricing-page URL, against the workload and conditions; up to 20 plans in one call are judged against the same conditions. Returns met / not met / unknown per condition with the official source sentence, which plans and billing options each value applies to, and a purchase link. For each plan it also names the cheapest plan of the same product that meets every required condition, with its monthly cost, or null if none does. An ambiguous name or URL returns the candidate plans instead of a guess. If you already have candidate plans or providers (for example from a web search), pass them as providers (search) or offer_ids (check_conditions) so that only those are judged. Example: 2 plans by id against 100,000 emails a month with a dedicated IP.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_extraction_pages | integer | – | How many of the pages need their fields extracted by an AI model (from a prompt or a schema, or automatically) without writing selectors. Each page counts in one of the two extraction fields. |
| billing_types | array | – | Acceptable billing: monthly_subscription (A plan with a fixed fee (or minimum commitment) billed every month.) annual_subscription (A plan paid for a year at a time.) pay_as_you_go (No plan fee; a pr… |
| browser_seconds_per_page | number | – | Browser time per page in seconds, for headless-browser products billed by time. Every plan must then serve pages that take this long: a hosted browser does, a request-based API only when one request… |
| captcha_solving | boolean | – | The plan must solve CAPTCHAs for the browser sessions (the vendor does it, not the buyer own service). |
| data_regions | array | – | Regions where data must be stored or processed, e.g. ["EU"]. Different from exit-IP countries. |
| detail | string | – | summary returns one source sentence per fact; full returns every recorded fact and sentence. |
| exit_ip_countries | array | – | ISO 3166-1 alpha-2 codes of countries the page requests must exit from, e.g. ["US","DE"]. For search results of a country use search_countries. |
| failed_requests_not_billed | boolean | – | Requests that fail on the provider side (timeouts, blocks, 5xx) must not be billed. A flat monthly price for unlimited requests meets it, since no request is billed on its own; when only success-base… |
| format | string | – | brief returns, per plan, the plan, provider, whether it meets all, the monthly cost and the requested conditions only, each with its verdict, a one-line reason, one source sentence and its source (ab… |
| max_monthly_cost_usd | number | – | Monthly budget in USD before tax. Compared with listed prices; annual plans use their per-month equivalent. |
| max_overage_usd_per_1k | number | – | The most the plan may charge for each 1,000 emails beyond its included volume, in USD, for transactional email. A plan whose extra price is not published as a per-1,000 figure is unknown. |
| mcp_auth | array | – | Ways to authenticate to the provider's hosted MCP endpoint, any one of which will do: api_key, oauth. Met when the endpoint accepts at least one of them; implies a hosted endpoint. |
| min_concurrency | integer | – | Minimum number of concurrent requests (or browsers) the plan must allow. |
| min_log_retention_days | integer | – | Days the plan must keep the logs or events of sent email where the account can read them, for transactional email. Longer retention sold as an add-on does not count. |
| min_pages_per_crawl | integer | – | Pages one crawl job (from one start URL, following links) must be able to reach. A plan whose crawl has no page cap meets any number; give the size of the largest site to crawl. Different from the mo… |
| min_pages_per_doc | integer | – | Pages one document may have at the most the plan allows, for document parsing. Met when the stated limit is at least this many (or the pages say there is no page limit); a plan whose pages do not sta… |
| min_requests_per_minute | number | – | Minimum request rate the plan must allow, per minute. |
| min_sending_domains | integer | – | Sending domains the plan must let one account authenticate, for transactional email. Met when the stated limit is at least this many (or the pages say it is unlimited); a plan whose pages do not stat… |
| min_session_minutes | number | – | Minutes one browser session must be able to run on this plan, for hosted browsers. Met when the stated longest session of the plan is at least this long; a plan whose pages do not state a session lim… |
| monthly_audio_hours | number | – | Hours of audio transcribed per month, for speech-to-text APIs (Deepgram, AssemblyAI, Speechmatics, Amazon Transcribe, Google Cloud, OpenAI). A price given per minute is multiplied by 60. It is the wh… |
| monthly_browser_hours | number | – | Browser time per month in hours, for hosted browsers (Browserbase, Browserless) billed by browser time. It is the whole workload: give it instead of monthly_pages, monthly_searches and browser_second… |
| monthly_characters | number | – | Characters of text voiced per month, for text-to-speech APIs (ElevenLabs, Cartesia, Deepgram Aura, OpenAI, Google Cloud, Amazon Polly, Azure, Gradium, Rime, Inworld, MiniMax, Murf, Hume). It is the w… |
| monthly_document_pages | number | – | Pages of documents parsed per month, for document-parsing APIs (LlamaParse, Reducto, Unstructured, Mistral OCR, LandingAI, Amazon Textract, Google Document AI, Azure Document Intelligence, Datalab, M… |
| monthly_emails | number | – | Emails sent per month, for transactional email APIs (SendGrid, Mailgun, Postmark, Resend, Amazon SES, Brevo, Mailtrap, Loops). It is the whole workload: give it instead of monthly_pages, monthly_sear… |
| monthly_pages | object | – | Pages per month by type: plain_html (static pages), javascript (needs rendering), premium_proxy (blocked sites that need residential/premium proxies), javascript_premium_proxy (both). |
| monthly_pages_total | integer | – | Total pages per month when the split by type is not known yet. Costs and verdicts then cover every share of JavaScript-rendered pages from 0% to 100% of the total (no premium proxies), and the result… |
| monthly_searches | integer | – | Search requests per month (one results page each). |
| needs_batch | boolean | – | The plan must transcribe recorded audio (a file or a stored recording), for speech-to-text. A plan priced for live audio only is not met. |
| needs_batch_discount | boolean | – | An official page must say a batch or asynchronous way of sending documents costs less than the list price on the plan, for document parsing. The budget and the cost are judged at the list price, not… |
| needs_commercial_use | boolean | – | The plan must allow commercial use of the generated audio, for text-to-speech. A free plan limited to non-commercial use does not count; a plan whose pages do not say is unknown. |
| needs_dedicated_ip | boolean | – | The plan must come with a dedicated sending IP address, for transactional email. A dedicated IP sold only as an add-on on top of the plan, or only on another plan, does not count. |
| needs_diarization | boolean | – | The plan must label who spoke (speaker diarization), for speech-to-text. Where the vendor charges extra for it, the extra price is added to the monthly cost; where the pages state no price or no incl… |
| needs_inbound | boolean | – | The service must receive email for the buyer and hand it on (inbound parsing, routes), for transactional email. |
| needs_korean | boolean | – | The service must voice Korean text (text-to-speech) or transcribe Korean speech (speech-to-text). |
| needs_no_min_billing | boolean | – | An official page must say audio is billed by the second (or an increment of seconds) with no minimum billed duration per request, for speech-to-text. A page that says nothing about rounding is unknow… |
| needs_no_training | boolean | – | An official page must say the vendor does not use the buyer's text, audio or documents to train its models without the buyer opting in. A use that is on by default with an opt-out to ask for does not… |
| needs_official_mcp | boolean | – | The provider must publish its own MCP server (hosted by it or run by the buyer), stated in its official documentation. A server only a third party published does not count. |
| needs_recurring_free_tier | boolean | – | The plan must be usable every month without paying (a free plan with a monthly allowance or a monthly free credit). |
| needs_remote_mcp | boolean | – | The provider must host a remote MCP endpoint (a URL an MCP client connects to). An official server that can only be run on the buyer own machine does not meet it. |
| needs_soc2 | boolean|string | – | The provider must hold a SOC 2 report: true for Type I or Type II, "II" for Type II. |
| needs_streaming | boolean | – | The service must return audio in real time as it is made (streaming or a WebSocket), for text-to-speech; for speech-to-text, it must transcribe live audio as it arrives. A speech-to-text price line i… |
| needs_table_extraction | boolean | – | The service must return the tables of a page as structure (rows and cells), not only the text, for document parsing. |
| needs_voice_cloning | boolean | – | The plan must let the account clone a voice from its own recording, for text-to-speech. Cloning limited to eligible customers, a request form or an enterprise plan does not count for a plan that is n… |
| needs_zdr | boolean | – | Zero data retention must be usable on this plan. A provider that offers it only on a custom enterprise agreement does not meet it on its listed plans. |
| offer_ids | array | – | Plan ids to check (from search or get_details). |
| only_successful_requests_billed | boolean | – | Billing must count successful requests only: each successful request is charged (or draws credits) and failed ones cost nothing. A flat monthly price for unlimited requests does not meet it, since th… |
| persistent_profiles | boolean | – | The plan must keep browser profiles (login state, cookies) between sessions. |
| plans | array | – | Plans given by provider and plan name (e.g. "ScrapingBee Freelance") or by pricing-page URL, for plans found elsewhere. A name or URL that fits several plans returns the candidates under resolution a… |
| preferred | object | – | Nice-to-have conditions; they do not filter, they break ties. |
| proxies_included | boolean | – | The plan must include proxy traffic of the vendor (some gigabytes in the plan fee). Proxy traffic sold only per gigabyte on top of the fee, or only on another plan, does not count. |
| realtime_search_required | boolean | – | Search results must be returned in real time (not through a queue). |
| search_countries | array | – | ISO 3166-1 alpha-2 codes of the countries whose search results the searches must return (the search engine's country setting, e.g. Google gl), e.g. ["GB","CA"]. Different from exit_ip_countries. |
| search_engines | array | – | Search engines whose results the plan must return, each at the plan's search price: google, bing, yahoo, yandex, baidu, duckduckgo, naver, brave (brave is Brave's own index). monthly_searches is the… |
| search_result_types | array | – | Result types the parsed search response must contain: organic, ads, local_pack, knowledge_graph, people_also_ask, related_searches, shopping, news, images, videos, ai_overview. |
| search_returns_content | boolean | – | The search response itself must carry the text of the result pages (extracted content), not only titles, links and snippets. |
| session_recording | boolean | – | The plan must record browser sessions (video or replay) that the buyer can watch afterwards. |
| structured_extraction_pages | integer | – | How many of the pages must come back as JSON fields rather than HTML or text, by any method the plan offers (CSS or XPath selectors, a schema, or AI). When the fields must be found without writing se… |
| target_errors_not_billed | boolean | – | Error responses from the target site (e.g. 404) must not be billed. |
Structured output declared, but exposes no named fields.
No examples provided.
cost_scenarios Plan costs as the workload changes ~2,574
Use this when: the user asks how the cost changes as the workload grows or shifts, or at what volume another plan becomes the cheapest. Do not use this when: the workload is fixed (use search). Show how API plan costs change when the monthly workload changes, for example twice the pages or a larger share of JavaScript pages. Along the path from the current to a target workload it returns the cheapest fully matching plan at both ends, each workload where the cheapest plan changes, and for tracked plans where the cost first steps up, where the plan can no longer cover the volume and where the budget is exceeded. Costs follow published pricing rules (whole packs of extra credits, per-period pack limits, per-connection browser billing, monthly minimums) with official source sentences. Example: 10,000 searches a month growing to 200,000.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_extraction_pages | integer | – | How many of the pages need their fields extracted by an AI model (from a prompt or a schema, or automatically) without writing selectors. Each page counts in one of the two extraction fields. |
| billing_types | array | – | Acceptable billing: monthly_subscription (A plan with a fixed fee (or minimum commitment) billed every month.) annual_subscription (A plan paid for a year at a time.) pay_as_you_go (No plan fee; a pr… |
| browser_seconds_per_page | number | – | Browser time per page in seconds, for headless-browser products billed by time. Every plan must then serve pages that take this long: a hosted browser does, a request-based API only when one request… |
| captcha_solving | boolean | – | The plan must solve CAPTCHAs for the browser sessions (the vendor does it, not the buyer own service). |
| data_regions | array | – | Regions where data must be stored or processed, e.g. ["EU"]. Different from exit-IP countries. |
| detail | string | – | summary returns one source sentence per fact; full returns every recorded fact and sentence. |
| exit_ip_countries | array | – | ISO 3166-1 alpha-2 codes of countries the page requests must exit from, e.g. ["US","DE"]. For search results of a country use search_countries. |
| failed_requests_not_billed | boolean | – | Requests that fail on the provider side (timeouts, blocks, 5xx) must not be billed. A flat monthly price for unlimited requests meets it, since no request is billed on its own; when only success-base… |
| max_monthly_cost_usd | number | – | Monthly budget in USD before tax. Compared with listed prices; annual plans use their per-month equivalent. |
| max_overage_usd_per_1k | number | – | The most the plan may charge for each 1,000 emails beyond its included volume, in USD, for transactional email. A plan whose extra price is not published as a per-1,000 figure is unknown. |
| mcp_auth | array | – | Ways to authenticate to the provider's hosted MCP endpoint, any one of which will do: api_key, oauth. Met when the endpoint accepts at least one of them; implies a hosted endpoint. |
| min_concurrency | integer | – | Minimum number of concurrent requests (or browsers) the plan must allow. |
| min_log_retention_days | integer | – | Days the plan must keep the logs or events of sent email where the account can read them, for transactional email. Longer retention sold as an add-on does not count. |
| min_pages_per_crawl | integer | – | Pages one crawl job (from one start URL, following links) must be able to reach. A plan whose crawl has no page cap meets any number; give the size of the largest site to crawl. Different from the mo… |
| min_pages_per_doc | integer | – | Pages one document may have at the most the plan allows, for document parsing. Met when the stated limit is at least this many (or the pages say there is no page limit); a plan whose pages do not sta… |
| min_requests_per_minute | number | – | Minimum request rate the plan must allow, per minute. |
| min_sending_domains | integer | – | Sending domains the plan must let one account authenticate, for transactional email. Met when the stated limit is at least this many (or the pages say it is unlimited); a plan whose pages do not stat… |
| min_session_minutes | number | – | Minutes one browser session must be able to run on this plan, for hosted browsers. Met when the stated longest session of the plan is at least this long; a plan whose pages do not state a session lim… |
| monthly_pages | object | – | Pages per month by type: plain_html (static pages), javascript (needs rendering), premium_proxy (blocked sites that need residential/premium proxies), javascript_premium_proxy (both). |
| monthly_pages_total | integer | – | Total pages per month when the split by type is not known yet. Costs and verdicts then cover every share of JavaScript-rendered pages from 0% to 100% of the total (no premium proxies), and the result… |
| monthly_searches | integer | – | Search requests per month (one results page each). |
| needs_batch | boolean | – | The plan must transcribe recorded audio (a file or a stored recording), for speech-to-text. A plan priced for live audio only is not met. |
| needs_batch_discount | boolean | – | An official page must say a batch or asynchronous way of sending documents costs less than the list price on the plan, for document parsing. The budget and the cost are judged at the list price, not… |
| needs_commercial_use | boolean | – | The plan must allow commercial use of the generated audio, for text-to-speech. A free plan limited to non-commercial use does not count; a plan whose pages do not say is unknown. |
| needs_dedicated_ip | boolean | – | The plan must come with a dedicated sending IP address, for transactional email. A dedicated IP sold only as an add-on on top of the plan, or only on another plan, does not count. |
| needs_diarization | boolean | – | The plan must label who spoke (speaker diarization), for speech-to-text. Where the vendor charges extra for it, the extra price is added to the monthly cost; where the pages state no price or no incl… |
| needs_inbound | boolean | – | The service must receive email for the buyer and hand it on (inbound parsing, routes), for transactional email. |
| needs_korean | boolean | – | The service must voice Korean text (text-to-speech) or transcribe Korean speech (speech-to-text). |
| needs_no_min_billing | boolean | – | An official page must say audio is billed by the second (or an increment of seconds) with no minimum billed duration per request, for speech-to-text. A page that says nothing about rounding is unknow… |
| needs_no_training | boolean | – | An official page must say the vendor does not use the buyer's text, audio or documents to train its models without the buyer opting in. A use that is on by default with an opt-out to ask for does not… |
| needs_official_mcp | boolean | – | The provider must publish its own MCP server (hosted by it or run by the buyer), stated in its official documentation. A server only a third party published does not count. |
| needs_recurring_free_tier | boolean | – | The plan must be usable every month without paying (a free plan with a monthly allowance or a monthly free credit). |
| needs_remote_mcp | boolean | – | The provider must host a remote MCP endpoint (a URL an MCP client connects to). An official server that can only be run on the buyer own machine does not meet it. |
| needs_soc2 | boolean|string | – | The provider must hold a SOC 2 report: true for Type I or Type II, "II" for Type II. |
| needs_streaming | boolean | – | The service must return audio in real time as it is made (streaming or a WebSocket), for text-to-speech; for speech-to-text, it must transcribe live audio as it arrives. A speech-to-text price line i… |
| needs_table_extraction | boolean | – | The service must return the tables of a page as structure (rows and cells), not only the text, for document parsing. |
| needs_voice_cloning | boolean | – | The plan must let the account clone a voice from its own recording, for text-to-speech. Cloning limited to eligible customers, a request form or an enterprise plan does not count for a plan that is n… |
| needs_zdr | boolean | – | Zero data retention must be usable on this plan. A provider that offers it only on a custom enterprise agreement does not meet it on its listed plans. |
| offer_ids | array | – | Compare only these plans and follow each of them along the path. Default: every plan that can serve the workload, following the cheapest full match at the start. |
| only_successful_requests_billed | boolean | – | Billing must count successful requests only: each successful request is charged (or draws credits) and failed ones cost nothing. A flat monthly price for unlimited requests does not meet it, since th… |
| persistent_profiles | boolean | – | The plan must keep browser profiles (login state, cookies) between sessions. |
| preferred | object | – | Nice-to-have conditions; they do not filter, they break ties. |
| product_types | array | – | Limit to these product types. Default: every type that can serve the workload. |
| proxies_included | boolean | – | The plan must include proxy traffic of the vendor (some gigabytes in the plan fee). Proxy traffic sold only per gigabyte on top of the fee, or only on another plan, does not count. |
| realtime_search_required | boolean | – | Search results must be returned in real time (not through a queue). |
| scale | number | – | Multiply every monthly count by this factor for the end of the path, e.g. 2 for twice the current workload. Give target or scale. |
| search_countries | array | – | ISO 3166-1 alpha-2 codes of the countries whose search results the searches must return (the search engine's country setting, e.g. Google gl), e.g. ["GB","CA"]. Different from exit_ip_countries. |
| search_engines | array | – | Search engines whose results the plan must return, each at the plan's search price: google, bing, yahoo, yandex, baidu, duckduckgo, naver, brave (brave is Brave's own index). monthly_searches is the… |
| search_result_types | array | – | Result types the parsed search response must contain: organic, ads, local_pack, knowledge_graph, people_also_ask, related_searches, shopping, news, images, videos, ai_overview. |
| search_returns_content | boolean | – | The search response itself must carry the text of the result pages (extracted content), not only titles, links and snippets. |
| session_recording | boolean | – | The plan must record browser sessions (video or replay) that the buyer can watch afterwards. |
| structured_extraction_pages | integer | – | How many of the pages must come back as JSON fields rather than HTML or text, by any method the plan offers (CSS or XPath selectors, a schema, or AI). When the fields must be found without writing se… |
| target | object | – | Workload at the end of the path; fields not given keep their current value. Give target or scale. |
| target_errors_not_billed | boolean | – | Error responses from the target site (e.g. 404) must not be billed. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| assumptions | array | yes | – |
| at_end | array | yes | Up to three cheapest full matches at the target workload. |
| at_start | array | yes | Up to three cheapest full matches at the current workload. |
| compared | – | yes | – |
| counts | object|null | yes | – |
| link_notes | object | – | The note of each link level (link.link_level) of the plans in this result, stated once. |
| needs_input | array | yes | – |
| notes | array | yes | – |
| path | object|null | yes | – |
| plans | array | yes | Every plan named above, with the official facts its costs were computed from. |
| request | object | – | – |
| switches | array | yes | Each workload on the path where the cheapest full match changes. |
| tracked | array | yes | – |
No examples provided.
get_details Get recorded conditions of a plan or product ~155
Use this when: you need every recorded condition, pricing rule and source sentence of one plan or product found by search or named by the user. Do not use this when: you want to compare plans against a workload (use search or check_conditions). Get every recorded condition for one API plan or product: value, which plans it applies to, exceptions, official source sentence, check date and purchase link. A product too long for one response comes with one source sentence per fact. Example: every recorded condition of 1 plan found by search.
| Name | Type | Req | Description |
|---|---|---|---|
| offer_id | string | – | A plan id, e.g. "firecrawl-standard". |
| product_id | string | – | A product id, e.g. "firecrawl-api". |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| evidence_detail | – | – | Present when the product was too long for one response: each fact carries one source sentence. Ask for a plan by offer_id for every sentence. |
| link_notes | object | – | The note of each link level (link.link_level) of the plans in this result, stated once. |
| offers | array | yes | – |
| product | object | yes | – |
| provider | object | yes | – |
No examples provided.
relax_conditions Smallest condition changes that admit plans ~2,676
Use this when: search finds no plan or too few plans and the user wants to know which condition to loosen and by how much. Do not use this when: plans already match (use search or check_conditions). When no API plan, or too few API plans, meet every required condition: for each condition the user can change, returns the smallest change that lets at least one plan meet everything (for example the monthly budget needed, the concurrency available, or one exit-IP country to drop) and the plans it admits with their monthly cost. Also lists plans that fail only because a condition is not stated on the official pages, with the pages checked and the check date, so the user can confirm with the provider. Example: no plan meets 5,000 hours of audio a month under $100.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_extraction_pages | integer | – | How many of the pages need their fields extracted by an AI model (from a prompt or a schema, or automatically) without writing selectors. Each page counts in one of the two extraction fields. |
| billing_types | array | – | Acceptable billing: monthly_subscription (A plan with a fixed fee (or minimum commitment) billed every month.) annual_subscription (A plan paid for a year at a time.) pay_as_you_go (No plan fee; a pr… |
| browser_seconds_per_page | number | – | Browser time per page in seconds, for headless-browser products billed by time. Every plan must then serve pages that take this long: a hosted browser does, a request-based API only when one request… |
| captcha_solving | boolean | – | The plan must solve CAPTCHAs for the browser sessions (the vendor does it, not the buyer own service). |
| data_regions | array | – | Regions where data must be stored or processed, e.g. ["EU"]. Different from exit-IP countries. |
| detail | string | – | summary returns one source sentence per fact; full returns every recorded fact and sentence. |
| exit_ip_countries | array | – | ISO 3166-1 alpha-2 codes of countries the page requests must exit from, e.g. ["US","DE"]. For search results of a country use search_countries. |
| failed_requests_not_billed | boolean | – | Requests that fail on the provider side (timeouts, blocks, 5xx) must not be billed. A flat monthly price for unlimited requests meets it, since no request is billed on its own; when only success-base… |
| limit | integer | – | Maximum plans listed for each change and under confirm_with_provider (default 3). |
| max_monthly_cost_usd | number | – | Monthly budget in USD before tax. Compared with listed prices; annual plans use their per-month equivalent. |
| max_overage_usd_per_1k | number | – | The most the plan may charge for each 1,000 emails beyond its included volume, in USD, for transactional email. A plan whose extra price is not published as a per-1,000 figure is unknown. |
| mcp_auth | array | – | Ways to authenticate to the provider's hosted MCP endpoint, any one of which will do: api_key, oauth. Met when the endpoint accepts at least one of them; implies a hosted endpoint. |
| min_concurrency | integer | – | Minimum number of concurrent requests (or browsers) the plan must allow. |
| min_log_retention_days | integer | – | Days the plan must keep the logs or events of sent email where the account can read them, for transactional email. Longer retention sold as an add-on does not count. |
| min_pages_per_crawl | integer | – | Pages one crawl job (from one start URL, following links) must be able to reach. A plan whose crawl has no page cap meets any number; give the size of the largest site to crawl. Different from the mo… |
| min_pages_per_doc | integer | – | Pages one document may have at the most the plan allows, for document parsing. Met when the stated limit is at least this many (or the pages say there is no page limit); a plan whose pages do not sta… |
| min_requests_per_minute | number | – | Minimum request rate the plan must allow, per minute. |
| min_sending_domains | integer | – | Sending domains the plan must let one account authenticate, for transactional email. Met when the stated limit is at least this many (or the pages say it is unlimited); a plan whose pages do not stat… |
| min_session_minutes | number | – | Minutes one browser session must be able to run on this plan, for hosted browsers. Met when the stated longest session of the plan is at least this long; a plan whose pages do not state a session lim… |
| monthly_pages | object | – | Pages per month by type: plain_html (static pages), javascript (needs rendering), premium_proxy (blocked sites that need residential/premium proxies), javascript_premium_proxy (both). |
| monthly_pages_total | integer | – | Total pages per month when the split by type is not known yet. Costs and verdicts then cover every share of JavaScript-rendered pages from 0% to 100% of the total (no premium proxies), and the result… |
| monthly_searches | integer | – | Search requests per month (one results page each). |
| needs_batch | boolean | – | The plan must transcribe recorded audio (a file or a stored recording), for speech-to-text. A plan priced for live audio only is not met. |
| needs_batch_discount | boolean | – | An official page must say a batch or asynchronous way of sending documents costs less than the list price on the plan, for document parsing. The budget and the cost are judged at the list price, not… |
| needs_commercial_use | boolean | – | The plan must allow commercial use of the generated audio, for text-to-speech. A free plan limited to non-commercial use does not count; a plan whose pages do not say is unknown. |
| needs_dedicated_ip | boolean | – | The plan must come with a dedicated sending IP address, for transactional email. A dedicated IP sold only as an add-on on top of the plan, or only on another plan, does not count. |
| needs_diarization | boolean | – | The plan must label who spoke (speaker diarization), for speech-to-text. Where the vendor charges extra for it, the extra price is added to the monthly cost; where the pages state no price or no incl… |
| needs_inbound | boolean | – | The service must receive email for the buyer and hand it on (inbound parsing, routes), for transactional email. |
| needs_korean | boolean | – | The service must voice Korean text (text-to-speech) or transcribe Korean speech (speech-to-text). |
| needs_no_min_billing | boolean | – | An official page must say audio is billed by the second (or an increment of seconds) with no minimum billed duration per request, for speech-to-text. A page that says nothing about rounding is unknow… |
| needs_no_training | boolean | – | An official page must say the vendor does not use the buyer's text, audio or documents to train its models without the buyer opting in. A use that is on by default with an opt-out to ask for does not… |
| needs_official_mcp | boolean | – | The provider must publish its own MCP server (hosted by it or run by the buyer), stated in its official documentation. A server only a third party published does not count. |
| needs_recurring_free_tier | boolean | – | The plan must be usable every month without paying (a free plan with a monthly allowance or a monthly free credit). |
| needs_remote_mcp | boolean | – | The provider must host a remote MCP endpoint (a URL an MCP client connects to). An official server that can only be run on the buyer own machine does not meet it. |
| needs_soc2 | boolean|string | – | The provider must hold a SOC 2 report: true for Type I or Type II, "II" for Type II. |
| needs_streaming | boolean | – | The service must return audio in real time as it is made (streaming or a WebSocket), for text-to-speech; for speech-to-text, it must transcribe live audio as it arrives. A speech-to-text price line i… |
| needs_table_extraction | boolean | – | The service must return the tables of a page as structure (rows and cells), not only the text, for document parsing. |
| needs_voice_cloning | boolean | – | The plan must let the account clone a voice from its own recording, for text-to-speech. Cloning limited to eligible customers, a request form or an enterprise plan does not count for a plan that is n… |
| needs_zdr | boolean | – | Zero data retention must be usable on this plan. A provider that offers it only on a custom enterprise agreement does not meet it on its listed plans. |
| negotiable | array | – | Conditions the user said can change: monthly_volume, concurrency, rate_limit, monthly_budget, billing_type, free_allowance, failed_request_billing, success_billing, target_error_billing, geo_targetin… |
| only_successful_requests_billed | boolean | – | Billing must count successful requests only: each successful request is charged (or draws credits) and failed ones cost nothing. A flat monthly price for unlimited requests does not meet it, since th… |
| persistent_profiles | boolean | – | The plan must keep browser profiles (login state, cookies) between sessions. |
| preferred | object | – | Nice-to-have conditions; they do not filter, they break ties. |
| product_types | array | – | Limit to these product types. Default: every type that can serve the workload. |
| proxies_included | boolean | – | The plan must include proxy traffic of the vendor (some gigabytes in the plan fee). Proxy traffic sold only per gigabyte on top of the fee, or only on another plan, does not count. |
| realtime_search_required | boolean | – | Search results must be returned in real time (not through a queue). |
| search_countries | array | – | ISO 3166-1 alpha-2 codes of the countries whose search results the searches must return (the search engine's country setting, e.g. Google gl), e.g. ["GB","CA"]. Different from exit_ip_countries. |
| search_engines | array | – | Search engines whose results the plan must return, each at the plan's search price: google, bing, yahoo, yandex, baidu, duckduckgo, naver, brave (brave is Brave's own index). monthly_searches is the… |
| search_result_types | array | – | Result types the parsed search response must contain: organic, ads, local_pack, knowledge_graph, people_also_ask, related_searches, shopping, news, images, videos, ai_overview. |
| search_returns_content | boolean | – | The search response itself must carry the text of the result pages (extracted content), not only titles, links and snippets. |
| session_recording | boolean | – | The plan must record browser sessions (video or replay) that the buyer can watch afterwards. |
| structured_extraction_pages | integer | – | How many of the pages must come back as JSON fields rather than HTML or text, by any method the plan offers (CSS or XPath selectors, a schema, or AI). When the fields must be found without writing se… |
| target_errors_not_billed | boolean | – | Error responses from the target site (e.g. 404) must not be billed. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| assumptions | array | yes | – |
| changes | array | yes | – |
| confirm_with_provider | object | yes | – |
| counts | object | yes | – |
| link_notes | object | – | The note of each link level (link.link_level) of the plans in this result, stated once. |
| needs_input | array | yes | – |
| notes | array | yes | – |
| request | object | – | – |
No examples provided.
search Find API plans by conditions ~3,516
Call this right before choosing or buying an API plan: it returns, for each plan, whether it meets every condition, the monthly cost, and the official sentence behind each verdict. Use this when: the user wants to know which API plans (web scraping, SERP, web search, browser infrastructure, transactional email, text-to-speech, speech-to-text, document parsing) fit a monthly workload, budget or required conditions, or what one would cost per month at that workload. Do not use this when: the user wants to scrape, search the web, send email, generate speech, transcribe audio or parse a document itself (this tool reads no pages and calls no provider), needs proxies only, or asks about an API outside these fields. Call it right before you choose or buy a tool or plan; format "brief" returns a short answer. Find API plans (web scraping, SERP, web search, browser infrastructure, transactional email, text-to-speech, speech-to-text, document parsing) that meet required conditions: monthly pages by type (plain HTML, JavaScript rendering, blocked sites that need premium proxies), monthly searches, concurrency, requests per minute, monthly budget before tax, billing type, exit-IP countries, search engines, search-result countries and parsed result types, pages per crawl, data storage region and structured (JSON) or AI extraction. Browser infrastructure is asked in monthly browser hours, transactional email in monthly emails, text-to-speech in monthly characters, speech-to-text in monthly audio hours and document parsing in monthly document pages, each with its own conditions (for example session length, dedicated IP, voice cloning, Korean, live or recorded audio, speaker labels, pages per document, table extraction, batch discount). For search APIs it also checks the agent connection: an official or remote (hosted) MCP server and how it signs in (API key or OAuth), zero data retention on the plan, a SOC 2 report, and whether results carry the page text. Returns each plan's mon…
| Name | Type | Req | Description |
|---|---|---|---|
| ai_extraction_pages | integer | – | How many of the pages need their fields extracted by an AI model (from a prompt or a schema, or automatically) without writing selectors. Each page counts in one of the two extraction fields. |
| billing_types | array | – | Acceptable billing: monthly_subscription (A plan with a fixed fee (or minimum commitment) billed every month.) annual_subscription (A plan paid for a year at a time.) pay_as_you_go (No plan fee; a pr… |
| browser_seconds_per_page | number | – | Browser time per page in seconds, for headless-browser products billed by time. Every plan must then serve pages that take this long: a hosted browser does, a request-based API only when one request… |
| captcha_solving | boolean | – | The plan must solve CAPTCHAs for the browser sessions (the vendor does it, not the buyer own service). |
| data_regions | array | – | Regions where data must be stored or processed, e.g. ["EU"]. Different from exit-IP countries. |
| detail | string | – | summary returns one source sentence per fact; full returns every recorded fact and sentence. |
| exit_ip_countries | array | – | ISO 3166-1 alpha-2 codes of countries the page requests must exit from, e.g. ["US","DE"]. For search results of a country use search_countries. |
| failed_requests_not_billed | boolean | – | Requests that fail on the provider side (timeouts, blocks, 5xx) must not be billed. A flat monthly price for unlimited requests meets it, since no request is billed on its own; when only success-base… |
| format | string | – | brief returns, per plan, the plan, provider, whether it meets all, the monthly cost and the requested conditions only, each with its verdict, a one-line reason, one source sentence and its source (ab… |
| limit | integer | – | Maximum plans returned in each list (default and maximum 5). |
| max_monthly_cost_usd | number | – | Monthly budget in USD before tax. Compared with listed prices; annual plans use their per-month equivalent. |
| max_overage_usd_per_1k | number | – | The most the plan may charge for each 1,000 emails beyond its included volume, in USD, for transactional email. A plan whose extra price is not published as a per-1,000 figure is unknown. |
| mcp_auth | array | – | Ways to authenticate to the provider's hosted MCP endpoint, any one of which will do: api_key, oauth. Met when the endpoint accepts at least one of them; implies a hosted endpoint. |
| min_concurrency | integer | – | Minimum number of concurrent requests (or browsers) the plan must allow. |
| min_log_retention_days | integer | – | Days the plan must keep the logs or events of sent email where the account can read them, for transactional email. Longer retention sold as an add-on does not count. |
| min_pages_per_crawl | integer | – | Pages one crawl job (from one start URL, following links) must be able to reach. A plan whose crawl has no page cap meets any number; give the size of the largest site to crawl. Different from the mo… |
| min_pages_per_doc | integer | – | Pages one document may have at the most the plan allows, for document parsing. Met when the stated limit is at least this many (or the pages say there is no page limit); a plan whose pages do not sta… |
| min_requests_per_minute | number | – | Minimum request rate the plan must allow, per minute. |
| min_sending_domains | integer | – | Sending domains the plan must let one account authenticate, for transactional email. Met when the stated limit is at least this many (or the pages say it is unlimited); a plan whose pages do not stat… |
| min_session_minutes | number | – | Minutes one browser session must be able to run on this plan, for hosted browsers. Met when the stated longest session of the plan is at least this long; a plan whose pages do not state a session lim… |
| monthly_audio_hours | number | – | Hours of audio transcribed per month, for speech-to-text APIs (Deepgram, AssemblyAI, Speechmatics, Amazon Transcribe, Google Cloud, OpenAI). A price given per minute is multiplied by 60. It is the wh… |
| monthly_browser_hours | number | – | Browser time per month in hours, for hosted browsers (Browserbase, Browserless) billed by browser time. It is the whole workload: give it instead of monthly_pages, monthly_searches and browser_second… |
| monthly_characters | number | – | Characters of text voiced per month, for text-to-speech APIs (ElevenLabs, Cartesia, Deepgram Aura, OpenAI, Google Cloud, Amazon Polly, Azure, Gradium, Rime, Inworld, MiniMax, Murf, Hume). It is the w… |
| monthly_document_pages | number | – | Pages of documents parsed per month, for document-parsing APIs (LlamaParse, Reducto, Unstructured, Mistral OCR, LandingAI, Amazon Textract, Google Document AI, Azure Document Intelligence, Datalab, M… |
| monthly_emails | number | – | Emails sent per month, for transactional email APIs (SendGrid, Mailgun, Postmark, Resend, Amazon SES, Brevo, Mailtrap, Loops). It is the whole workload: give it instead of monthly_pages, monthly_sear… |
| monthly_pages | object | – | Pages per month by type: plain_html (static pages), javascript (needs rendering), premium_proxy (blocked sites that need residential/premium proxies), javascript_premium_proxy (both). |
| monthly_pages_total | integer | – | Total pages per month when the split by type is not known yet. Costs and verdicts then cover every share of JavaScript-rendered pages from 0% to 100% of the total (no premium proxies), and the result… |
| monthly_searches | integer | – | Search requests per month (one results page each). |
| needs_batch | boolean | – | The plan must transcribe recorded audio (a file or a stored recording), for speech-to-text. A plan priced for live audio only is not met. |
| needs_batch_discount | boolean | – | An official page must say a batch or asynchronous way of sending documents costs less than the list price on the plan, for document parsing. The budget and the cost are judged at the list price, not… |
| needs_commercial_use | boolean | – | The plan must allow commercial use of the generated audio, for text-to-speech. A free plan limited to non-commercial use does not count; a plan whose pages do not say is unknown. |
| needs_dedicated_ip | boolean | – | The plan must come with a dedicated sending IP address, for transactional email. A dedicated IP sold only as an add-on on top of the plan, or only on another plan, does not count. |
| needs_diarization | boolean | – | The plan must label who spoke (speaker diarization), for speech-to-text. Where the vendor charges extra for it, the extra price is added to the monthly cost; where the pages state no price or no incl… |
| needs_inbound | boolean | – | The service must receive email for the buyer and hand it on (inbound parsing, routes), for transactional email. |
| needs_korean | boolean | – | The service must voice Korean text (text-to-speech) or transcribe Korean speech (speech-to-text). |
| needs_no_min_billing | boolean | – | An official page must say audio is billed by the second (or an increment of seconds) with no minimum billed duration per request, for speech-to-text. A page that says nothing about rounding is unknow… |
| needs_no_training | boolean | – | An official page must say the vendor does not use the buyer's text, audio or documents to train its models without the buyer opting in. A use that is on by default with an opt-out to ask for does not… |
| needs_official_mcp | boolean | – | The provider must publish its own MCP server (hosted by it or run by the buyer), stated in its official documentation. A server only a third party published does not count. |
| needs_recurring_free_tier | boolean | – | The plan must be usable every month without paying (a free plan with a monthly allowance or a monthly free credit). |
| needs_remote_mcp | boolean | – | The provider must host a remote MCP endpoint (a URL an MCP client connects to). An official server that can only be run on the buyer own machine does not meet it. |
| needs_soc2 | boolean|string | – | The provider must hold a SOC 2 report: true for Type I or Type II, "II" for Type II. |
| needs_streaming | boolean | – | The service must return audio in real time as it is made (streaming or a WebSocket), for text-to-speech; for speech-to-text, it must transcribe live audio as it arrives. A speech-to-text price line i… |
| needs_table_extraction | boolean | – | The service must return the tables of a page as structure (rows and cells), not only the text, for document parsing. |
| needs_voice_cloning | boolean | – | The plan must let the account clone a voice from its own recording, for text-to-speech. Cloning limited to eligible customers, a request form or an enterprise plan does not count for a plan that is n… |
| needs_zdr | boolean | – | Zero data retention must be usable on this plan. A provider that offers it only on a custom enterprise agreement does not meet it on its listed plans. |
| only_successful_requests_billed | boolean | – | Billing must count successful requests only: each successful request is charged (or draws credits) and failed ones cost nothing. A flat monthly price for unlimited requests does not meet it, since th… |
| persistent_profiles | boolean | – | The plan must keep browser profiles (login state, cookies) between sessions. |
| preferred | object | – | Nice-to-have conditions; they do not filter, they break ties. |
| product_types | array | – | Limit to these product types. Default: every type that can serve the workload. |
| providers | array | – | Judge only the plans of these providers (candidates you already have, for example from a web search). Give provider ids or names as listed, such as "tavily", "Brave Search API" or "You.com"; case doe… |
| proxies_included | boolean | – | The plan must include proxy traffic of the vendor (some gigabytes in the plan fee). Proxy traffic sold only per gigabyte on top of the fee, or only on another plan, does not count. |
| realtime_search_required | boolean | – | Search results must be returned in real time (not through a queue). |
| search_countries | array | – | ISO 3166-1 alpha-2 codes of the countries whose search results the searches must return (the search engine's country setting, e.g. Google gl), e.g. ["GB","CA"]. Different from exit_ip_countries. |
| search_engines | array | – | Search engines whose results the plan must return, each at the plan's search price: google, bing, yahoo, yandex, baidu, duckduckgo, naver, brave (brave is Brave's own index). monthly_searches is the… |
| search_result_types | array | – | Result types the parsed search response must contain: organic, ads, local_pack, knowledge_graph, people_also_ask, related_searches, shopping, news, images, videos, ai_overview. |
| search_returns_content | boolean | – | The search response itself must carry the text of the result pages (extracted content), not only titles, links and snippets. |
| session_recording | boolean | – | The plan must record browser sessions (video or replay) that the buyer can watch afterwards. |
| structured_extraction_pages | integer | – | How many of the pages must come back as JSON fields rather than HTML or text, by any method the plan offers (CSS or XPath selectors, a schema, or AI). When the fields must be found without writing se… |
| target_errors_not_billed | boolean | – | Error responses from the target site (e.g. 404) must not be billed. |
Structured output declared, but exposes no named fields.
No examples provided.
verify_answer Check an answer's plan claims against the recorded facts ~346
Use this when: you have drafted an answer that names API plans, costs or whether they meet the user's conditions, before you give it. Do not use this when: you have not looked up any plan yet (use search). Check what a drafted answer says about API plans against the recorded official facts, using the user's conditions as given in request. For each plan claim (plan id, name or pricing-page URL, with the stated billing, monthly cost, whether it meets every condition, single condition verdicts and recorded values) it returns conflicts with the official source sentences, the check date and a one-line fix: a plan not in the catalog, unmet or unknown conditions stated as met, met stated as unmet, a condition verdict, a cost outside the computed cost or range, or a value that differs. It also lists verdicts that rest on a derived value, official pages that disagree or a two-value price range (state the condition), plans it could not check (an ambiguous name returns the candidates), the cheapest plan that meets every condition when the answer does not name it, and words of the question that suggest a condition the request does not carry. Example: a drafted answer says 1 plan costs $49 a month for 100,000 emails.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | One entry per plan the answer names, with what the answer says about it. |
| question | string | – | The user's words, if available. Read only for words that suggest a condition the request does not carry. |
| request | object | yes | The user's workload and required conditions as you understood them, in the search input format. Each claim is judged against these, not against earlier calls. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_scope | string | yes | What this call checked and what it did not. |
| conditional | array | yes | Verdicts or costs of the answer that rest on a derived value, official pages that disagree, or a price range of two official values. State the condition with the claim. |
| conflicts | array | yes | Claims the record contradicts or does not back. Correct each before giving the answer. facts are keys of evidence. |
| consistent | boolean | yes | True when no claim conflicts with the record (all claims are judged, also those left out of this result for its size). |
| evidence | object | yes | The official sentences ({source, quote}) of each fact id that conflicts and conditional refer to, once per fact. |
| limits | array | yes | Known gaps of the record that the request touches. They are not conflicts. |
| omitted | array | yes | The cheapest plan that meets every required condition of the request, when the answer does not name it. |
| request_may_omit | array | yes | Words of the question that suggest a condition the request does not carry. |
| request_used | object | yes | The request the claims were judged against. |
| unchecked | array | yes | Claims that could not be checked: an ambiguous name (candidates listed), a plan not in this catalog, a condition the request does not carry, a key with no recorded field, or claims past the result si… |
No examples provided.
Install
How do I install the API Plan Finder MCP server?
API Plan Finder is a hosted endpoint at https://plans.intoperson.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · plans.intoperson.com
# add to Claude Code
claude mcp add --transport http scraping-api-plans-web-data-plan-finder 'https://plans.intoperson.com/mcp'
Common questions
What is the API Plan Finder MCP server?
API Plan Finder is an MCP server listed in the public MCP registry as io.github.scraping-api-plans/web-data-plan-finder. Compare API plans on 42 conditions with cost: scraping, SERP, search, browser, email, TTS, STT, docs. This page covers its hosted endpoint (https://plans.intoperson.com/mcp).
Is the API Plan Finder MCP server safe to use?
API Plan Finder scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the API Plan Finder MCP server expose?
API Plan Finder exposes 6 tools: search, get_details, check_conditions, cost_scenarios, relax_conditions, verify_answer. Their descriptions and schemas cost roughly 12,471 tokens of context every time the server is loaded.
Does the API Plan Finder MCP server require authentication?
No. We connected to API Plan Finder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the API Plan Finder MCP server still maintained?
API Plan Finder is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.