> For the complete documentation index, see [llms.txt](https://docs.urbit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbit.org/urbit-os/kernel/behn/scry.md).

# Behn Scry Reference

Here are Behn's scry endpoints. There's only a few and they're mostly just useful for debugging. All of Behn's scries take a `%x` `$care` and require the `$desk` in the path prefix be empty, so the general format is `.^([type] %bx /=//=/[some-path])`.

## /debug/timers <a href="#debugtimers" id="debugtimers"></a>

A scry with a `%x` `$care` and a `$path` of `/debug/timers` will return the timestamp and `$duct` of all timers which are currently set. The type returned is a `(list [@da duct])`.

```
> .^((list [@da duct]) %bx /=//=/debug/timers)
~[
  [~2021.8.9..16.16.30..9d49 ~[/ames/pump/~wet/0 /ames]]
  [~2021.8.9..16.17.58..597d ~[/ames/pump/~nes/0 /ames]]
]
```

## /timers <a href="#timers" id="timers"></a>

A scry with a `%x` `$care` and a `$path` of `/timers` will return the timestamps of all timers currently set. The type returned is a `(list @da)`.

```
> .^((list @da) %bx /=//=/timers)
~[~2021.8.9..16.17.02..9de6 ~2021.8.9..16.17.58..597d]
```

## /timers/next <a href="#timersnext" id="timersnext"></a>

A scry with a `%x` `$care` and a `$path` of `/timers/next` will return the timestamp of the timer set to fire next, or null if there's none. The type returned is a `(unit @da)`.

```
> .^((unit @da) %bx /=//=/timers/next)
[~ ~2021.8.9..16.17.58..597d]
```

## /timers/\[da] <a href="#timersda" id="timersda"></a>

A scry with a `%x` `$care` and a `$path` of `/timers/[da]` (where `[da]` is an absolute date) will return all timers which are scheduled to fire between now and the specified date (inclusive). The type returned is a `(list @da)`.

```
> .^((list @da) %bx /=//=/timers/(scot %da (add now ~d1)))
~[~2021.8.9..16.17.58..597d ~2021.8.9..16.18.06..a24b]
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.urbit.org/urbit-os/kernel/behn/scry.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.