Reviewer & evidence hub

One trust layer. Multiple payment rails. Verifiable outcomes.

SafeGate sits after payment and before trust. This hub gives reviewers, developers and design partners a clean path through current production evidence, machine-readable verification surfaces and historical engineering artifacts — without turning SafeGate into a payment processor, wallet, custodian or escrow.

Base Mainnet commerce evidence Real x402 paid API revenue Replay-safe recovery proven Public SDK / MCP surface Historical reviewer paths preserved

Review current evidence Open technical archive Open developer portal

Current review surfaces

Start with what SafeGate can prove now.

Current production evidence is separated from older controlled demos. Each card states what was actually observed and avoids upgrading evidence beyond its supported assurance.

Production evidence

Base Mainnet commerce verification

Real USDC commerce activity has been bound to intended requests, replay-protected, followed through fulfillment and converted into portable commerce evidence.

Payment → request → outcome → evidence

Real paid API

x402 machine-buyable evidence

A real 0.07 USDC paid API flow completed with signed evidence delivery. Recovery reused the original authorization and completed without a second charge.

Paid request → review → recovery → evidence

Merchant pilot

Real merchant outcome proof

A Base Mainnet merchant pilot completed payment verification, fulfillment completion and evidence creation with customer- and merchant-visible results.

Verified commerce outcome

Agent surface

Commerce Outcome / MCP

Agents can inspect deterministic commerce outcomes and assurance without SafeGate receiving wallet authority or permission to move funds.

Verify before trust

Public SDK

Developer integration

The public SafeGate SDK exposes verification and agent-facing surfaces while preserving error semantics and preventing fake success states.

@nurexenlabs/safegate-sdk

Historical / controlled

Earlier testnet & reviewer evidence

Pi Testnet, Base Sepolia, Hedera and earlier reviewer flows remain available as historical engineering evidence, not as substitutes for current production claims.

Preserved, not promoted

Reviewer route

A cleaner reading order.

Instead of reading the project chronologically, review SafeGate from current product claim to supporting evidence, then descend into historical engineering detail only when needed.

Understand the product

Start at the homepage: what SafeGate does, who uses it and what it does not become.

Inspect current proof

Review real payment-bound commerce outcomes, replay safety, evidence and signed results.

Check developer surfaces

Review SDK, API and MCP integration boundaries and machine-readable assurance.

Open historical archive

Use the technical archive only when implementation lineage or earlier controlled evidence is relevant.

Proof, not promises

Selected current milestones.

0.07 USDCReal paid API revenue with replay-safe recovery and no second charge.

0.10 USDCReal Base Mainnet merchant pilot with commerce outcome and evidence delivery.

OBSERVED → VALIDATEDAssurance remains explicit; stronger labels require real validation mechanisms.

Agent-readableOutcome and evidence can be consumed by software without SafeGate controlling funds.

Public-safe boundaries

What a reviewer should — and should not — conclude.

Supported conclusions

SafeGate independently verifies post-payment commerce evidence. Payment evidence can be bound to the exact intended request. Replay and duplicate consumption can be rejected durably. Evidence can be classified with explicit assurance and provenance. Agents can consume results without giving SafeGate wallet authority.

Not claimed

SafeGate is not a payment processor, wallet, bank or exchange. SafeGate does not custody funds or private keys. Historical testnet evidence is not presented as current Mainnet production proof. Unsupported evidence links remain UNVERIFIED rather than being inferred. No external partnership or validation is claimed without evidence.

Historical archive rule: old reviewer URLs remain available so hackathon, audit and engineering references do not break. They are preserved as historical evidence, while the homepage and this hub present the current product first.