// Terms of Service · last updated 2026-07-31

What you can expect from us, and what you must not assume.

This is not a guarantee, and treating it as one is dangerous

Security tools fail. Ours fail in documented ways, and we publish those limits rather than hide them:

The content rules match shapes. They are evadable by rewriting the text, they are English-only, and they do not cover selection-capture attacks at all — the docs name the published proof-of-concept they miss. Detection is triage, not a verdict on safety.

The payment conformance check is arithmetic and does not have that weakness: either a payment matches its quote or it does not. But it can only compare what it is given. A wrong quote produces a wrong answer, an abstain is not an all-clear, and a payment path that does not route through the guard is not guarded.

You remain responsible for the payments your agent makes and the software it runs. Do not deploy an autonomous agent holding funds on the assumption that our tools make it safe. They reduce specific, named risks.

Using this website

Read it, quote it, link to it. Our research pages exist to be cited — attribution is appreciated and the underlying scripts are public so you can reproduce the numbers rather than take our word for them. Do not scrape it in a way that degrades service for anyone else.

The prose and diagrams on this site are ours. The code is Apache 2.0. Those are different things and the licence file is the authority for the second.

Using a hosted API from us

Not open to the public yet. When it is, these terms apply to it and this section will be expanded before anyone can send a request. In the meantime, the parts already settled:

An API key identifies your organisation and you are responsible for keeping it secret. A dashboard session is not an API key and cannot be used as one. Do not use the service to attack anyone, to test payloads against third parties without their consent, or to build a competing service by proxying ours.

We may rate-limit, suspend, or decline service to prevent abuse. If we suspend you and you think we are wrong, write to hello@agentwormhole.com — a human will read it.

Nothing here promises uptime. There is no SLA until there is a signed agreement that says otherwise, and any figure quoted in marketing copy is not one.

Security research and disclosure

Testing our tools is encouraged; that is what they are for. If you find a way past a control, tell us at hello@agentwormhole.com and we will fix it and credit you if you want the credit. We will not threaten you for reporting a vulnerability in good faith.

Our own published findings concern third-party protocols and are drawn entirely from public chain state and published packages. We do not withhold a disclosure to make a point, and we do not describe a mechanism as a loss when no loss occurred.

Warranty and liability

The software and this website are provided as is, without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. This mirrors sections 7 and 8 of the Apache 2.0 licence and does not narrow any right that licence gives you.

To the maximum extent permitted by law, we are not liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, lost funds, or lost data, arising from your use of the software or this site. Some jurisdictions do not allow these exclusions, and where that is so they do not apply to you.

Changes and contact

If these terms change materially, the date at the top changes. The site is open source, so the history of this file is public. Continuing to use a hosted service after a change means you accept the change; if you do not, stop using it and ask us to delete your data.

Reach a human at hello@agentwormhole.com.

Questions about this document: hello@agentwormhole.com· Agent Wormhole is an independent project. The software is licensed Apache 2.0 and its licence, not this page, governs your use of the code.