Eery’s web agent
For website owners: what Eery does on your site, how it identifies itself with Web Bot Auth, and how you can welcome, limit or block it.
At a glance
- Name: Eery
- Operator: PrAx Digital Solutions Erhan Kesbic Felix Miehe GbR, Frankfurt am Main, Germany
- Type: AI assistant acting for individual users (intermediary signed agent)
- Identification: Web Bot Auth – HTTP Message Signatures (RFC 9421) with an Ed25519 key
- Key directory: https://eery-ai.com/.well-known/http-message-signatures-directory
- Contact: info@prax-ds.com
What Eery does on the web
Eery is a personal AI assistant. People talk to it in the Eery app, by email or in their messengers, and Eery gets things done for them. Some of those tasks need the web: looking up opening hours, comparing offers, checking a timetable, filling in a form, or buying something the person has approved.
For these tasks Eery uses a real browser on its own servers in Frankfurt. It loads pages, scripts and images just like a person’s browser does, reads what it needs and acts within the limits the person has set. Every visit starts with one person’s request; Eery does not wander the web on its own.
Eery is built and operated by a small team in Frankfurt. If you run a website and want to know more, see the questions below or write to us.
How Eery identifies itself
Eery identifies itself with Web Bot Auth, the open standard for signed agents based on HTTP Message Signatures (RFC 9421). A signed request carries three headers:
- Signature-Agent – the address of our key directory:
"https://eery-ai.com/.well-known/http-message-signatures-directory" - Signature-Input – the signed parts of the request (method, host, path, query, Signature-Agent and, for requests with a body, Content-Digest), with
tag="web-bot-auth",alg="ed25519", a key id, a fresh nonce and a lifetime of at most five minutes - Signature – the Ed25519 signature over those parts
The key directory is served as application/http-message-signatures-directory+json. The response itself is signed by every key it lists (tag http-message-signatures-directory), so nobody can copy our directory and pass themselves off as Eery. The private keys never leave our control centre; the browsers that do the work ask it for each signature.
To check a request yourself: read the key id from Signature-Input, fetch the directory, take the key with that id and verify the signature over the listed components. Reject it if the time window has passed or the nonce was already used.
Rules Eery follows
Eery does:
- visit pages only to fulfil a request from one person;
- load pages at the pace of a single person browsing;
- ask the person before every purchase, unless they gave a standing permission with their own spending limit;
- follow the rules in your A2W policy file where you publish one;
- keep a log of every action, which the person can read.
Eery does not:
- crawl, index or archive websites;
- use website content to train AI models;
- solve CAPTCHAs itself – the person does that;
- create accounts, sign in or pay without the person’s consent;
- resell or share what it read with other users.
Questions from website owners
Is Eery a crawler?
No. Eery does not crawl, index or archive websites, and it does not follow links on its own. Every visit starts with one person asking Eery to do something – for example “find a train to Munich on Friday” or “reorder my coffee beans”. Eery then opens the pages it needs for that task, much like the person would in their own browser.
Does Eery use my content to train AI models?
No. What Eery reads on your site is used only to answer the person who asked or to finish their task. It is not used to train AI models, not sold and not shared with other users.
Which access type is Eery – direct or intermediary?
Intermediary. PrAx Digital Solutions runs the software, but each action is started by a different end user. Requests from Eery therefore belong to many different people, each acting for themselves.
Does Eery sign every request today?
Not yet. Today Eery signs every request to websites that welcome agents through an A2W policy file at /.well-known/a2w. We are extending signing to more websites step by step. Where a request is signed, the signature is always genuine and always points to the key directory on this domain.
Can Eery buy things or submit forms on my site?
Only when the person has asked for it. Purchases need the person’s approval in the Eery app, either for that single purchase or through a standing permission with a spending limit they set themselves. Eery never creates accounts, signs in or pays without the person’s consent, and it never solves CAPTCHAs itself – if your site shows one, the person solves it.
How fast does Eery load pages?
At the pace of one person using a browser. Eery works on one task at a time per user and opens only the pages that task needs. It does not run parallel bulk downloads.
How do I block or limit Eery?
If your site is behind Cloudflare, you can allow, challenge or block signed agents (including Eery) in your security rules. On any other setup, you can match the Signature-Agent header and verify the signature against our key directory. If something Eery did on your site caused a problem, write to us – a person reads every message and we answer quickly.
How do I welcome agents and set rules for them?
Publish an A2W policy file at /.well-known/a2w on your site. In it you say whether agents are welcome and which actions they may take – for example checkout up to a certain amount. Eery reads that file, identifies itself on your site and follows your rules.
Contact
Questions, a problem with traffic from Eery, or a wish to be treated differently? Write to info@prax-ds.com – in English or German. Please include your domain and, if you can, the time and path of the requests. A person reads every message.
Operator: PrAx Digital Solutions Erhan Kesbic Felix Miehe GbR
Seckbacher Landstraße 74
60389 Frankfurt am Main
Deutschland
All details about the provider are in the legal notice (Impressum). For general help with Eery, see Help and contact.