Nox's browser — a guide for website owners

#What is Nox's browser?

Nox is an autonomous AI agent. Each person on nox.cool has their own Nox (and can add more agents), and each agent has its own computer in the cloud with a real Chrome browser. When the person gives it a task, it does the work in that browser: it reads pages, clicks, fills in forms and asks the person before anything important — before it buys, sends or signs anything.

That makes it different from the bots website owners usually see:

• It works for one person at a time. Every visit is part of a task a signed-in person asked for.
• It opens what the task needs, one page at a time — the pace of someone clicking through, not thousands of pages a minute.
• It isn't building an index, and nox.cool doesn't train AI models on the pages its agents read.
• It never solves CAPTCHAs. When a site asks it to prove it's human, the person does that step themselves, on the agent's screen.

#How do I recognise a request from Nox?

Every request from the browser's tabs carries a signature, following the Web Bot Auth proposal: an HTTP Message Signature made with an Ed25519 key. You'll see three headers:

Signature-Agent: "https://nox.cool"
Signature-Input: sig1=("@authority" "signature-agent");created=…;expires=…;keyid="…";alg="ed25519";nonce="…";tag="web-bot-auth"
Signature: sig1=:…:

• The signature covers your site's host name and the Signature-Agent header, and it's good for 60 seconds.
• The public keys are at https://nox.cool/.well-known/http-message-signatures-directory — a key directory that is itself signed. Look the keyid up there and check the signature.
• A request that verifies came from a nox.cool agent. One that only says it's Nox, without a valid signature, didn't.

Two things to know:

• Don't rely on the user agent. It's the ordinary user agent of the Chrome version the computer runs, so it looks like any Chrome browser. The signature is what identifies Nox.
• A few requests go unsigned: what runs inside another site's frame embedded in your page, and service workers. A page's own requests, its scripts and its calls to other sites are all signed.

#Which address does Nox browse from?

Nox's browsers reach the web from:

• 35.239.114.111

They don't use IPv6. We'll update this page before that changes.

One exception, chosen by the person: they can tell Nox to open particular sites through their own Mac and home internet — usually a site that won't load from the cloud. Those requests come from the person's own address, and they still carry the nox.cool signature.

#How do I let Nox in?

If your site blocks automated traffic, allow requests whose signature verifies against the key directory above. Bot-management services that support Web Bot Auth can check the signature for you. Allowing the address above works too, but the signature is the stronger test: it can't be borrowed by someone else on the same network.

#How do I keep Nox out?

Refuse requests that carry a valid nox.cool signature. Nox then tells the person your site turned it away; it doesn't disguise itself or switch identities to get around a block, and its requests stay signed whichever way they travel. Blocking the address also works for traffic from the cloud, but not for the sites a person chose to open through their own Mac — the signature catches both.

#Questions, or something wrong?

Write to info@nox.cool with your site's address and what you'd like. If Nox did something on your site you didn't expect, tell us what and when, and we'll look into it.

#Questions and answers

Is Nox a web crawler?

No. Nox works for one signed-in person at a time, on a task that person gave it, and opens only the pages that task needs, one at a time. It doesn't build a search index, and nox.cool doesn't train AI models on the pages its agents read.

How can I check that a request really came from Nox?

Every request from its browser carries an HTTP Message Signature (RFC 9421, Ed25519) with the header Signature-Agent set to "https://nox.cool". Check the signature against the public keys at https://nox.cool/.well-known/http-message-signatures-directory. A request that claims to be Nox without a valid signature didn't come from nox.cool.

Which IP address does Nox browse from?

Nox's browsers reach the web from 35.239.114.111 (IPv4; they don't use IPv6). When a person chooses to open a site through their own Mac, that request comes from their home internet instead — and still carries the signature.

Does Nox follow robots.txt?

Nox isn't a crawler, so it doesn't read robots.txt — like a person's own browser, it opens what the person asked about. To keep it out, refuse requests that carry a valid nox.cool signature.

Does Nox solve CAPTCHAs or get around blocks?

No. Nox never tries to solve a CAPTCHA; the person does that step themselves. If your site turns it away, it tells the person. Its requests stay signed whichever way they travel, so a block on the signature holds.

Who do I contact about Nox on my site?

Write to info@nox.cool. Tell us your site's address and what you'd like; a person on the nox.cool team reads every message.