Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-10-04 · 1 day ago

vaaya.ai/api/run/fal/generate

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://vaaya.ai/api/run/fal/generate
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x7c655d3d3944bd27994dd81a036c3afb19806c40
Declared price (base units)400000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)24 / 10

2.Probe history

2026-09-142026-10-04
Figure 1. Probe timeline, last 30 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-04 22:40 UTCPOSTfail40226 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-10-04 04:40 UTCPOSTfail402423 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-10-03 04:40 UTCPOSTfail402597 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-10-02 13:40 UTCPOSTfail40233 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-10-01 16:40 UTCPOSTfail40268 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-09-30 22:40 UTCPOSTfail40280 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-09-30 04:40 UTCPOSTfail402151 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-09-29 10:30 UTCPOSTfail40294 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-09-29 07:38 UTCPOSTfail402225 msprice_mismatchDeclared 400000 of 0x8335…2913; the 402 offered 10000 of 0x8335…2913.
2026-09-28 22:40 UTCPOSTfail402611 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-28 04:40 UTCPOSTfail402801 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 13:40 UTCPOSTfail402608 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 22:40 UTCPOSTfail402616 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 04:40 UTCPOSTfail402174 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 13:40 UTCPOSTfail402154 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 16:40 UTCPOSTfail402181 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 22:40 UTCPOSTfail402413 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-23 04:40 UTCPOSTfail402283 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-22 13:40 UTCPOSTfail402216 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-21 16:40 UTCPOSTfail402402 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 22:40 UTCPOSTfail402392 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-20 04:40 UTCPOSTfail402506 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-19 13:40 UTCPOSTfail40298 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 22:40 UTCPOSTfail40284 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-18 04:40 UTCPOSTfail402278 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-17 13:40 UTCPOSTfail402190 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-16 16:40 UTCPOSTfail402112 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 22:40 UTCPOSTfail402122 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-15 04:40 UTCPOSTfail402133 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-14 16:40 UTCPOSTfail402269 msprice_mismatchAmount or asset 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