# Witness Holoweave Signature Acceptance Check

> Witness Holoweave Signature Acceptance Check is a paid API for AI agents from witness.holoweave.org, paid per call via x402, $0.01/call, status down (last checked 2026-09-15).

Checks whether a signed HTTP request would be accepted by major bot-auth verifiers (Cloudflare, AWS WAF, Akamai, Vercel) according to the draft-meunier-web-bot-auth-architecture spec

## Facts

- Endpoint: POST https://witness.holoweave.org/v1/signature-acceptance
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/witness-holoweave-signature-acceptance-check-0196e7be
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fF4EDRgA_J_cF81E-9js-

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability witness-holoweave-signature-acceptance-check-0196e7be -d '<json body>'
```

Example prompt: Check whether my signed request to https://api.example.com/data — using these headers including Signature-Input and Signature — would be accepted by Cloudflare's bot-auth verifier according to the draft-meunier spec; my JWKS is at https://myagent.example.com/.well-known/jwks.json.

## When to prefer this

Use this endpoint when you need to pre-flight check whether an agent's signed HTTP request will be accepted by specific deployed WAF/bot-auth verifiers before actually sending it. It is purpose-built for the draft-meunier-web-bot-auth-architecture spec and tests against real verifier rule sets (especially Cloudflare). Prefer this over generic signature validators when you specifically need per-verifier acceptance decisions, not just cryptographic correctness — for that, use the sibling RFC 9421 signature verification endpoint instead.

## Known failure modes

- Missing required headers (Signature-Input, Signature) returns validation error
- Invalid JWKS URI or unreachable key directory causes key lookup failure
- Unsupported verifier name returns error or unknown verdict
- Malformed request_sample object causes schema validation rejection
- Network issues reaching verifier endpoints may return partial results

## How this service works

Web bot auth debugging for AI agents, priced per check at $0.01. RFC 7638 keyid thumbprint verification, RFC 9421 Ed25519 signature verification, and per-verifier acceptance rules. Signed attestations, published fixtures, sources with dates.

## Output

A per-verifier acceptance verdict indicating whether the signed request would pass bot-auth checks on each requested platform (Cloudflare, AWS WAF, Akamai, Vercel). Cloudflare provides form-level rule detail; others return 'unknown' if rules aren't published. Includes overall compliance status against the draft-meunier-web-bot-auth-architecture spec.

## Response schema (JSON Schema)

```json
{
 "example": {
  "signature": {
   "alg": "ed25519",
   "value": "base64...",
   "key_id": "aw-attest-2026-08"
  },
  "attestation": {
   "verdict": "fail",
   "endpoint": "signature-acceptance",
   "evidence": {
    "acceptance": {
     "aws-waf": {
      "result": "unknown",
      "reason_code": "FORM_RULES_UNSTATED"
     },
     "cloudflare": {
      "result": "reject",
      "reason_code": "CF_SIG_AGENT_DICTIONARY_FORM"
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/witness-holoweave-signature-acceptance-check-0196e7be/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from witness.holoweave.org](https://www.zero.xyz/host/witness.holoweave.org/llms.txt)