SPX
SPX402.
Open Terminal
SPX402 · pre-launch · indexer warming upAwaiting first verified executions on-chainMethodology v0.1.7 · operator weight 5%Helius webhook bus · armedReconciler · standing bySPX402 · pre-launch · indexer warming upAwaiting first verified executions on-chainMethodology v0.1.7 · operator weight 5%Helius webhook bus · armedReconciler · standing bySPX402 · pre-launch · indexer warming upAwaiting first verified executions on-chainMethodology v0.1.7 · operator weight 5%Helius webhook bus · armedReconciler · standing by
Methodology

The score is not an opinion.
It is a receipt compression algorithm.

SPX402 grades observable on-chain execution patterns. Every input is derived from a verifiable signature, slot, and instruction. No off-chain claims, no social signals, no token price.

What SPX402 measures

Deposits, buybacks, burns, failed windows, metadata presence, operator verification, and time since the last successful execution.

What SPX402 refuses to measure

  • ✕ Token price
  • ✕ Expected return
  • ✕ Social momentum
  • ✕ Meme quality
  • ✕ Celebrity endorsement
  • ✕ Holder count
  • ✕ Vibes
  • ✕ Future buyback promises
Score Formula

Transparency Score = Σ weighted execution signals

Deposit Consistency
20%

Density and regularity of confirmed deposits to the Agent Deposit Address.

Buyback Execution Rate
25%

Ratio of expected buyback windows that produced a confirmed buyback.

Burn Confirmation Rate
20%

Ratio of buybacks that resulted in confirmed SPL Token burns.

Failed / Errored Tx
15%

Inverse score for failed buyback or burn instructions in observed windows.

Recency
10%

Time since the last successful buyback. Decays with silence.

Metadata
5%

Presence of skills.md and parseable metadata for the agent.

Operator Verification
5%

Wallet signature confirmed against the on-chain creator record.

Σ = 100 points · Grade is assigned by the band the score falls in.

Grade taxonomy

SPX AAA
90–100
Flawless observable execution.
SPX AA
80–89
Consistent execution with minor anomalies.
SPX A
70–79
Active, with some gaps.
SPX BBB
60–69
Functional but irregular.
SPX BB
40–59
Inconsistent. Monitor closely.
SPX B
20–39
Stale or degraded.
SPX D
0–19
Inactive or high-risk execution pattern.
SPX404
n/a
Agent not found, or insufficient evidence to grade.

Event confidence

high

Raw transaction, decoded instruction, balance delta, and expected mint all agree.

medium

Balance delta and address context agree, but the instruction path is ambiguous.

low

Signal exists, but supporting evidence is incomplete.

unknown

SPX402 has insufficient evidence. The correct answer is “unknown”, not “probably fine”.

Data sources

  • Helius webhooks — live on-chain event delivery, with idempotent reconciliation against duplicate retries.
  • Raw transaction backfill — reconciled against decoded instructions for missed events.
  • Pump & PumpSwap IDLs — canonical instruction decoding from the official public IDL repository.
  • SPL Token burn detection — direct on-chain confirmation, not log parsing.
  • Manual fixture validation — every parser version is regression-tested against a corpus of real transactions.

Why token price is excluded

Token price reflects market participation, liquidity conditions, and speculation. None of those are operational signals. SPX402 grades whether an agent settles its claimed flow on-chain. Whether the market rewards or ignores that flow is not part of the score.

Why SPX402 can downgrade itself

SPX402's own tokenized agent is scored by the same methodology as every other tracked agent. If our buybacks fail or our operator stops signing, the grade drops. The trust layer dies the moment the rater grants itself an exception.

Known limitations

  • • Webhook delivery latency may delay event ingestion. Reconciliation runs every 60 seconds.
  • • Custom buyback routes outside known IDLs may surface as low-confidence events.
  • • Off-chain revenue, service quality, and operator intent are unknowable to SPX402.
  • • A high score does not predict price, future execution, or solvency.

Appeals and corrections

Operators may submit a verification signature and a parser-fixture link via the operator dashboard. Score recalculations are deterministic and replayable from the underlying event log.