jinba trail
Browser tasks, as typed endpoints

Record a browser task once.
Ship it as an API.

Demonstrate the task in a real browser. Jinba Trail captures it as a deterministic Recording, publishes it behind a typed HTTP endpoint, and replays it on every call — no scraping scripts, no headless babysitting, no model in the hot path.

Start buildingTry the playground
POST/v1/run/get-order-statusLive
request
curl -X POST https://api.jinba.trail/v1/run/get-order-status \
  -H "Authorization: Bearer bf_live_••••3f9a" \
  -H "Content-Type: application/json" \
  -d '{ "orderId": "NW-100423" }'
200 OK~2.0s · replayed, no model
response
{
  "run_id": "run_8f21c4",
  "status": "succeeded",
  "output": {
    "status": "In transit",
    "carrier": "Northwind Freight",
    "eta": "2026-07-02"
  }
}
01

Record

Describe the task. An agent drives a real browser and captures every step — navigate, fill, extract — as a typed Recording.

02

Publish

One click compiles the Recording into a FlowSpec, deploys it, and pins a live digest. Your inputs become a typed JSON schema.

03

Call

POST with a bearer key. The plane replays the Recording deterministically — no model in the hot path — and returns JSON in seconds.