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

​
Provider-specific requirements

Use Openmart for local-business and SMB workflows where store-level location data, brand records, shared company emails, known-person enrichment, employee discovery, or technology detection matter.
  • Prefer openmart_search_brands when the workflow needs one row per company/brand.
  • Prefer openmart_search_businesses when the workflow needs physical store records, ratings, categories, addresses, or location filters.
  • Use openmart_enrich_company when the input is a website or social profile and the goal is to resolve matching Openmart records.
  • Async launchers default to synchronous execution: they submit the batch, wait for completion, and return completed task results. Set wait_for_completion: false when the workflow only needs a batch_id.
  • For manually managed async jobs, poll openmart_get_batch_status, list completed IDs with openmart_get_batch_task_ids, then fetch each result with openmart_get_task_result.
  • Treat null arrays in brand responses as empty arrays.
  • Openmart docs require country on each /api/v2/brands/search location entry.
  • The configured provider token should be rotated if it has been pasted into chat, logs, or other plaintext surfaces.
Pricing note: search, enrichment, and technographics are billed per returned record, and phone lookups are the most expensive result type — bound limit when exploring. Openmart bills successful results only. failed calls and no-result calls are not billed. Deepline credit pricing for these actions is generated from the provider pricing metadata and rendered on the public provider pages.

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