Autonomous Commerce Assurance

Your payment succeeded. Did the service?

SafeGate proves what happened after payment.

A rail-agnostic commerce verification and evidence layer for AI agents, paid APIs, digital services and platforms. SafeGate binds payment to the exact request, prevents replay, observes or validates what happened next, and produces portable CommerceProof.

BindObserveProve

Build with SafeGate See working evidence SafeShelf

3-minute overview

What is SafeGate?

Prefer to listen? This short overview explains the problem SafeGate solves, how the verification and evidence layer works, and why post-payment proof matters for AI agents, paid APIs and digital commerce.

3:02 English Audio overview

Listen: What is SafeGate?

No autoplay. Playback starts only when the visitor presses play.

Why SafeGate?

The hard part isn’t enabling AI agents to pay.

It’s independently proving what happened after they paid. SafeGate is built for that gap.

One core. Multiple surfaces.

Use SafeGate where your commerce happens.

Developers, agents and platforms use the same assurance model through different integration surfaces. The integration surface can evolve without weakening the SafeGate core.

Live foundation

Verify API

Programmatic verification for payment evidence, request binding, replay safety, outcome evidence and CommerceProof.

Payment → request → outcome

Observed core

Observed Middleware

Bind verified payment evidence to the exact request, enforce durable single-consume, preserve execution evidence and classify the resulting outcome.

Adapter → bind → consume → evidence

Public SDK

SDK

Embed SafeGate verification and proof workflows directly into applications and platforms.

@nurexenlabs/safegate-sdk@0.4.0

Agent surface

Agent / MCP

Give autonomous agents a machine-readable path to verify paid-service outcomes without granting SafeGate wallet authority.

Agent-callable commerce evidence

Paid evidence

x402 Commerce Evidence

Machine-buyable signed commerce evidence with payment-bound recovery, replay protection and explicit assurance.

Real paid production flow proven

Proven core

CommerceProof

Portable signed evidence describing what was paid for, what happened next, what evidence supports it and how strong the assurance is.

Human-readable + machine-readable

The assurance pipeline

Payment proves money moved. SafeGate proves what actually happened next — and tells you how strong that proof is.

SafeGate binds payment or execution evidence to the exact request, prevents replay, preserves the actual outcome and produces a signed, portable CommerceProof with explicit assurance.

Payment evidence Request binding Durable single-consume / replay safety Actual outcome observation

Field-level provenance Evidence class Assurance Signed CommerceProof

CLAIMED

A provider or execution system asserts that an outcome happened.

OBSERVED

SafeGate directly observed the paid request, execution, response or equivalent evidence.

VALIDATED

An independent validation mechanism verified the field using a named evidence class.

THIRD-PARTY ATTESTED

A separately identified external party contributes evidence under its own trust mechanism.

No silent upgrades. A field is VALIDATED only when its validation mechanism and evidence class are named and available. If that mechanism becomes stale or unavailable, assurance must degrade.

Rail-agnostic by design

Payment rails can change. The assurance model stays the same.

SafeGate keeps the core stable and pushes rail-specific logic into adapters. The core does not bend to an integration.

Production evidence

Base Mainnet

Real USDC payment verification and signed commerce evidence on Base Mainnet.

Real paid flow

x402

0.07 USDC machine-paid evidence flow completed with recovery and no second charge.

Proven testnet

Hedera x402

Paid request, request/payment binding, single-consume and replay rejection with signed OBSERVED outcome.

Public evidence

The Graph

Agent evidence continuity and proof-oriented integration artifacts.

Adapter / review

Circle / Arc

Adapter and reconciliation work retained without claiming unsupported production settlement.

Historical / backlog

Pi Network

Historical Testnet verification work remains archived as adapter evidence, not as the current product identity.

KeeperHub Execution Adapter V1

INTEGRATED

KeeperHub execution evidence is normalized into SafeGate’s request-binding, replay-safety and signed CommerceProof flow. Boundary: simulation is not execution proof.

SilentSwap Integration V1

PARTNER WORDING REVIEW

Real Base → Solana routed execution has been completed and independently evidenced. The final public presentation of the swap surface is being locked with the partner before production copy is changed.

Proof, not promises

Real commerce evidence now exists across more than one production model.

SafeGate is no longer only demonstrating future monetization. It has completed real paid and routed flows while preserving explicit evidence boundaries.

0.07 USDCFirst real paid API revenue over Base x402 with recovery and no double charge.

12.318083 → 11.339726Real Base → Solana routed USDC fulfillment completed in 55 seconds.

0.06 USDCFirst integrator revenue recorded from the routed SilentSwap flow.

0.10 USDCReal Base Mainnet merchant pilot used to verify commerce outcome and evidence delivery.

One assurance layer

For developers, AI agents, platforms and commerce applications.

Each audience gets a different interface to the same underlying proof semantics.

Developers

Integrate verification and CommerceProof through API and SDK surfaces.

AI Agents

Read deterministic assurance before trusting a paid API, dataset, inference or digital service.

Platforms

Embed SafeGate as middleware or an inline verifying proxy without becoming dependent on one payment rail.

Commerce Applications

Attach portable evidence to payment, delivery, API and digital-service outcomes.

Commerce application

SafeShelf stays.

SafeShelf remains SafeGate’s controlled digital-commerce surface: product, checkout, access or delivery outcome, merchant-visible record and proof — all in one inspectable flow. It is a commerce application built on SafeGate, not the SafeGate core itself.

Open SafeShelf

Developer quick start

Make commerce verifiable without rebuilding the trust layer.

Keep payment where it already works. Add SafeGate after the payment and around the outcome. Full integration guidance lives on the Developer Portal.

Open Developer Portal Open Evidence Archive

npm install @nurexenlabs/safegate-sdk

// Verify a payment-bound outcome
// Preserve SafeGate assurance + provenance
// Do not manufacture COMMERCE_VERIFIED

INTENT
  → PAYMENT
  → BINDING
  → SINGLE CONSUME
  → EXECUTION / FULFILLMENT
  → EVIDENCE
  → COMMERCEPROOF

Clear boundaries

SafeGate verifies commerce. It does not become the payment rail.

What SafeGate does

Binds payment evidence to the intended request and roles. Enforces durable single-consume and replay safety. Observes or validates outcomes at an explicit assurance level. Names provenance, evidence class and validation mechanism. Produces signed, portable commerce evidence.

What SafeGate is not

Not a wallet, bank, exchange or payment processor. No custody, escrow or control of private keys. No automatic authority to spend user funds. No silent upgrade from OBSERVED to VALIDATED. No claim of partnership or validation where none exists.