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

Provider-specific requirements

Use Fundable for startup discovery, venture funding rounds, investor portfolios, founders, and saved funding alerts.

Choose the endpoint

  • Use fundable_discover_companies to find companies by company attributes, latest-round details, or investor participation.
  • Use fundable_search_deals when the target is funding rounds across company histories. Use the latest_deal filters on company discovery when only the newest round matters.
  • Use fundable_search_companies, fundable_search_investors_by_name, or fundable_search_people_by_name when resolving a name or uncertain identifier. Supply exactly one search input.
  • Use fundable_get_company, fundable_get_investor, or fundable_get_person for a known entity. Prefer a domain or profile URL when available.
  • Use the corresponding *_deals action for full funding history or investor activity.
  • Use fundable_unlock_person_email or fundable_unlock_person_phone only when a verified contact is explicitly needed. New unlocks consume Fundable credits. A repeated unlock on the same account is free.
  • Resolve readable location or industry names with fundable_search_locations or fundable_search_industries before using permalink filters.
  • fundable_get_alerts requires alert IDs and a start/end date. fundable_get_alert_configurations lists the authenticated account’s saved alerts.
  • Email and phone unlocks are available on non-trial Pro, Enterprise, and API plans. Alert reads are available on Pro+ and Enterprise plans. alert reads are free.

Authentication and pricing

Every operation uses a Fundable API key in a Bearer token. Fundable’s API docs describe 200 free starting credits and pay-as-you-go credits from $0.05 per credit. Deepline settles paid calls from the exact meta.credits_used value returned by Fundable. that provider billing metadata is removed from the customer-visible response. API documentation: https://docs.tryfundable.ai/ Pricing and credits: https://docs.tryfundable.ai/usage

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.