# MimirAPI Provenance Certificate

> MimirAPI Provenance Certificate is a paid API for AI agents from mimirapi.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-11).

Issues a chain-of-custody license certificate binding a SHA-256 content hash to an issuer, subject, and license terms under an HMAC-SHA-256 signature.

## Facts

- Endpoint: POST https://mimirapi.com/v1/provenance/certificate?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mimirapi-provenance-certificate-7c4c98eb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0an3HyNQDOVelDM4LM6VD

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 mimirapi-provenance-certificate-7c4c98eb -d '<json body>'
```

Example prompt: Issue a provenance certificate for the image with SHA-256 hash 'a3f1c9...', licensed under Creative Commons BY 4.0, with the subject set to 'alice@example.com' — I need a signed receipt I can carry to prove what I licensed and on what terms.

## When to prefer this

Choose this endpoint when you need a cryptographically signed, portable, auditable license receipt binding a specific digital asset (identified by its SHA-256 hash) to a named subject and license terms — especially in agentic workflows where an AI agent must carry proof of what it licensed and from whom. Prefer it over simple logging or database writes when you need issuer-verifiable integrity and portability of the certificate across systems.

## Known failure modes

- Invalid or malformed SHA-256 hex in contentHash — certificate rejected
- Missing required fields (license, subject, or contentHash) — 400 bad request
- Payment not settled via x402 protocol — 402 payment required
- HMAC signing failure on issuer side — 500 internal error
- Content hash format not conforming to hex encoding — validation error

## How this service works

Chain-of-custody license certificate for any digital asset: a SHA-256 content hash bound to issuer, subject, and license terms under an HMAC-SHA-256 signature. Deterministic, portable, and verifiable through the issuer while the current HMAC v1 profile is active — a receipt an agent can carry to record what it licensed, from whom, and on what terms.

## Output

A structured license certificate containing the SHA-256 content hash, issuer identity, subject, license terms, and an HMAC-SHA-256 signature over those fields — serving as a portable, verifiable chain-of-custody receipt that can be presented to the issuer for verification while the HMAC v1 profile is active.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "license": {
   "type": "string"
  },
  "subject": {
   "type": "string"
  },
  "contentHash": {
   "type": "string",
   "description": "SHA-256 hex of the asset"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mimirapi-provenance-certificate-7c4c98eb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mimirapi.com](https://www.zero.xyz/host/mimirapi.com/llms.txt)