What we can show, and what we cannot yet.
Every line below is marked. In code means the behaviour can be read in the source in the Caelara repository and is exercised by its automated tests. It does not by itself prove what is running in production. Design intent means we intend it or rely on it, but have not confirmed it from the source or from a deployed endpoint.
shield.caelaralabs.com. The chips below still say what is verified in code and what is not; a deployment is not a claim of certification or of independent audit.In the access gate.
These come from the Caelara API worker source that Shield is built beside, and the Shield worker carries the same gate. They describe the access gate and the upstream fetch helper.
X-Payment-Required header.ck_trial_ key allows 50 calls and expires after 14 days. Each call increments a counter stored with the key; at the limit the request falls through to x402 terms.console logging calls. This describes our code only; the hosting platform keeps its own operational metrics and logs, which this code does not control.In the Shield source.
Read from the Shield worker source and checked by its tests. Screening is heuristic: it will miss some attacks and flag some harmless text, and no findings is not proof of safety.
Cache-Control: no-store. Limits: with a full key, prompt and output text is sent to the Agent Safety checks, which are not cached. For transaction and proxy checks, the token, hash, address or hostname is sent as a lookup to other Caelara suites and the answer is cached for 2 to 5 minutes under a hashed key. The hosting platform keeps its own logs.shield.caelaralabs.com, caelaralabs.com and www.caelaralabs.com. Any other browser origin gets no allow header. This does not restrict agents or server-side clients, which are not subject to browser origin rules, and it is not an access control: every call still passes the three-way gate.coverage field that says which checks ran. With a trial key the other suites are not called, and the response says so.caelaralabs.com are refused. A fetched page that scores as an attack is withheld unless you ask for it.system_prompt for output checking, it goes to the local echo check for that one request. It is not included in the call to any other suite.coverage shows what was not checked. The endpoint is read-only: nothing is signed or sent.Design intent.
We intend or rely on these, and have not confirmed them from our own source or a deployed endpoint.
What we do not say.
Nothing here is claimed anywhere on this site.
- No latency or uptime figure for Shield. None has been measured for it.
- No third-party audit or compliance certification.
- No customer count or customer names.
- No detection-rate or accuracy figure. No benchmark has been run yet.
- The browser sandbox on the Shield page is a local demo in your tab, not the production engine.
Questions or a security report: [email protected].