# Rubric Protocol Tiered AI Decision Attestation

> Rubric Protocol Tiered AI Decision Attestation is a paid API for AI agents from rubric-protocol.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Creates a post-quantum-signed (ML-DSA-65) attestation of an AI decision anchored to the Hedera mainnet HCS topic ledger

## Facts

- Endpoint: POST https://rubric-protocol.com/v1/x402/tiered-attest
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rubric-protocol-tiered-ai-decision-attestation-be318588
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JMW4DHPIVQwQYY7LuK3Dc

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 rubric-protocol-tiered-ai-decision-attestation-be318588 -d '<json body>'
```

Example prompt: Create a post-quantum-signed attestation on Hedera mainnet for this AI decision — the model recommended approving loan application #LN-84821 — and give me a public verification URL I can share with auditors.

## When to prefer this

Choose this endpoint when you need a quantum-resistant, blockchain-anchored proof of an AI decision — specifically when auditability, regulatory compliance, or tamper-evidence is required and you want the Hedera Consensus Service as the public ledger. Prefer this over generic signing services when ML-DSA-65 (NIST post-quantum standard) signatures and a free public verifyUrl for third-party auditors are necessary.

## Known failure modes

- Payment not received or insufficient — paid returns false and attestation is not created
- HCS transaction fails to settle — settled returns false, attestationId may still be returned but anchoring is unconfirmed
- Invalid or malformed AI decision payload — 400 error before signing occurs
- Hedera mainnet congestion causing delayed settlement confirmation
- x402 payment protocol handshake failure — request rejected before processing begins

## How this service works

One post-quantum-signed AI decision attestation, anchored to Hedera mainnet HCS.

## Output

Returns an attestationId, the Hedera HCS topic ID the record was anchored to, a public verifyUrl for free third-party verification, the ML-DSA-65 algorithm used, and boolean flags confirming payment was received (paid), the HCS transaction settled (settled), and the overall operation succeeded (success).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "Arbitrary JSON content to be attested. Hashed and ML-DSA-65 signed; payment metadata is embedded in the attestation payload."
  },
  "agentId": {
   "type": "string",
   "description": "Identifier of the calling agent (optional; defaults to x402-agent)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "paid": "boolean",
 "topic": "string",
 "settled": "boolean",
 "success": "boolean",
 "algorithm": "ML-DSA-65",
 "verifyUrl": "string — free public verification",
 "attestationId": "string"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rubric-protocol-tiered-ai-decision-attestation-be318588/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rubric-protocol.com](https://www.zero.xyz/host/rubric-protocol.com/llms.txt)