Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-05 · today

agents.allium.so/api/v1/explorer/queries/run-async

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://agents.allium.so/api/v1/explorer/queries/run-async
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xac70a61f4039639d25e7a103de2c92f2335bae76
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)16 / 5

2.Probe history

2026-08-142026-10-05
Figure 1. Probe timeline, last 11 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-05 10:30 UTCPOSTfail402705 msmetadata_mismatchDeclared payTo 0xac70…ae76 on eip155:8453; the 402 offered 0x44a5…4535 on eip155:8453, EmbDaQ…u2TQ on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0x61Fd…Cada on eip155:196, 0xF5B5…68CA on eip155:137.
2026-09-29 10:30 UTCPOSTfail402823 msmetadata_mismatchDeclared payTo 0xf9de…be0a on eip155:8453; the 402 offered 0x1853…d1e3 on eip155:8453, Akpe8P…D2Rf on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0x61Fd…Cada on eip155:196, 0xF5B5…68CA on eip155:137.
2026-09-29 07:38 UTCPOSTfail402783 msmetadata_mismatchDeclared payTo 0xf9de…be0a on eip155:8453; the 402 offered 0x5124…0d1e on eip155:8453, 34Fbz4…RuYk on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0x61Fd…Cada on eip155:196, 0xF5B5…68CA on eip155:137.
2026-09-26 10:30 UTCPOSTfail4022943 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 11:24 UTCPOSTfail402694 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 16:19 UTCPOSTfail4021274 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 11:24 UTCPOSTfail402940 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-11 11:24 UTCPOSTfail4023946 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-07 11:24 UTCPOSTfail4021078 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-02 11:24 UTCPOSTfail4022701 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-08-14 08:53 UTCPOSTfail402852 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

No listing changes observed.

unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.

5.Dispute this record

Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.

20–2,000 characters · 0 so far