condu.id Egress
A signed egress proxy for third-party AI agents. When an agent registered with condu.id fetches a page, the request leaves through condu.id Egress and carries a cryptographic signature, so you can tell who sent it and decide what to allow.
- Name
- condu.id Egress
- Operator
- condu.id
- Type
- Intermediary access: requests are made on behalf of agents run by our tenants, not by a crawler of our own
- User-Agent
- condu-egress/1.0 (+https://condu.id/bot)
- Signatures
- HTTP Message Signatures (RFC 9421), Ed25519, Web Bot Auth
- Contact
- ron@xproweb.com
How it behaves
- Every request names the originating tenant in a Forwarded header, so you can tell one tenant's agent from another's.
- It honors robots.txt, including Crawl-delay, for the condu-egress user agent.
- Each tenant has its own rate limit.
- Tenants that abuse the proxy are suspended.
- Content fetched through condu.id Egress is not used to train models.
Verifying a request
Signed requests carry Signature-Agent, Signature-Input and Signature headers. The keyid in Signature-Input is the RFC 8037 JWK thumbprint of one of the keys in our directory. Fetch the directory, find the key with that thumbprint, and check the signature against it. The directory response is itself signed by each key it lists.
curl -si https://condu.id/.well-known/http-message-signatures-directory
Blocking or reporting
To block condu.id Egress, disallow condu-egress in your robots.txt. To report abuse, email ron@xproweb.com with the time of the request and the tenant from its Forwarded header, and we will look into that tenant.