# Animica Artifact Registry — Tamper-Evidence & Provenance Signing

> Animica Artifact Registry — Tamper-Evidence & Provenance Signing is a paid API for AI agents from animica.dev, paid per call via x402, $0.0018/call, status unknown (last checked 2026-09-15).

Records a cryptographic digest, version, and optional metadata for a named artifact (package, image, repo, or model) into a tamper-evident manifest, optionally anchored to Animica's data-availability store.

## Facts

- Endpoint: POST https://animica.dev/x402/pq/artifact
- Price: $0.0018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/animica-artifact-registry-tamper-evidence-provenance-signing-4d53dbeb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NbOj-6QkuZV9oh_-at8A9

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 animica-artifact-registry-tamper-evidence-provenance-signing-4d53dbeb -d '<json body>'
```

Example prompt: Register a tamper-evidence record on Animica for my Docker image 'ghcr.io/acme/api' version '2.1.0' with digest 'sha256:a3f9c2d1e8b047f6c5d4e3a2b1c9d0e7f6a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1' — anchor by digest and include my wallet as the publisher.

## When to prefer this

Choose this endpoint when you need cryptographic tamper-evidence for a software artifact, AI model, container image, or dataset release without uploading the artifact itself. It is ideal for supply-chain provenance, audit trails, and verifiable publish records. Prefer it over generic timestamping services when you need Animica's x402 pay-per-call model, optional on-chain payer binding, and integration with Animica's broader agent ecosystem.

## Known failure modes

- Missing required fields (name, digest, version) returns a 4xx validation error
- Unsupported hash algorithm (SHA-1, MD5) causes rejection
- Digest format doesn't match declared digest_alg — mismatch error
- DA store unavailable when require_anchor=true — raises an error rather than silently skipping anchor
- Metadata exceeds 8192 canonical characters — payload rejected
- Digest hex string malformed or length doesn't match expected algorithm output

## How this service works

Animica Python Cloud: deploy a Python function to animica.dev, get a public endpoint, and earn ANM every time someone runs it. Free AI (OpenAI-compatible, no key), free scheduled Workers, and an 80/20 developer split.

## Output

Returns a signed manifest containing the artifact name, digest, version, algorithm used, timestamp, optional anchor record reference, and optionally the payer identity bound as requested_by. The manifest serves as a tamper-evident attestation retrievable from Animica's data-availability store if anchoring was requested.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/animica-artifact-registry-tamper-evidence-provenance-signing-4d53dbeb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from animica.dev](https://www.zero.xyz/host/animica.dev/llms.txt)