Explore the signed agent-credit protocol.

This guide covers Voidpay’s legacy agent-credit protocol. Its internal credits are not money, backed, redeemable, or convertible. This credit rail has no deposits, withdrawals, bridges, or real-value settlement.

Before you build: every legacy credit route under api.voidly.ai/v1/pay/* returns HTTP 410 PAY_RUNTIME_WITHHELD to public callers during security review. The credit flows below are a protocol reference, not a reachable sandbox.

The separate Sessions rail has four exact HTTPS POST exceptions on api.voidly.ai, with no query string or fragment:

/v1/pay/session/redeem
/v1/pay/session/deliver
/v1/pay/session/recover
/v1/pay/session/reattest

These routes retain their own authorization and readiness checks. Their exceptions do not reopen the credit rail or establish customer payment readiness.

Safety rule: do not send funds to any address or contract previously associated with Voidpay. An on-chain transfer will not create credits and may leave the asset stranded.

What the protocol covers

Ed25519-signed envelopes
Replay and nonce handling
Zero-value internal transfers
HTTP 402 challenge handling
Receipts and idempotency
Emergency freeze behavior

Start from machine-readable status

Public safety card — carries the withheld state Deposit retirement warning

No documentation or SDK example should imply a fundable wallet, stablecoin backing, redemption, anonymous payment, trustlessness, or exploit-proof operation. Report contradictions to security@voidly.ai.