ai-safe2-framework

NEXUS v0.5.0 — Sovereign Payment Gateway

NEXUS v0.5.0 gives builders a safer boundary for agent-initiated payments. An agent may propose a purchase, but it cannot silently expand its authority, obtain unrestricted payment keys, replay an approval, restore spent capacity, or decide for itself that money moved.

Why use it

Agent identity and a valid signature are not enough when the agent host may be compromised. NEXUS adds deterministic checks at the point of value movement:

This raises the cost of fraud and agent compromise while keeping the normal user experience simple: clear decisions by default, and immediate evidence when a person, investigator, or auditor needs to understand what happened.

Install

python -m pip install nexus-a2a-sdk==0.5.0
import nexus_sdk
from nexus_sdk.payments import NEXUSPaymentExecutionPlane

assert nexus_sdk.__version__ == "0.5.0"

The published distribution is named nexus-a2a-sdk; the Python import is nexus_sdk.

What is included

Compatibility

The release retains the CP.5.APAY/0.4 profile, schemas, policy identifiers, and wire contracts. v0.5.0 composes and hardens that foundation; it does not silently introduce an incompatible protocol revision.

Production boundary

NEXUS is a reference implementation, not a certification or automatic claim of production safety. Before moving real value, operators must supply durable production storage, protected signing or HSM-backed credentials, authenticated payment-rail integrations, independently controlled trust roots, monitoring, operational governance, and the deployment evidence identified by the readiness API.

Start with the NEXUS guide, the Sovereign Payment Gateway contract, and Deployment Proof & Readiness.

Security issues should be reported through the repository’s security policy, not a public issue.