402402Signal

Developer guides

Check a session or invoice commitment

Separate seller call prices, cumulative spend, deposited capital and native fees.

Read as Markdown · Packages and capability record

Check the commitment, not just the call price

Use this when funding a supported session or accepting an explicit grouped-purchase manifest. An ordinary exact-payment receipt does not authorize a batch or session.

Base and Solana sessions

The Session Client requires Node 24 and private POSIX/SQLite storage. Pin one endpoint, channel, parties, asset, call price, cumulative cap, maximum call count and fixed deadline before funding. Deposited capital, native fees and seller charges are different exposures.

The original signed observation stays in the private journal. Later continuation follows separately pinned buyer policy; it does not extend the original receipt or buy another routing check. No automatic top-up or new channel is authorized. Unknown results stop later calls, including after restart.

The controller supports 1 to 64 sequential calls and a buyer deadline up to 24 hours. Those are versioned bounds, not throughput or merchant-availability promises. Base receiver/token activity is serialized; unrelated receiver activity can leave confirmation unknown. This is not general concurrent-receiver coordination.

The Solana session cap is not a per-call price. The observed per_call_amount_atomic is null; establish and pin the merchant's actual call economics separately.

Complete opening, continuation, recovery and close guide.

Algorand groups and invoices

The multi-item profile supports 2 to 15 job payments plus a sponsor transaction. The aggregate-invoice profile supports 2 to 64 explicit jobs represented by one invoice payment plus sponsorship. The invoice total is not a known per-job price.

The merchant must supply the supported ordered manifest. Verify exact jobs, payment count, recipient, total and fee quote. Do not split an ordinary one-payment offer into invented job payments. On-chain atomicity does not promise atomic HTTP delivery.

Manifest contract · Buyer adapter and examples.

Finish and reconcile

A voucher acknowledgment, a settlement transaction and a delivered resource are separate events. Confirm the original transaction and account effects. Receipt lookup must be genuinely read-only; resending a live voucher with a custom header is not automatically safe recovery. Missing evidence leaves the operation uncertain.

A qualifying hosted observation costs $0.003. Merchant charges, capital deposits, gas and rent are separate. Check profile and release scope before a live run.

Give this task to your coding agent
Integrate only the supported session or manifest profile at https://402signal.com/developers/sessions-and-invoices. Review runtime/storage requirements and hosted availability. Separate call price, cumulative spend, locked capital and native fees. Keep initial evidence historical and continuation policy explicit. Do not auto-top-up, extend expiry or retry an uncertain economic operation. Confirm original settlement and refund effects independently.