> For the complete documentation index, see [llms.txt](https://asteroid-shiba.gitbook.io/asteroid-shiba-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asteroid-shiba.gitbook.io/asteroid-shiba-docs/core-gameplay/signals-hunting.md).

# Signals & Hunting

## Signals

A **signal** is one attempt to scan the field. Every player gets **5 signals per day**, free — no passes, no paid tiers. Everyone hunts on the same footing.

Signals refresh daily, so there's always a reason to come back.

## The hunt

Spend a signal and your Shiba scans the void. One of two things happens:

* **Empty** — most scans find nothing. Space is mostly empty rock. This is normal, even at high Scanner levels.
* **A find** — the scan lights up and reveals an asteroid with a rarity. See [Discovery & Reveal](/asteroid-shiba-docs/core-gameplay/reveal.md).

## Why most scans are empty (and that's the point)

Valuable asteroids are genuinely scarce — only a limited number exist each season. That scarcity is what makes a find feel like *striking gold*, not collecting a daily bonus. Your **Scanner** tilts the odds in your favor over time, and your [**Explorer Network bonus**](/asteroid-shiba-docs/referral-and-explorer-network/explorer-bonus.md) nudges them further — but the thrill of the hunt is always real.

**Next:** [Discovery & Reveal →](/asteroid-shiba-docs/core-gameplay/reveal.md)


---

# 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://asteroid-shiba.gitbook.io/asteroid-shiba-docs/core-gameplay/signals-hunting.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.