Skip to main content

​
Prerequisites

  • Webcompute CLI installed and available as web.
  • A saved Webcompute API key from web login <key>.
  • A model profile from web model setup, or one-off model flags from model setup.
  • A successful first web agent run from the CLI quickstart, so browser, auth, and model setup are already working.
After the quickstart, run a browser-agent task that resembles product work: search a public site, open detail pages, and return specific fields.

​
Run the task

web agent \
  --url https://www.grants.gov/search-grants \
  --allow-domain grants.gov \
  "Search active Grants.gov opportunities for cybersecurity workforce. Return the first 5 opportunities with title, agency, opportunity number, close date, detail URL, and a one-sentence fit summary. Do not apply, log in, or submit forms."
The task includes the site, the search phrase, the result count, the fields to return, and the safety boundary.

​
Expected result

Cybersecurity workforce opportunities

1. Title: ...
   Agency: ...
   Opportunity number: ...
   Close date: ...
   URL: https://www.grants.gov/search-results-detail/...
   Fit: ...
Live public sites change. Treat the output as current browsing evidence, not as a static fixture.

​
Return JSON

web agent \
  --json \
  --url https://www.grants.gov/search-grants \
  --allow-domain grants.gov \
  "Search active Grants.gov opportunities for cybersecurity workforce. Return the first 5 opportunities with title, agency, opportunity number, close date, detail URL, and a one-sentence fit summary. Do not apply, log in, or submit forms."
Use --schema ./opportunities.schema.json when your downstream code needs validated fields.

​
If the site blocks progress

The agent should return the blocker state and the evidence it can see. Do not ask it to solve a CAPTCHA, submit forms, or invent data. To inspect a run, repeat the task with --debug-url and open the signed Debug UI URL only in a trusted context.

​
Build from here