# Baby Blue Viper — invinoveritas Execution Proof

> Baby Blue Viper — invinoveritas Execution Proof is a paid API for AI agents from api.babyblueviper.com, paid per call via x402, $0.181831/call, status unknown (last checked 2026-09-14).

Generates a cryptographic proof (Nostr or HMAC signature) for a previously executed agent action, providing an auditable attestation of execution.

## Facts

- Endpoint: POST https://api.babyblueviper.com/prove
- Price: $0.181831/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/baby-blue-viper-invinoveritas-execution-proof-37424068
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YlrG4G8tpuNXKs5KLi_f3

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 baby-blue-viper-invinoveritas-execution-proof-37424068 -d '<json body>'
```

Example prompt: Generate a cryptographic proof for my agent execution with action_id 'exec_abc123' and publish it to Nostr so there's a verifiable on-chain record of what happened.

## When to prefer this

Use this endpoint when an AI agent needs to produce a cryptographically verifiable, auditable attestation that a specific action was executed — especially in trustless or multi-agent coordination contexts where proof of execution must be shared on Nostr or verified by other parties. Prefer over generic logging when a tamper-evident, signed record is required.

## Known failure modes

- Invalid or unknown action_id returns an error — the action must exist in the system before it can be proved
- Payment failure via Lightning/L402/x402 results in 402 response before proof is generated
- Nostr publish failure may succeed locally but fail to broadcast the Nostr event
- Expired or already-proved action_id may return a conflict or not-found error

## How this service works

A neutral verdict before an irreversible action, a signed proof after, and a public track record of being right you recompute — not a score you trust. The verdict is provably committed before the outcome it's graded against: no TEE, no trusted scorer.

## Output

Returns a proof object containing the invinoveritas.proof.v1 schema identifier, the original action_id, and a signature_type field indicating either 'nostr' or 'hmac'. Status field confirms success. If nostr_publish was true, the proof is also broadcast as a Nostr event.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "action_id": {
   "type": "string",
   "description": "Execution audit action_id to prove"
  },
  "nostr_publish": {
   "type": "boolean"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "proof": {
   "schema": "invinoveritas.proof.v1",
   "action_id": "exec_…",
   "signature_type": "nostr|hmac"
  },
  "status": "success"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/baby-blue-viper-invinoveritas-execution-proof-37424068/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)