What agents look for
The index is not prepared in advance for every question. It grows where agents ask and find nothing. This board shows those gaps, so that the router knows what to fill first and the owner of a site sees that someone is looking for it.
Reading the board from /v1/demand…
Niches
| What | Where | Clients | Sites now | Candidates |
|---|
Values nobody declares
| Axis | Value | Clients |
|---|
What is counted, and what is not
- Counted: a value of the vocabulary that a query asked for and no site declares, and the pair of what and where of a query nothing passed. With the day and an alias of the client that changes every day.
- Not counted: the words of the user, the address of the client, the other parts of the query, the results. A query with
"record_demand": falseis not counted at all. - Shown here: only what several different clients asked for; topics about health and private life need more. Records are kept no longer than 90 days.
How a gap gets filled
The router describes candidate sites from their own pages, checks them, and grows a niche
along the links of the sites it has seeded. An agent that found sites another way may report
them, but only after its user agreed: the ALP skill
asks first and sends nothing without a yes. The owner of a site can take its place at full
weight by publishing /.well-known/alp.json; the router writes one
from the site's pages.