Skip to main content
vet402
MenuClose
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-11-12 · 3 days ago
vet402Back to the registerMethodology

x402engine.app/api/llm/gpt-5-nano

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402engine.app/api/llm/gpt-5-nano
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x7dd5be069f2d2ead75ec7c3423b116ff043c2629
Declared price (base units)2393
Catalog statusactive
First seen / last seen2026-10-12 01:02 UTC / 2026-11-15 08:06 UTC
Catalog-reported calls / payers (30d)13 / 6

2.Probe history

2026-10-132026-11-12
Figure 1. Probe timeline, last 18 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-11-12 22:40 UTCPOSTfail402192 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-11-10 22:40 UTCPOSTfail402433 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-11-08 16:40 UTCPOSTfail402197 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-11-06 13:40 UTCPOSTfail402248 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-11-04 06:41 UTCPOSTfail40293 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-11-01 04:40 UTCPOSTfail402279 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-30 04:40 UTCPOSTfail402283 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-28 13:40 UTCPOSTfail402296 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-26 18:40 UTCPOSTfail402419 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-25 00:40 UTCPOSTfail402560 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-22 22:40 UTCPOSTfail40298 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-21 13:40 UTCPOSTfail402126 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-19 22:40 UTCPOSTfail402110 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-18 13:40 UTCPOSTfail402106 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-17 04:40 UTCPOSTfail402263 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-15 12:40 UTCPOSTfail402217 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-14 10:30 UTCPOSTfail402393 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.
2026-10-13 10:30 UTCPOSTfail402153 msprice_mismatchDeclared 2393 of 0x8335…2913; the 402 offered 1773 of 0x8335…2913, 1773000000000000 of 0xFAfD…79E7, 1773 of EPjFWd…Dt1v.

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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far