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

​
Provider-specific requirements

Use Bloomberry when the user needs account-level B2B technographic signals or hiring signals. Prefer:
  • bloomberry_get_company_tech_stack when you already know a company domain and need the vendors it currently uses.
  • bloomberry_get_tech_stack_changes when the user needs recent adoption, churn, or usage signals. Provide exactly one of category or vendor_name.
  • bloomberry_get_current_customers when building a list of companies currently using a vendor or category. Provide exactly one of category or vendor_name.
  • bloomberry_list_vendors before vendor-filtered searches when the exact vendor/category name is uncertain.
  • bloomberry_search_job_postings for hiring intent. Provide at least one of keyword, normalized_job_titles, or domain.
Use limit conservatively on result-list endpoints because Bloomberry charges credits per returned signal, customer, or job posting.

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