Skip to main content
ClaudeWave

Find out why your web bot auth signature is being rejected — RFC 9421 signature base, RFC 7638 keyid thumbprint, and what published verifier rules say. $0.01 per call, x402.

SubagentsOfficial Registry0 stars0 forksJavaScriptNOASSERTIONUpdated today
ClaudeWave Trust Score
80/100
Trusted
Passed
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Flags
  • !Licence file present but not machine-readable
Last scanned: 8/28/2026
Install as a Claude Code subagent
Method: Clone
Terminal
git clone https://github.com/ninefiveonefive/web-bot-auth-check && cp web-bot-auth-check/*.md ~/.claude/agents/
1. Clone the repository and copy the agent .md definitions into ~/.claude/agents (or .claude/agents inside a project).
2. Start a new Claude Code session to load the agents.
3. Delegate work to them with the Task/Agent tool or by name.
Use cases

Subagents overview

# web-bot-auth-check

Find out why your web bot auth signature is being rejected.

Signed attestations, paid per call over [x402](https://x402.org) on Base.

Part of **autobus**, which is where the rest of these live — one face per
product, each carrying everything its buyer needs.

This repository is the buyer's side: how to call the service, and how to verify
what it gave you. It carries no dependencies and nothing here phones home.

**Live at `https://witness.holoweave.org`.** No account, no key, no signup. Call the
endpoint, get a 402 with a quote, pay, get a signed attestation.

## What it answers

### `POST /v1/wba-thumbprint` — $0.01

Web bot auth keyid verification for AI agents. Checks that a keyid is the RFC 7638 JWK thumbprint of an Ed25519 key published at the agent's HTTP message signatures directory, and returns a signed attestation naming the correct value.

Anchored to **RFC 7638 JWK Thumbprint, with RFC 8037 Appendix A.3 for Ed25519** (RFC 7638), read 2026-08-23.

### `POST /v1/wba-signature` — $0.01

Web bot auth signature verification for AI agents. Verifies an RFC 9421 HTTP message signature against the Ed25519 key published at the agent's key directory, and returns a signed attestation naming the component that failed.

Anchored to **RFC 9421 HTTP Message Signatures** (RFC 9421), read 2026-08-23.

### `POST /v1/signature-acceptance` — $0.01

Web bot auth acceptance check for AI agents. Verifies a signed request end to end — key directory, RFC 7638 keyid thumbprint, RFC 9421 Ed25519 signature — and returns a signed attestation naming which verifiers' published rules it breaks.

Anchored to **draft-meunier-web-bot-auth-architecture** (-05), read 2026-08-23.

### `POST /v1/wba-self` — $0.01

Web bot auth standing check for AI agents, on the request that arrives: sign this call the way your agent signs every request and receive a signed attestation covering your key directory, the keyid against the RFC 7638 thumbprint of a key published there, the RFC 9421 Ed25519 signature verified against that key, and which named verifiers' published rules the request breaks. Nothing to paste, nothing stored; call it from your own schedule.

Anchored to **draft-meunier-web-bot-auth-architecture** (-05), read 2026-08-23.

## Evidence, never conclusions

An attestation says what is true of the artifact you sent, against a named
specification, at a stated time. It never says you are compliant, valid or
approved — those are conclusions, and they are yours to draw.

A finding looks like *"keyid matches the kid of key 0 but NOT its RFC 7638
thumbprint"*. It does not look like *"your setup is wrong"*.

## Calling it

```
POST https://witness.holoweave.org/v1/wba-thumbprint
Content-Type: application/json

{
  "key_directory": "https://signer.example/.well-known/http-message-signatures-directory",
  "keyid": "poqkLGiymh_W0uP6PZFw-dvez3QJT5SolqXBCW38r0U"
}
```

Unpaid, that returns **402** with a `PAYMENT-REQUIRED` header carrying the
quote: scheme `exact`, network `eip155:8453` (base-mainnet), the amount
in atomic units, and the asset. Pay with an x402 client and repeat the call with
the `PAYMENT-SIGNATURE` header. See [`examples/call.mjs`](examples/call.mjs)
for the whole flow in one dependency-free file.

A `GET` returns the same 402, so a crawler can read the price without buying
anything.

## Verifying what you were given

Every attestation is signed Ed25519 over the RFC 8785 canonical form of the
attestation object alone — the signature block is not part of what is signed.

```
node verify.mjs attestation.json
```

[`verify.mjs`](verify.mjs) has no dependencies and does not call us. The public
key is in [`key.json`](key.json) and is also served live at
`https://witness.holoweave.org/v1/key`.

[`examples/attestation.json`](examples/attestation.json) is a real one, bought
on mainnet for a cent. Verify it before you trust anything else here.

## Fixtures

[`fixtures.json`](fixtures.json) is the published fixture suite: inputs and the
exact findings they must produce. If a fixture stops matching, our judgment
moved, and you can tell without asking us.

## Idempotence

The same input digest is served from cache and **not charged twice**. Asking the
same question again is free; asking a different one is a different question.

---

Operated from Austria as a Kleinunternehmen. Imprint and privacy notice at
`https://witness.holoweave.org/impressum.html` and `/datenschutz.html`.
ai-agentshttp-message-signaturesrfc7638rfc9421web-bot-authx402

What people ask about web-bot-auth-check

What is ninefiveonefive/web-bot-auth-check?

+

ninefiveonefive/web-bot-auth-check is subagents for the Claude AI ecosystem. Find out why your web bot auth signature is being rejected — RFC 9421 signature base, RFC 7638 keyid thumbprint, and what published verifier rules say. $0.01 per call, x402. It has 0 GitHub stars and its last recorded update is dated 2026-08-27.

How do I install web-bot-auth-check?

+

You can install web-bot-auth-check by cloning the repository (https://github.com/ninefiveonefive/web-bot-auth-check) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is ninefiveonefive/web-bot-auth-check safe to use?

+

Our security agent has analyzed ninefiveonefive/web-bot-auth-check and assigned a Trust Score of 80/100 (tier: Trusted). See the full breakdown of passed checks and flags on this page.

Who maintains ninefiveonefive/web-bot-auth-check?

+

ninefiveonefive/web-bot-auth-check is maintained by ninefiveonefive. The last recorded GitHub activity is dated 2026-08-27, with 0 open issues.

Are there alternatives to web-bot-auth-check?

+

Yes. On ClaudeWave you can browse similar subagents at /categories/agents, sorted by popularity or recent activity.

Deploy web-bot-auth-check to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: ninefiveonefive/web-bot-auth-check
[![Featured on ClaudeWave](https://claudewave.com/api/badge/ninefiveonefive-web-bot-auth-check)](https://claudewave.com/repo/ninefiveonefive-web-bot-auth-check)
<a href="https://claudewave.com/repo/ninefiveonefive-web-bot-auth-check"><img src="https://claudewave.com/api/badge/ninefiveonefive-web-bot-auth-check" alt="Featured on ClaudeWave: ninefiveonefive/web-bot-auth-check" width="320" height="64" /></a>

More Subagents

web-bot-auth-check alternatives