What the agent does
This is for a small general contractor or specialty subcontractor that wins much of its work through public bids: city parks, school roof replacements, county road drainage. Each owner posts its solicitations on its own website, a purchasing page or a bid portal, and an estimator checks a dozen of them by hand every week and still misses one. This run needs no sign-in to any app: the agent uses the browser in its own cloud computer to open the public pages listed in its input, and the session returns a file.
For each page in the list, the agent opens it, finds the list of open solicitations and reads each entry's title, number, owner, posting date and due date. It opens every entry posted since the last check to read the scope, the location, the estimated value when the owner publishes one, the pre-bid meeting date and whether it is mandatory, bonding requirements stated in the notice, and where the plans and specifications are posted. When a page needs a free account to see documents, it records that and the link rather than trying to register.
It scores each new solicitation against the contractor's own profile from the input: the trades it self-performs, the counties it works in, the size of job it bids, and the work it never takes. Each one is marked fits, maybe or does not fit, with the reason in one sentence that quotes the notice ("Scope: replacement of the built-up roofing at Lincoln Middle School"). Anything with a mandatory pre-bid meeting in the next 10 days goes to the top, because missing it rules the contractor out.
It writes bids.csv, one row per new solicitation with every field it read and the link, and bids.md, a one-page summary for the estimator: the fits first, by due date, then the maybes. It also lists any page it could not read, such as a site that was down or changed its layout, so a gap in coverage is visible.
Start it with one API call
POST https://api.phoenix.so/o/{org}/sessions with this body:
{
"agent": "claude",
"input": "Check these public bid pages for solicitations posted since 2026-11-07: https://www.example-city.gov/purchasing/bids, https://www.example-county.gov/procurement/open-solicitations, https://www.example-schools.org/business-office/bids. For each new one, open the notice and read: title, number, owner, posted date, due date and time, scope, location, estimated value if stated, pre-bid meeting date and whether mandatory, bonding stated, and where plans are posted. Our profile: general contractor, self-performs concrete, carpentry and roofing; works in Example and Harlan counties; bids jobs from $150,000 to $3,000,000; never bids road paving or HVAC-only work. Mark each fits, maybe or does_not_fit with a one-sentence reason quoting the notice. Write bids.csv (one row per solicitation) and bids.md (fits by due date, then maybes; mandatory pre-bid meetings within 10 days at the top; pages you could not read). Do not register for any account or submit anything."
}- Get an API key. In the console, open Settings, then API keys, and create a key for your org. Send it in the Authorization header as a Bearer token.
- Send the request. POST the body in request.json to https://api.phoenix.so/o/{org}/sessions, with your repository as the resources URL. The run starts in its own cloud sandbox.
- Read what came back. Follow the run on its live stream or wait for the run.completed webhook, then read the result and its trajectory.
What comes back
The session returns bids.csv and bids.md as artifacts, each with a download url, and the summary in result. The estimator reads bids.md on Monday morning, opens the notices marked fits, and decides which ones the company pursues. The agent bids on nothing, registers for nothing and contacts no owner.
What the estimator checks: the due date and time on the owner's own notice before planning around it, since a notice can be amended after the run read it; anything marked maybe, which usually means the scope mixes trades; and the list of pages the agent could not read. Every page it opened is in the transcript, so a missed solicitation can be traced to the page and what the agent saw there.
Run it on every Monday morning
In the console, a Project automation with a schedule trigger, cron 0 7 * * 1 in the contractor's timezone, runs a saved agent that holds the company profile and the list of bid pages in its instructions. The automation's prompt asks for solicitations posted in the last seven days, so the window moves with each run.
When the estimator adds a new owner to watch, it is one more URL in the saved agent's instructions, and the next Monday's run includes it. Each week's run is its own session, so the files from earlier weeks stay readable from the session list.
The use case this job follows, with its automation and trigger: Produce a report or file, no repo.
Why run it on Rush?
Each owner publishes bids its own way, as a table, a PDF list or a portal page with filters, and the layouts change without notice. A scraper written for each site breaks one at a time and silently. The agent reads each page the way the estimator would and lists the ones it could not read, so a broken site shows up as a line in the report instead of a missed bid.
The run has its own computer and browser, so nothing runs on the estimator's machine and no browser profile is shared. Each run keeps a record of every page it opened and what it read there, and the session lists what its model calls cost, which the company can compare with the hours an estimator spent checking the same pages.
Frequently asked questions
Can it download the plans and specifications?
It can download files a page offers publicly and attach them to the session, if the prompt asks. Many owners post plans through a plan room that needs an account, and this prompt tells the agent not to register, so it records the link instead.
Can it tell us whether we should bid?
It marks fit against the profile you give it and quotes the notice. Whether to bid, and at what price, is the estimator's decision.
What if a site blocks automated browsers?
The page is listed as one the agent could not read. For a site that needs the estimator's own signed-in browser, a run can name the estimator's linked Mac in devices and use its browser after they approve it.
How does it know what is new?
It compares each entry's posted date to the date in the prompt. An owner that does not show a posted date is listed with every open solicitation, marked so the estimator can skip ones already seen.
More Public websites jobs
More jobs like this: Produce a report or file, no repo
- Which Customer Quote Requests Have We Not Answered? A Wholesale Distributor's Morning Check of Each Sales Rep's Outlook (Outlook)
- Find Customer Questions Nobody Answered in Your Shared Slack Channels (Slack)
- Find Last Month's Uncategorized Expenses in QuickBooks Before the Close (QuickBooks)
- Flag Loads at Risk of Missing Delivery in a Freight Broker's Airtable (Airtable)