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

​
Provider-specific requirements

Use GetLeads for B2B contact search and enrichment, company colleagues and decision-makers, and funding or acquisition signals.

​
Choose the endpoint

  • Use getleads_count_contacts to estimate a contact search before calling getleads_search_contacts. Counts and dataset metadata lookups are free in the provider API.
  • Use getleads_search_contacts for filtered prospect lists. Request only the columns needed, and keep pages small because Deepline charges 1.625 credits per successfully returned contact at the standard $0.10 per credit rate. GetLeads may separately apply its own account credit rules.
  • Use getleads_lookup_colleagues or getleads_lookup_decision_makers when you already know a company domain or LinkedIn company URL. Deepline charges 1.625 credits for each contact returned.
  • Use getleads_lookup_phone or getleads_batch_phone_lookup when phone numbers are the lookup key. Deepline charges 1.625 credits for each successfully matched contact.
  • Use getleads_enrich_from_linkedin, getleads_enrich_from_email, or getleads_enrich_from_person for contact enrichment. Deepline charges 1.625 credits for each successful enrichment result.
  • Use getleads_get_filter_values and getleads_get_available_columns to discover accepted filter values and field names. getleads_get_contacts_health checks dataset availability.
  • Use getleads_list_funding_signals and getleads_list_acquisition_signals for company event research. Deepline charges 1.625 credits per returned signal.

​
Authentication and provider billing

Every operation uses your GetLeads API key in the X-API-Key header. Count and metadata reads are free through Deepline. Billable result operations cost 1.625 Deepline credits per successful contact or signal. Your connected GetLeads account can have separate plan and credit rules. Inspect the live action contract before execution. The catalog disables provider-managed exports, CSV uploads, deprecated batch aliases, follower orders, profile monitoring, and provider balance or usage endpoints. Manage those operations in GetLeads. Deepline results do not include provider balances or internal usage totals. API reference: https://app.getleads.io/openapi.json Website: https://www.getleads.io/

​
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.