Who operates this service, how to reach a human, what you are charged, and what happens when something goes wrong.
Email is the contact channel of record for billing, refunds, security reports and legal notice.
Animica operates a set of pay-per-call HTTP endpoints under animica.dev/x402, priced individually and settled per request. There is no subscription, no account, and no stored balance. The authoritative, machine-readable list of endpoints and their current prices is the catalog itself:
Prices shown on this page or in documentation are informational; the price quoted in the 402 response for your specific request is the price you pay, and no more than that amount can be taken against that request.
Requests are paid with the x402 protocol. An unpaid request returns HTTP 402 carrying the exact terms: amount, asset, recipient and network. You authorize that specific amount by signing an EIP-3009 transfer authorization; the transfer settles on Base (chain id 8453) in USDC. Animica sponsors the gas for that settlement.
Settlement is performed by a facilitator operated by Animica itself. No third-party payment processor receives your request or your authorization.
Because each call is settled individually and delivered immediately, a successfully delivered response is not refundable. Two situations are:
If settlement succeeds and the underlying service then fails, the endpoint answers HTTP 502 with error: "paid_service_failed", an incident_id, and a cryptographically signed receipt referencing the settled payment. Send that receipt and incident id to ai@3vdc.com and the payment will be refunded to the paying address. Keep the receipt — it is the evidence, and it is signed by us so we cannot dispute it.
If you believe you were charged more than the quoted terms, or charged twice for one authorization, contact us with the settlement transaction hash. Every settlement is a public on-chain transfer on Base and can be verified independently by both of us.
Paid requests are pseudonymous: we do not ask for a name, an email address or an account.
For each payment we retain the paying blockchain address, the amount, the asset and network, the endpoint paid for, timestamps, the settlement transaction hash, and the signed authorization. This is what makes replay prevention, refunds and accounting possible, and it cannot be deleted on request without also destroying your own refund evidence.
Our web server records request lines in the ordinary way — IP address, timestamp, method, path, status, user agent — for operations, abuse prevention and rate limiting.
The public statistics endpoint is aggregate only. It carries no payer addresses, no transaction hashes and no per-payment rows.
Note that a blockchain settlement is public by design: the transfer from your address to ours is visible to anyone on Base, independently of anything we publish.
Do not use these endpoints to break the law, to attack the service or its upstreams, or to resell a response in a way that misrepresents what it is — in particular, do not present a software-CSPRNG randomness draw as hardware or quantum randomness. We may decline service or rate-limit any client, and the free discovery surfaces stay available so an automated client can always re-read the terms.
Report vulnerabilities to ai@3vdc.com. Please do not open a public issue for a security problem. Good-faith reports are welcome and will not be pursued legally.