Skip to content
Pine Computer Request access
Menu

Read: structure.

Ruby 
# In an existing backend session
computer.require_agent_protocol!
turn = session.agent.run(
  "Collect the invoices for review.",
  idempotency_key: saved_message_id
)
turn = session.agent.wait(turn_id: turn.turn_id)

Existing Computer, session and saved request ID required. Setup and turn handling

  1. Pine's agent reads structured web state where available, with visual input when the work needs it.

    pixelsstructure

Speed and cost

2–5×

faster1

~1/20

the model cost2

Selected long-horizon tasks in Pine's evaluations, compared with selected frontier-agent systems.

  1. 1. Pine's preliminary comparisons. Results vary by task and system.
  2. 2. Approximate model API cost ratio. Infrastructure and tools excluded.
  3. How we measured

What you can build

Build agents that work across software and return to the same computer.

All 26 use cases

Renew permits

Your customer clicks Renew once, and every permit due this quarter is renewed on its own city’s portal.

How it runs
Illustration of an example: in your customer’s property software, three permits are renewed at once, each on a computer of its own working its city’s portal. The portal for 9 Pier Road asks for a sign-in; your customer signs in on its screen and hands it back. Each city’s receipt comes back to its permit’s row as a PDF.

Build more.
Hand AI the work.

Pine Computer is invite-only while in beta.