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

​
Provider-specific requirements

  • Use prospeo_search_person or prospeo_search_company to build list-level candidates, then refine with prospeo_enrich_person and prospeo_enrich_company for details.
  • Use prospeo_search_person for prospecting — it supports stable filters (job title with boolean operators, department, seniority, industry, headcount, technology, location). Search is billed per page of 25 results.
  • Do not use Prospeo for job-change detection or job-change filtered searches. The live Prospeo job-change filter has schema drift. Use FullEnrich for job-change workflows.
  • Use prospeo_search_company to build account lists by firmographic criteria before drilling into individual contacts.
  • Use prospeo_enrich_person for profile fields such as title, company, and location. Mobile reveal uses enrich_mobile: true or only_verified_mobile: true. Its maximum estimate is 10 times the standard enrichment estimate. Play spend guards use that estimate before execution. Enable mobile reveal only when the requested workflow needs phone outreach.
  • Use prospeo_enrich_company for firmographic enrichment (industry, headcount, technologies, description) from a website, company name, or LinkedIn company URL.
Recommended workflow: prospeo_search_person or prospeo_search_company to build lists, then prospeo_enrich_person for individual contacts.

​
Mobile reveal pitfalls

  • For mobile outreach, explicitly send enrich_mobile: true. Add only_verified_mobile: true when only verified mobiles are acceptable. Forward supported identity fields already available, especially email or a personal LinkedIn URL.
  • A profile match and a revealed phone are separate results. A mobile status of VERIFIED does not make a masked number usable. Require revealed: true and an unmasked mobile value in person.mobile or data.person.mobile. A masked value with revealed: false indicates availability, not a number ready for outreach.
  • Inspect a small sample’s actual request payload and reveal fields before a bulk run. Zero revealed phones from requests without mobile reveal does not establish zero provider coverage.
  • Diagnose completed runs from their original request receipts. The current configuration may have been edited after execution. It does not prove the mobile flags were sent in the earlier run.

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