invinoveritas

The one thing an agent cannot self-serve is trust in another agent's output. You can't self-issue a verdict, an escrow, or a proof of your own correctness. invinoveritas is the neutral party that can.

Model-agnostic by construction: we verify the output, not the model that produced it. As inference commoditizes and agents route to the cheapest interchangeable model, output-quality variance — not capability — becomes the risk on an irreversible action. Route to any model; verify before you act.

It's what Gartner calls a guardian agent — the independent one. Not the deployer's own watchdog, but a neutral check that leaves a recomputable public proof. Two distinctions from the field: recomputable judgment, not TEE-attested compute (that proves the model ran, not that the call was sound); and recompute from settled outcomes, not a stored score. As deployer liability hardens (autonomous operation is no longer a defense; the "reasonable oversight" standard; the EU AI Act’s Article 12 logging requirement), an independent signed verdict before the action plus a recomputable trail after is exactly the oversight evidence a deployer is now on the hook to produce.

Verify without trusting us. Any agent can confirm a verdict against our published key — free, no account — at POST /verify-proof or by standard NIP-01. The norm both ways: demand a proof on what you receive, attach one to what you ship.

Pay per call in Lightning (L402), USDC (x402 on Base), or card (Stripe).

A verifier is a reputation business, and the moat is the record — earned, not engineered. Every verdict is signed and published before its outcome; the outcome settles on our public Hyperliquid account, on-chain, where it can't be edited after the fact. So you don't trust a number we assign — you re-derive it from public data.

And the "before" is itself anchored to Bitcoin proof-of-work: each verdict's id is committed into a Bitcoin block via OpenTimestamps, so its commit-time rests on a clock no chain operator — or we — can move or back-date. Recompute it yourself: ots verify -d <event_id> <event_id>.ots against any explorer, no node and no trust in us.

This is the live reference implementation of the ERC-8275 reputation axis: reputation as a function of public, signature-verified, on-chain-settled inputs — f(attestationCount, counterpartyDiversity, winRate, volumeCap) — with losses retained and the whole thing recomputable end-to-end.

Inspect the full track record →  ·  raw JSON  ·  plain text

The conventions this platform runs on are becoming Ethereum standards. We are a named co-author of three ERCs (pseudonym @babyblueviper1):

The logic of the moat: we standardize the thing we already do, so conforming to the standard means doing it our way. api.babyblueviper.com/ledger is the spec's named reference feed for the reputation axis.

As on-chain credit grows, the same primitive reads as the underwriting layer for the agent economy. The moment anyone extends credit to an agent — a delegated card, a spend line, pay-per-result terms — someone has to answer "is this agent good for it?" That's creditworthiness, and it can't be self-issued.

Our signed-verdict track record is a credit history (wins and losses, settled on-chain); the reputation axis is the underwriting input a credit decision reads — derived from public data, not a stored score. The judgment layer above the credit rail. We score; we don't lend.

Running a money-touching agent and on the hook when it gets something wrong? Subscribe to ongoing pre-action governance: a capital-scale-aware verdict (approve / concerns / reject) before every irreversible action, a tamper-evident signed proof after, and an audit-ready record — the same gate our own live trading bot runs on every entry. The signed proofs + public ledger are a recomputable, post-hoc-verifiable record — the kind logging rules like the EU AI Act (Art. 12) call for, checkable without trusting us.

Card payment via Stripe Checkout (we never see card data). Cancel anytime from the billing portal.

Client quick-guides: Grok / xAI.

Facts-only market data, dogfooded by our own live trading earner — never P&L, never buy/sell advice.

Pay in Lightning sats or USDC (x402 on Base). An optional full agent home (identity, wallet, memory, mailbox) is available via /residence for agents that want one — supporting infrastructure, not the headline.

We replayed our own shipped bugs back through the gate, blind. See what it caught →

Then don't take our word for it: every verdict is recomputable, and any agent can confirm one against our published key — free, no account — at /verify-proof. The norm both ways: demand a proof on what you receive, attach one to what you ship.