Skip to main content
Human guide: work with your agent → Inspect one RapidAPI action before starting provider-backed work. Your first result is a verified input and output contract.

​
Provider-specific requirements

Use RapidAPI when a registered listing covers the required data. Deepline uses a managed key for its subscribed listings. Each listing has separate plan limits. Only listings registered in Deepline are available.
  • Prefer the typed listing tools first: rapidapi_google_web_search for Google organic results and rapidapi_google_image_search for 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_request only for an endpoint on a registered listing that has no typed tool yet. Pass the listing host (or slug), the path, and query or body. 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.
  • Each page incurs request usage. Start with pages: 1. Increase it only when the workflow requires more results. A larger pages value retrieves and bills earlier pages again.
  • 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_requests in every result is the count the listing reported in its X-RapidAPI-Billing header. 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: false with 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.

​
Examples

​
Find an applicable action

Confirm your effective workspace, then search the live catalog:
Search returns candidates. Check the returned provider and operation rather than selecting a similar title automatically.

​
Inspect the selected contract

Replace <returned-tool-id> with the identifier returned by discovery:
These commands do not execute the selected provider action. Read its required inputs, supported access mode, pricing unit, outputs, and limits. A connection does not establish that every action supports BYOK. Follow the provider-specific requirements above and the live action contract.

​
Prepare one reviewed input

Use one authorized record that matches the inspected schema. Preserve its source identity and define the result you will accept. Open the action reference for its payload and response shape. Provider-backed execution can incur usage or external effects. For reusable logic, follow Write Plays. For direct-call recovery, use Tool execution recovery.
Continue only when the workspace, provider, required fields, acceptance rule, and applicable price are understood. Keep unavailable access separate from no-result evidence.