Last updated
FeasaBot
The reader Feasa sends to public code and permit pages.
What it is for
Feasa prepares feasibility and permit studies for people who want to build a home, an ADU or a lot split. Each study cites the code sections, fee schedules and permit instructions that apply to one property, so the person can comply with them. FeasaBot reads those public pages on that person’s behalf and keeps a dated copy of each as the study’s evidence.
How it identifies itself
- User-Agent:
Mozilla/5.0 (compatible; FeasaBot/1.0; +https://feasa.ai/bot) - Signed requests. Every request carries an HTTP message signature
(Web Bot Auth, RFC 9421) with
tag="web-bot-auth". The public key is athttps://feasa.ai/.well-known/http-message-signatures-directory. - It never presents itself as a person’s browser and never solves or works around a challenge page. A page it is not allowed to read is left for a person to read.
How it reads
- It reads
robots.txtbefore anything else on a site and follows it, includingCrawl-delay. If a site answers the request forrobots.txtwith a bot challenge or a server error, FeasaBot does not read that site. - It honours Content Signals. Its use is
ai-input: a page is given to a model that cites it back in one study. A site that setsai-input=nois not read. Nothing it reads is used to train a model. - One request at a time to a site, at least 2 seconds apart, and each page is read once and kept, not read again for every study.
- It only sends
GETrequests to public pages. It does not sign in, submit forms or read anything behind an account.
Blocking or contacting it
To stop FeasaBot reading your site, add User-agent: FeasaBot and
Disallow: / to your robots.txt. To ask a question or
report a problem, write to hello@feasa.ai.
Questions: hello@feasa.ai