public

Turn any material into a plan of searches

Changed on Oct 22, 2026

Read what someone sells and who they want to reach, from their own words, the text of documents or pages, or page addresses read by the server, and answer with a plan of people searches: what was said and what was inferred, the segments with their kinds of company, places and job titles, the searches a run would send and what they cost. While something blocking is missing the answer carries up to five questions and no searches; call again with plan_id and the answers. Free: nothing is searched, charged or saved. In a conversation the plan is that conversation's own, and a later call changes it.

post/public/plan-searches

Request

Base URL: https://api.bereach.ai
URL: https://api.bereach.ai/public/plan-searches
Auth: HTTP bearer

Request body

contextstring

Everything known about who the user sells to and who they want to reach, as written: their own words, the text of their documents or pages, their answers to earlier questions. Pass texts whole, not summarised.

urlsstring[]

Pages the server reads itself: the user's own website, a page about their offer or their customers. Only addresses the user gave or a tool returned.

plan_idstring

The plan_id of the plan this call answers or changes, as it was returned.

Response

Questions to ask, a ready plan, or nothing to search

Changes

Oct 22, 2026549f4adbbfcf Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
Oct 22, 2026bdaed6984b20 Revision changes
- warning
  removed the optional property / from the response with the status

Operation history (5 revisions)