animica.dev
https://animica.dev/x402/web/askShares a payout wallet with 88 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Give a URL and a question; get an answer grounded in that page, WITH the passages the answer was drawn from. We fetch the page, chunk it, embed the chunks and your question, retrieve the closest 4 passages and answer from those only. Nothing is stored — it is a one-shot pipeline, not an index. The retrieved passages come back with the answer so you can check it rather than trust it, and when nothing on the page is relevant the product says so instead of letting the model improvise.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
82.9% avgResponse time
p50 98ms · p95 1398msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 9/29/2026, 3:00:00 AM | 100% | 1 | 95ms |
| 9/29/2026, 4:00:00 AM | 100% | 1 | 2272ms |
| 9/29/2026, 6:00:00 AM | 100% | 1 | 93ms |
| 9/29/2026, 8:00:00 AM | 100% | 1 | 2692ms |
| 9/29/2026, 10:00:00 AM | 100% | 1 | 1301ms |
| 9/29/2026, 12:00:00 PM | 100% | 1 | 92ms |
| 9/29/2026, 2:00:00 PM | 100% | 1 | 102ms |
| 9/29/2026, 4:00:00 PM | 100% | 1 | 101ms |
| 9/29/2026, 6:00:00 PM | 100% | 1 | 101ms |
| 9/29/2026, 8:00:00 PM | 100% | 1 | 102ms |
| 9/29/2026, 10:00:00 PM | 100% | 1 | 101ms |
| 9/30/2026, 1:00:00 AM | 100% | 1 | 116ms |
| 9/30/2026, 3:00:00 AM | 100% | 1 | 111ms |
| 9/30/2026, 5:00:00 AM | 100% | 1 | 272ms |
| 9/30/2026, 7:00:00 AM | 100% | 1 | 103ms |
| 9/30/2026, 9:00:00 AM | 100% | 1 | 183ms |
| 9/30/2026, 11:00:00 AM | 100% | 1 | 89ms |
| 9/30/2026, 1:00:00 PM | 100% | 1 | 85ms |
| 9/30/2026, 3:00:00 PM | 100% | 1 | 84ms |
| 9/30/2026, 5:00:00 PM | 100% | 1 | 126ms |
| 9/30/2026, 7:00:00 PM | 100% | 1 | 84ms |
| 9/30/2026, 9:00:00 PM | 100% | 1 | 78ms |
| 9/30/2026, 11:00:00 PM | 100% | 1 | 77ms |
| 10/1/2026, 1:00:00 AM | 100% | 1 | 95ms |
| 10/1/2026, 3:00:00 AM | 100% | 1 | 86ms |
| 10/1/2026, 5:00:00 AM | 100% | 1 | 126ms |
| 10/1/2026, 7:00:00 AM | 100% | 1 | 96ms |
| 10/1/2026, 9:00:00 AM | 100% | 1 | 79ms |
| 10/1/2026, 11:00:00 AM | 100% | 1 | 99ms |
| 10/1/2026, 1:00:00 PM | 100% | 1 | 101ms |
| 10/1/2026, 3:00:00 PM | 100% | 1 | 86ms |
| 10/1/2026, 5:00:00 PM | 100% | 1 | 251ms |
| 10/1/2026, 7:00:00 PM | 100% | 1 | 94ms |
| 10/1/2026, 9:00:00 PM | 100% | 1 | 114ms |
| 10/1/2026, 11:00:00 PM | 100% | 1 | 114ms |
| 10/2/2026, 1:00:00 AM | 100% | 1 | 90ms |
| 10/2/2026, 3:00:00 AM | 100% | 1 | 93ms |
| 10/2/2026, 5:00:00 AM | 100% | 1 | 98ms |
| 10/2/2026, 7:00:00 AM | 100% | 1 | 113ms |
| 10/2/2026, 9:00:00 AM | 100% | 1 | 176ms |
| 10/2/2026, 11:00:00 AM | 100% | 1 | 109ms |
| 10/2/2026, 1:00:00 PM | 100% | 1 | 89ms |
| 10/2/2026, 3:00:00 PM | 100% | 1 | 140ms |
| 10/2/2026, 5:00:00 PM | 100% | 1 | 421ms |
| 10/2/2026, 7:00:00 PM | 100% | 1 | 91ms |
| 10/2/2026, 9:00:00 PM | 100% | 1 | 83ms |
| 10/2/2026, 11:00:00 PM | 100% | 1 | 73ms |
| 10/3/2026, 12:00:00 AM | 100% | 1 | 84ms |
| 10/3/2026, 1:00:00 AM | 100% | 1 | 80ms |
| 10/3/2026, 3:00:00 AM | 100% | 1 | 104ms |
| 10/3/2026, 5:00:00 AM | 100% | 1 | 80ms |
| 10/3/2026, 7:00:00 AM | 100% | 1 | 122ms |
| 10/3/2026, 9:00:00 AM | 100% | 1 | 70ms |
| 10/3/2026, 11:00:00 AM | 100% | 1 | 2727ms |
| 10/3/2026, 1:00:00 PM | 100% | 1 | 89ms |
| 10/3/2026, 3:00:00 PM | 100% | 1 | 93ms |
| 10/3/2026, 5:00:00 PM | 100% | 1 | 95ms |
| 10/3/2026, 7:00:00 PM | 100% | 1 | 124ms |
| 10/3/2026, 9:00:00 PM | 0% | 1 | — |
| 10/3/2026, 11:00:00 PM | 0% | 1 | — |
| 10/4/2026, 1:00:00 AM | 0% | 1 | — |
| 10/4/2026, 2:00:00 AM | 0% | 1 | — |
| 10/4/2026, 4:00:00 AM | 0% | 1 | — |
| 10/4/2026, 6:00:00 AM | 0% | 1 | — |
| 10/4/2026, 8:00:00 AM | 0% | 1 | — |
| 10/4/2026, 1:00:00 PM | 0% | 1 | — |
| 10/4/2026, 3:00:00 PM | 0% | 1 | — |
| 10/4/2026, 5:00:00 PM | 0% | 1 | — |
| 10/4/2026, 7:00:00 PM | 0% | 1 | — |
| 10/5/2026, 7:00:00 PM | 0% | 1 | — |
- Availability
- 97
- Latency
- 100
- Security
- 83
- Transparency
- 61
- Activity
- 1
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- animica:1, base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- Hosting Concepts B.V. d/b/a Registrar.eu
- Domain registered
- 2025-09-26
- Hosting network
- CONTA-48
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 9/30/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 9/7/2026 | 2 | 0.01 | 1 |
| 9/8/2026 | 6 | 0.01 | 2 |
| 9/9/2026 | 1 | 0 | 1 |
| 9/10/2026 | 1 | 0 | 1 |
| 9/11/2026 | 7 | 0.01 | 3 |
| 9/12/2026 | 3 | 0.01 | 2 |
| 9/13/2026 | 5 | 0.01 | 2 |
| 9/14/2026 | 3 | 0.01 | 3 |
| 9/15/2026 | 5 | 0.01 | 2 |
| 9/17/2026 | 1 | 0 | 1 |
| 9/22/2026 | 2 | 0 | 1 |
| 9/24/2026 | 1 | 0.01 | 1 |
| 9/25/2026 | 1 | 0.01 | 1 |
| 9/30/2026 | 1 | 0 | 1 |
This payout wallet is shared: figures cover all 89 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Response schema
{
"description": "product-specific JSON payload plus a payment block",
"type": "object"
}