Playbook
Use RapidAPI when a registered marketplace listing covers the data you need. RapidAPI is a marketplace like Apify: one Deepline-managed key reaches every listing Deepline is subscribed to, but each listing bills against its own plan, so only listings registered in Deepline can be called.- Prefer the typed listing tools first:
rapidapi_google_web_searchfor Google organic results andrapidapi_google_image_searchfor Google Images. They validate inputs, unwrap the listing’s response envelope, and publish an exact per-page price. - Use
rapidapi_list_listings(free) when you do not know which listings or endpoints exist. It returns each listing’s host, documented endpoints, required inputs, and the typed tool for each endpoint. - Use
rapidapi_requestonly for an endpoint on a registered listing that has no typed tool yet. Pass the listinghost(or slug), thepath, andqueryorbody. Hosts that are not registered are rejected before any call because Deepline cannot price them; ask the Deepline team to register a listing you need. - Every call is billed per RapidAPI request. Paginated endpoints bill one request per page: start with
pages: 1and raise it only when you need more than about 20 results, because a largerpagesvalue re-bills the earlier pages. - An empty result set from a search listing is a completed search, not an error, and it is still billed. Do not retry it automatically.
billed_requestsin every result is the count the listing reported in itsX-RapidAPI-Billingheader. Deepline settles the call from that count; when the header is absent it charges the requested count.- Upstream 401 means the RapidAPI key is not subscribed to that listing. 404 and 410 come back as
ok: falsewith the upstream body so you can inspect them; 429 and 5xx stay loud so the shared retry policy applies. - Deepline paces calls to the smallest paid plan’s per-second limit across the provider (5 requests per second today); bursts wait briefly for a slot instead of receiving a synthetic 429.