---
title: "act: browse step"
description: "a `BrowseStepInput` to the step's result: the accessibility tree, the text, the markdown, a screenshot's hash, or a download set"
section: reference
address: /reference/act/browse_step
contract: 0476e35e6e275db5
---
# act: browse step
a `BrowseStepInput` to the step's result: the accessibility tree, the text, the markdown, a screenshot's hash, or a download set
[figure: The caller sends BrowseStepInput to /v1/act/browse_step. The platform returns a card whose body is BrowsingStep.]
POST/v1/act/browse_stepa task, 202
Drive a browsing step. The call needs the strategy rung under a token with the act grant, and it is served by either, by the size bound.
The route takes [BrowseStepInput](/concepts/browsestepinput) and returns a card whose body is [BrowsingStep](/concepts/browsingstep).
## Request body
The request body is [BrowseStepInput](/concepts/browsestepinput).
| field | type | required | note |
|---|---|---|---|
| `session` | `id` | yes | |
| `step` | [BrowsingStep](/concepts/browsingstep) | yes | |
## Response
The route returns a card whose body is [BrowsingStep](/concepts/browsingstep). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true. This route runs as a long step and returns a task with status 202. `POST /v1/work/status` returns the task's progress, and `POST /v1/work/cancel` stops the task.
## Headers
| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/, then /brand/, then /strategy/ |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |
A caller needs the strategy rung and a token with the act grant. The platform or the desktop app serves this route.
## Example
The example sends the smallest body that BrowseStepInput allows. The build validates it against the schema of BrowseStepInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/act/browse_step \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "session": "…", "step": { "kind": "navigate", "reach": "reads only", "hop": { "stage": "fetched", "host": "…", "at": "…", "job": "…", "trace_id": "…", "span_id": "…" } } }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.act.browse_step({
"session": "…",
"step": {
"kind": "navigate",
"reach": "reads only",
"hop": {
"stage": "fetched",
"host": "…",
"at": "…",
"job": "…",
"trace_id": "…",
"span_id": "…"
}
}
});
// answer.body is a BrowsingStep. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/browse_step",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"session": "…",
"step": {
"kind": "navigate",
"reach": "reads only",
"hop": {
"stage": "fetched",
"host": "…",
"at": "…",
"job": "…",
"trace_id": "…",
"span_id": "…"
}
}
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/browse_step")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&BrowseStepInput { /* the fields of the page */ }).send().await?.json().await?;
```