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

​
Provider-specific requirements

Connect a customer-owned Crunchbase API key before using these tools. Deepline does not provide a managed key or bill for Crunchbase calls. Crunchbase applies the customer’s subscription access and quotas. Search for an entity to obtain its Crunchbase UUID or permalink, then use entity lookup for details. Request only the field_ids and card_ids needed by the workflow. Search and lookup coverage depends on the customer’s Crunchbase API package. A provider permission response may mean the key’s package does not include that endpoint or field. Source: Crunchbase API documentation and API package overview.

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