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

​
Provider-specific requirements

  • Use builtwith_domain_lookup when you already know the domain and need live/current technographics. The handler defaults live_only to true. set live_only=false only when historical detections matter.
  • Use builtwith_vector_search to discover the exact BuiltWith technology label before builtwith_lists or builtwith_trends. Free-text tech guesses often miss if the BuiltWith canonical name differs.
  • Use builtwith_bulk_domain_lookup for row-heavy domain work. It auto-polls queued jobs by default and normalizes both sync and async paths to the same results[] shape.
  • The batch compiler only coalesces builtwith_domain_lookup calls when the request can be losslessly represented by the native bulk API. Requests using trust, no_attr, or date-range filters stay single-call.
  • builtwith_lists is best for account sourcing by technology. builtwith_relationships, builtwith_redirects, and builtwith_tag_lookup are better for niche infrastructure signals and related-domain expansion.

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