Kinya (勤哉)

Crawler identity

KinyaBot

KinyaBot is the web crawler operated by Kinya. It visits a site for one of two reasons: a Kinya customer owns it or has asked Kinya to analyse it, or Kinya is testing the crawler itself against real public pages that the site’s robots rules leave open to crawlers.

At a glance

User-Agent
KinyaBot/1.0 (+https://www.kinya.ai/bot)
robots.txt token
KinyaBot
Operated by
Kinya
Contact
[email protected]
Machine-readable
/bot/identity.json

Why it visits

Two reasons KinyaBot requests a page

  • Analysis for a Kinya customer

    A Kinya customer owns the site, or has authorized Kinya to analyse it. KinyaBot collects the page source and technical SEO evidence Kinya needs to set that site up, then revisits it so the analysis stays current as the site changes.

  • Testing the crawler itself

    Kinya also runs the crawler against real public pages to check its own quality: that it reads real-world markup correctly, works across different server setups, and keeps its request rate reasonable. These runs are bounded, and limited to public paths that the site’s applicable robots.txt rules do not block for KinyaBot or for crawlers generally.

Either way it reads the same things: it requests pages over HTTP and reads the source your server returns, together with the response status and headers. It reads your robots.txt first and applies it to the crawling those rules cover.

How it behaves

What KinyaBot commits to on every crawl

  • It reads robots.txt first

    KinyaBot fetches your robots.txt before it crawls, matches rules against the product token KinyaBot, and follows the rules that apply to it.

  • It keeps requests bounded

    A crawl runs to a bounded number of requests. KinyaBot does not take as much of your server as it can get.

  • It backs off when your server says so

    A 429 or 503 response, a Retry-After header, a challenge page, or a sign that the origin is under strain makes KinyaBot slow down or stop.

  • It never works around a block

    KinyaBot does not attempt to evade blocks or challenges. If you shut it out, it stays out.

Control it

Control KinyaBot from your robots.txt

Add one of these groups to the robots.txt at the root of your domain. KinyaBot matches the token KinyaBot, case-insensitively, and the token never changes between versions.

  • Allow KinyaBot everywhere

    # Allow KinyaBot everywhere
User-agent: KinyaBot
Allow: /

  • Block KinyaBot entirely

    # Block KinyaBot entirely
User-agent: KinyaBot
Disallow: /

  • Keep KinyaBot out of one area

    # Allow KinyaBot, except these paths
User-agent: KinyaBot
Disallow: /cart/
Disallow: /search
Allow: /
  • If your robots.txt has no KinyaBot group, KinyaBot applies the rules under User-agent: *. Site owners often assume the opposite.
  • A change applies from the next time KinyaBot reads your robots.txt.
  • robots.txt is a crawl control, not a grant of permission, and the two uses above draw their authority from different places. Analysis for a customer is authorized by the Kinya customer who owns the site or asked Kinya to analyse it. Kinya’s own crawler testing has no customer behind it: it uses public paths that the applicable robots rules do not block for KinyaBot or for crawlers generally.
  • In both cases KinyaBot obeys every disallowed path, backs off on signals that an origin is under strain, and never evades a block or a challenge.

What is not published

Absent on purpose, so this page stays accurate

None of the following exists yet, so none of it is published here. A placeholder would be worse than the gap: it is the kind of detail a firewall rule gets written against.

  • No IP addresses or ranges. KinyaBot has no dedicated egress addresses to publish, so any list here would be wrong.
  • No reverse-DNS check and no signed requests. There is no cryptographic way to verify a KinyaBot request today.
  • No verified-bot listing. Kinya has not registered KinyaBot with any CDN, host, or security vendor programme.
  • No pause control inside the Kinya product. Today the controls are your robots.txt and the mailbox below.

So treat the User-Agent above as a claim rather than proof — anything can send a string. If you need to know whether traffic you are seeing is really KinyaBot, send the details below. When a verifiable identity exists, this page is where it will be published.

Tell Kinya about a crawl

Email [email protected] to have KinyaBot allowed, blocked, or kept out of part of a site you run — or to report a crawl that caused a problem.

What to include

  • The hostname affected.
  • Roughly when the requests arrived, and the time zone.
  • A request ID, or the matching log lines, if you have them.
  • What you want to happen: KinyaBot allowed, blocked, or limited to part of the site.

Please do not send credentials, private content, or raw logs containing personal data. The matching lines are enough.

Email [email protected]

Published 21 August 2026. This page is the address inside KinyaBot’s User-Agent header, so it will not move.