Skip to main content
POST
Create a web monitor agent

Authorizations

Authorization
string
header
required

Your API token (af_…) as the Basic-auth username, with an empty password.

Body

application/json
listName
string
required

Name for BOTH the agent and the results list it creates. Must be unique across your agents: a name already in use is rejected with 409 LIST_NAME_TAKEN.

Minimum string length: 1
entityType
enum<string>
required

What the monitor should find: 'person' for people, 'company' for companies.

Available options:
person,
company
prompt
string
required

Plain-language description of the signal to watch for on the open web (e.g. 'companies fined by a regulator over late supplier payments'). Including the year — 'in 2026' — materially improves recency.

Required string length: 1 - 2000
start
boolean
default:false

true creates AND activates the agent (spends credits); false (default) saves a draft to activate later.

searchPeriod
enum<string>

How often the search re-runs — use one of exactly: 1h, 6h, 1d, 7d. Defaults to 1d.

Available options:
1h,
6h,
1d,
7d
numResults
integer

Web pages to read per run (1-100, defaults to 10). This caps PAGES, not results — one page can yield several matches.

Required range: 1 <= x <= 100
maxContacts
integer

Cap on the total number of results this agent delivers into its list. Omit for no cap.

maxCreditSpend
integer

Maximum credits this agent may spend in a single run or refresh (1000 to 200000); delivery-driven monitors stop once their total delivered results reach it. Omit for no limit.

Required range: 1000 <= x <= 200000
expirationDate
string | null

Date the agent stops running, as YYYY-MM-DD (for example "2026-12-31"), and in the future. Pass null to run until you pause or delete it; omit it for the default of one month from creation.

Response

Success

agent
object
required