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

​
Provider-specific requirements

  • D&B Direct+ requires a customer consumer key and consumer secret. A Hoovers subscription alone does not prove Direct+ API access.
  • Company discovery: criteria search accepts domain, D-U-N-S numbers, registration numbers, SIC industries, employee ranges and location filters. Name lookup uses typeahead with a search term and country.
  • Company matching accepts D-U-N-S, or country plus a name, website, registration number, telephone, email or address. Matching returns candidates. match-quality information helps select the intended company. Extended match combines identity resolution and licensed Data Blocks in one request.
  • Data Blocks and versions must be licensed to the connected D&B account. Available content depends on that contract.
  • Deepline does not bill for D&B API usage. D&B can charge the customer account under its own contract.
  • Family tree returns corporate subsidiaries/branches with pagination. Beneficial ownership returns the licensed ownership list or structure, subject to country coverage.
  • Entitlements reports what the connected key can access. It does not grant or purchase access. Reference categories and codes decode D&B identifiers used in filters and results.
  • Batch, monitoring, the sketch Multi-Process endpoint, contact search, and historical audit are not exposed. Principal/contact information can be requested through licensed Data Blocks.

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