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

​
Provider-specific requirements

Use Limadata for real-time person enrichment, company enrichment, email/phone finding, identity resolution, web search, AI research, and URL extraction. Pricing is settled from Limadata’s x-credits-cost response header whenever present, except limadata_find_phone. Phone lookup settles at the documented 10 Limadata credits only when a phone number is returned. Static credit notes are used for pre-run estimates and fallback settlement for other actions. The current OpenAPI snapshot contains only synchronous POST endpoints. Watch/webhook APIs are not present in this snapshot and are not exposed by this provider registration.

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