
Primavera status
Answered our latest tool-list check 22 hours ago with 20 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 1 of 1 checks
- Last seen working
- 16 Nov, 12:17 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 16 Nov, 12:17 | Answered | 1.7 s | 20 |
Tools (20)
Read from the server on 16 Nov 2026.
- get_account
- Plan, credit balance, Agency fair use per country and rate limits of the Primavera account that owns the API key. Call it first: it tells what the account can afford. Free. Same call as GET /api/v1/account of the REST API.
- find_areas
- Find an area from a place as written: region, département, commune, postal code, or a radius around a town ("Lyon", "33", "30 km around Nantes"). Use the "area" field of a result (or of "match" when its status is "resolved") as the area of suggest_categories or as search.area. Free. Same call as GET /api/v1/areas of the REST API.
- suggest_categories
- Entry point for ANY target: call it before any search, and never invent category ids. Give the target in plain words, WITHOUT the place ("independent car repair shops", "restaurants that could use an online booking tool") and the area from find_areas. Primavera's engine picks the Google Maps categories in groups and counts them in the area. Returns "selection" (groups, categories left out and why,
- find_categories
- Look up a single Google Maps category by name (French or English), with its number of places. To build a target, use suggest_categories instead; use this only to check or add one category id to search.categories.ids. Free. Same call as GET /api/v1/categories of the REST API.
- find_networks
- Look up a brand, franchise or network by name. Use its id in search.filters.networks ({ "mode": "only" | "exclude", "ids": [...] }); mode "exclude" without ids removes every known network (independent businesses only). Free. Same call as GET /api/v1/networks of the REST API.
- count_search
- Count the places of a search (the "search" returned by suggest_categories). Its input describes the search object in full (target, area, filters one by one, sort): read it to edit a search. Places already delivered to the account are left out unless search.excludeDelivered is false. When "exact" is false, say "≈ N". Free. Same call as POST /api/v1/search/count of the REST API.
- get_search_metrics
- The figures of a search in one call: total, places with an email address, a phone number, a website, and the estimated number of email addresses. Free. Same call as POST /api/v1/search/metrics of the REST API.
- preview_search
- Up to 25 sample places of a search (name, city, category, rating, reviews). Contact details are booleans here: email addresses, phone numbers and websites only come with a list (create_list). Free. Same call as POST /api/v1/search/preview of the REST API.
- estimate_list
- Rows, cost in credits and balance after, for a list of N rows of a search (up to 50,000). Tell the user the cost, then send "cost" as maxCredits to create_list with the same search, rows and withEmail. In a rarely searched area it returns kind "zone": the list fills itself after creation (create_list with maxCredits ≥ zoneEstimate.creditCap). Free. Same call as POST /api/v1/search/estimate of the
- create_list
- Export the places of a search into a new list, with their contact details (up to 50,000 rows). Price: 1 credit per place never delivered to this account (Agency: included under fair use); withEmail: only places with an email address (found ones first, then guessed and verified ones); verifyEmails: plus 1 credit per address verified. maxCredits is never exceeded: send the "cost" of estimate_list, o
- list_lists
- The lists of the account, newest first, page by page (send nextCursor back as cursor). Free. Same call as GET /api/v1/lists of the REST API.
- get_list
- Status of a list (creating, ready, filling, failed), rows, credits spent, progress of the export, of the guessed email addresses and of the email verification (progress.emailCheck.unverified = what verify_list_emails would cost), contents and latest jobs. While it is not ready, call it again every 10 seconds or more. Free. Same call as GET /api/v1/lists/{id} of the REST API.
- get_list_items
- Rows of a ready list with every contact detail, page by page (nextCursor). Keep limit small (50 or less) and choose columns: large pages flood the conversation. For the whole list, use prepare_list_file. Free. Same call as GET /api/v1/lists/{id}/items of the REST API.
- complete_list
- Add places to a list from its original search; places already in the list are skipped. Priced as an export: 1 credit per place never delivered to the account (Agency: included under fair use). Paid: maxCredits (the most credits this call may spend, never exceeded) and idempotencyKey (a new UUID v4 for this operation) are required; without them nothing runs. To retry after an error or a timeout, se
- prepare_list_file
- Prepare the CSV file (every column) or the Excel file (the columns you choose) of a ready list. Then call get_list_file until the file is ready. A file stays available 7 days. Free. idempotencyKey (a new UUID v4) is required; reuse it only to retry the very same call. Same call as POST /api/v1/lists/{id}/files of the REST API.
- get_list_file
- Status of a prepared file. Once it is ready, "url" is a download link valid 120 seconds: download it at once or give it to the user, and call again for a new link. Free. Same call as GET /api/v1/lists/{id}/files/{fileId} of the REST API.
- estimate_list_job
- Estimate a job on a list before starting it: places eligible and the most credits it can spend. Jobs: executives (company executives, France and the United States only), summary (a 3-sentence summary of each website), question (a yes/no question asked to each website), filter (a criterion judged on the data we hold, no website read). Free. Same call as POST /api/v1/lists/{id}/jobs/estimate of the
- start_list_job
- Start a job on a list; it runs in the background. Each place is billed on its result, never beyond maxCredits nor the estimate: send estimate.maxCredits of estimate_list_job, with the same tool, question, criterion and scope. Follow it with get_job; results land in get_list_items. Paid: maxCredits (the most credits this call may spend, never exceeded) and idempotencyKey (a new UUID v4 for this ope
- get_job
- Progress of a job: status, places done and billed, credits spent; for a finished filter or question job, the places per verdict. Free. Same call as GET /api/v1/jobs/{id} of the REST API.
- verify_list_emails
- Verify the email addresses of a ready list (deliverable, risky, undeliverable): 1 credit per address that gets a verdict; the credits of the others are returned. maxCredits is the number of addresses you accept to verify: send progress.emailCheck.unverified of get_list. Paid: maxCredits (the most credits this call may spend, never exceeded) and idempotencyKey (a new UUID v4 for this operation) are