NEXUSEVALCHECKING
Operational gateway
Live service status is requested from Immortal Dynasty's server-side status proxy, which in turn checks the NexusEval production endpoints.
TOOLS350
ROUTES25
LIVE PROOF CENTER
Do not trust the pitch.
Inspect the infrastructure.
This page separates what is live and independently inspectable from what is product direction. Machine-payment configuration, API contracts, source and operational status are linked directly.
Open raw operational status ↗
Base USDC settlement address
0x756A9769…64A0551cThe x402 manifest declares the machine-service network, asset and payment recipient. Anyone can inspect the address independently.
View on BaseScan ↗x402 discovery
Paid routes publish machine-readable payment requirements. The current service manifest is public and includes the configured network and prices.
Open x402 manifest ↗OpenAPI
Buyer-facing routes expose a public OpenAPI contract so developers and agents can inspect request and response schemas before integrating.
Open live OpenAPI ↗GitHub discovery repository
The public NexusEval discovery repository exposes integration policies, machine-readable signals and public verification links without exposing payment keys, customer data or the private payment core.
Open GitHub ↗What counts — and what does not
Immortal Dynasty does not treat a crawler, 402 challenge, health probe, test, listing or bid as revenue. A paid result needs an independent payer, successful settlement and delivered 2xx output.
Open live revenue-readiness definition ↗Business payment trust
Human and enterprise payments use server-created commercial links. The amount is not taken from an editable browser parameter; the backend creates the order/link, verifies gateway state, and processes signed webhook events before recording paid state.
01
Scope first. Commercial amount is agreed for the actual work rather than forced into a public fixed plan.
02
Server creates payment. Customer details and the authoritative amount are sent to the gateway from the backend.
03
Verify after payment. Gateway state and signed webhook data are checked server-side before paid status is trusted.
Transparency boundary
Public proof can verify service configuration, source, network and on-chain settlement activity. It cannot prove a customer's identity, private prompt content, or confidential enterprise engagement—and those should not be exposed publicly.