animica.dev

Shares a payout wallet with 70 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.

Bind a build to its identity with a post-quantum signature: POST {name, version, digest} and get an ML-DSA-65 manifest (FIPS 204, alg 4099/0x1003 — the current Animica L1 signature scheme) committing that name+version+digest+timestamp. Buy it after building, training or repackaging something you may later have to prove you published — an image, a wheel, a model checkpoint — or before installing one, so two attestations claiming one name+version with different digests visibly contradict. That question is not answerable from a bare digest signature, which is why this is a separate product from /x402/pq/sign. The manifest also records the Animica chain head read just before signing — or, if the node could not be reached, records that absence and its reason, inside the signature either way, so a missing pin can never be mistaken for one that was never asked for. That pin is the part nobody can move: a block hash cannot be known before its block exists, so the manifest was signed at or AFTER that height, a bound we cannot inflate and anyone can re-check on any Animica node. Nothing is written to the chain. The artifact bytes never leave your side: you send the digest your pipeline already computed (sha256:… , 0x… or bare hex; sha256/sha512/sha3/blake2b/blake3 — SHA-1 and MD5 are refused with a reason, since a collidable digest identifies no single artifact). Optional anchor: the manifest digest is committed as a record in the node data-availability store (da.put), which returns a commitment plus a Merkle inclusion proof against it. Read that for what it is — a node-local, operator-run store, NOT a block: no blob written there is committed by consensus (the live chain's headers carry an all-zero daRoot), and the store evicts (lru) and can be deleted, so the record buys retrievability and tamper-evidence, never a trustless timestamp. anchor:"digest" (default) records only hashes and timestamps, anchor:"identity" also records name and version for a public release registry, anchor:false writes nothing — and your metadata is never anchored under any setting. Anchoring is operator-gated and off unless enabled here, so the default response may carry anchored:false for that reason alone; either way you get the real machine reason and never a commitment field that reads like a proof. Set require_anchor:true and an unwritable store becomes a 503 with nothing charged instead. Verification is FREE (POST /x402/pq/artifact/verify — it also re-reads the anchor and confirms it binds the manifest) and the signing public key is FREE (GET /x402/pq/artifact/pubkey), so anyone can check an attestation offline without paying us. No model is involved anywhere: every field is your input returned unchanged, a value the signer returned, or a value our node returned.