Voygr POI API

Return requested attributes for one place or a list of places. Standard attributes (opening_hours, phone, website, facebook, instagram, tiktok, email, existence, open_closed) cost one credit per place however many you request; any other attribute name is a research field, answered by a bounded research loop and charged per place per field. A request may mix both and pays for each. Send poi_name for one place and get the flat response; send pois for a list and get a rows-by-attributes matrix. include_summary=true also returns a short factual place_summary. Requires a key with the enrich or deep_research entitlement; either one may request any attribute, standard or custom. See [Research custom attributes](/docs/guides/research-custom-attributes/) for custom attributes. ### Verifying the name and address you sent When your records may be close but not exact - an abbreviation, an initialism, a store number, or a slightly stale spelling - three independent checks are available, one for each thing a record can get wrong: - `verify_name` settles what the business is actually called BEFORE researching anything else, and every attribute you asked for is then researched against the verified name. Each row carries `identity.name`. - `verify_address` checks the trading address AFTER research and never replaces it. Each row carries `address_checks.address`. - `verify_registered_address` checks the registered office. Each row carries `address_checks.registered_address`. `identity.name` gives the value we settled on, a verdict, and your original. The verdict is `confirmed` (yours was already right), `corrected` (we replaced it) or `unresolved` (we could not establish it, so your value comes back untouched). `value` is always what the rest of the row was researched against, so branch on the verdict rather than comparing strings. Formatting is not a correction: punctuation, casing, "and" vs "&" and a dropped or added Inc/Ltd/LLC all come back `confirmed` with your own string. `verify_name` and `verify_address` share one lookup, so either or both cost a flat 1 extra credit per row, independent of how many attributes you requested; `verify_registered_address` costs 1 more. Each can be overridden per place. `verify_identity` is deprecated. It means `verify_name` plus `verify_address`, costs the same 1, and additionally rewrites the address research runs against to the same premises written in full - never a different one - returning `identity.address` too. Use the separate flags in new integrations, so a place can decline either check on its own. This is not a postal validation - a `confirmed` address matches what the business publishes about itself, not a postal database - and it makes no claim about whether the business is still open. ### Owner discovery (`owner_person`, `owner_org`) Request these as ordinary field specs. `owner_person` is the individual owner, co-owners or franchisee; multiple owners are comma-separated in one string. `owner_org` is the parent organisation when no individual owner exists. They are mutually exclusive per place: when one is established, the other abstains. "no individual owner" is a legitimate answer. Results may be confirmed (high or medium confidence), estimated (low confidence, treat as a lead), or unconfirmed (value is null). Unavailable ownership is a normal result; do not interpret an abstention as a claim that no owner exists. Owner fields use the same billing rules as other fields on this endpoint.

Place an outbound AI phone call. Two request shapes - freeform (target_phone + brief) or structured (target_phone + intent + slots). See the guide above for the 422 slot-retry loop.