Skip to content
Pine Computer Request access
Menu

09 / 26 Research and reports · Example

Vet a company

The deal team’s memo shows where the seller’s files and the public record disagree, and cites both.

Who it’s for
Deal software whose users test a seller’s claims against what the company has filed.
Why it’s hard
The seller’s figures and the filings don’t always match, and the memo has to say where. The registry charges for older accounts, and spending the firm’s money is the deal lead’s call.
You get back
  • A diligence memo, as a Word document
  • The filings it read, saved as PDFs

The seller’s confidential files are opened on a computer sealed off for this target alone.

How it runs, in your product’s code

Pine’s AI reads the seller’s spreadsheets first, then the registry and the company’s own site. The 2022 accounts carry a fee, so the row turns to “Needs you: a fee” and the deal lead decides whether to buy them. The memo lists the disagreements in a section of their own.

Ruby · example
computer = pine.create_computer(  location: { country: "US" },  ephemeral: true)session = computer.create_session(name: "main", browser: true) session.agent.run(<<~JOB)  Research Halden Cold Storage from public sources and the  attached files. Write a diligence memo that cites every claim.JOB session.agent.events do |event|  case event.type  when "needs_input"    # Your user takes the controls on the live desktop in your    # product, does what only they can, and hands them back.    session.agent.answer(event.payload["request_id"], "Done.")  when "result"    session.list_artifacts(turn_id: event.turn_id).each do |file|      row.attach(file.filename, session.read_artifact(file.id))    end    break if event.terminal?  endend computer.stop

Build more.
Hand AI the work.

Pine Computer is invite-only while in beta.