# Animica Signing Policy

> Animica Signing Policy is a paid API for AI agents from animica.dev, paid per call via x402, $0.0018/call, status unknown (last checked 2026-09-16).

Returns the live, usable signing schemes on the Animica L1 chain, flagging deprecated stubs and providing key/signature sizes and usability verdicts per scheme.

## Facts

- Endpoint: POST https://animica.dev/x402/chain/signing-policy
- Price: $0.0018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/animica-signing-policy-a82d017c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u3rnIBTtEEdmoufrs_o5N

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-signing-policy-a82d017c -d '<json body>'
```

Example prompt: Before I generate a wallet key for Animica, check which signing schemes on the chain are actually live and usable — I don't want to get stranded on a deprecated scheme like those 4098 wallets did.

## When to prefer this

Use this endpoint before generating any Animica wallet key or implementing a signer, to avoid being stranded on deprecated schemes. Prefer this over static documentation because it reflects the chain's live state, not historical policy. Essential when auditing why historical transactions verified but new ones are rejected (use include_disabled=true).

## Known failure modes

- Chain cannot be read — endpoint returns free error response indicating chain connectivity issue
- Invalid input schema — non-boolean value for include_disabled causes a 400-style error
- Payment not received — x402 payment of $0.006 USDC required; missing payment results in 402 challenge response
- Chain reports no schemes — empty scheme list returned if chain state is anomalous

## How this service works

Which Animica signature scheme you can actually build on. The chain reports three schemes enabled, but two are deprecated commitment stubs the node refuses to make keys for — and 4098 wallets are already stranded on one. Returns the live scheme list plus both id spaces (consensus schemeId and PQ algorithm id 0x1003), key and signature byte sizes, and a usable/not verdict per scheme with its evidence. Buy before generating a key or writing a signer. No model. Free when the chain cannot be read.

## Output

A structured list of signing schemes reported by the Animica chain, each with: consensus schemeId, PQ algorithm id (e.g. 0x1003), key byte size, signature byte size, enabled/disabled status, a usable/not verdict, and supporting evidence for the verdict. Deprecated commitment stubs are clearly flagged.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "include_disabled": {
   "type": "boolean",
   "description": "include schemes the chain reports as disabled (default false). Useful when auditing why a historical transaction verifies but a new one is refused."
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/animica-signing-policy-a82d017c/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)