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

​
Provider-specific requirements

PitchBook actions use only the workspace’s own PitchBook API key. The key needs an API contract with access to the requested endpoint and sufficient PitchBook credits. PitchBook charges that account. Deepline does not bill for these calls. Start with a search action to obtain a PitchBook pbId, then use the matching entity action for details. Bulk POST actions retrieve multiple records and also spend PitchBook credits. Check the customer’s contract before using endpoints outside their licensed areas. A 402 response means insufficient PitchBook credits. A 403 can mean the endpoint is not licensed.

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