# invinoveritas /witness — Third-Party Claim Anchoring

> invinoveritas /witness — Third-Party Claim Anchoring is a paid API for AI agents from api.babyblueviper.com, paid per call via x402, $0.0825/call, status unknown (last checked 2026-10-20).

Anchors a third party's claim byte-for-byte, unmodified, to a neutral record so two independent verifiers can later compose a joint artifact

## Facts

- Endpoint: POST https://api.babyblueviper.com/witness?utm_source=zero.xyz
- Price: $0.0825/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invinoveritas-witness-third-party-claim-anchoring-4cfbce00
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ftYFkCJCHueJRRuPiTOnU

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 invinoveritas-witness-third-party-claim-anchoring-4cfbce00 -d '<json body>'
```

Example prompt: Witness and anchor this claim byte-for-byte, attributed to 'Alice Corp': 'We agree to deliver 1000 units by March 31, 2025 at $4.50 each, no substitutions.' Don't judge or modify it — just lock it in so a second verifier and I can later compose a joint artifact.

## When to prefer this

Choose this endpoint when you need to anchor a third party's claim verbatim, without modification or judgment, specifically to support a two-verifier joint artifact workflow. It is distinct from self-attestation endpoints (which anchor your own claims) and from verification endpoints (which evaluate truth). Prefer it when the provenance of who made the claim matters (source field) and when you need a neutral, tamper-evident record that two independent parties can later co-sign or compose together — particularly before executing an irreversible action.

## Known failure modes

- Missing 'body' field returns validation error — the exact bytes to anchor are required
- 'source' field absent may result in an anonymous or rejected record depending on service policy
- Duplicate submissions of identical bytes may or may not be deduplicated — each call may create a new anchor
- Payment failure (x402) prevents anchoring from occurring
- Malformed UTF-8 or binary content in 'body' may cause rejection if the service expects valid string encoding

## How this service works

invinoveritas /witness — anchor a THIRD PARTY's claim byte-for-byte, unmodified and unjudged, so two independent verifiers can compose a joint artifact with

## Output

A witness receipt confirming the exact bytes of the submitted claim have been anchored, along with the self-declared source attribution and a timestamp. The record is neutral — the service makes no judgment about the claim's truth — and is designed so two independent verifiers can reference the same artifact for joint composition or dispute resolution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "The exact bytes to anchor, verbatim"
  },
  "source": {
   "type": "string",
   "description": "Who this claim is attributed to (self-declared, not cryptographically verified)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invinoveritas-witness-third-party-claim-anchoring-4cfbce00/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.babyblueviper.com](https://www.zero.xyz/host/api.babyblueviper.com/llms.txt)