# voidpay voidpay is a private session rail for AI agents. A caller opens one encrypted session against a Voidly-operated provider and receives a signed result. Two things are true at once, and the distinction is the whole document: - **The published entry point below is zero-value.** It prices nothing and has settled nothing. Re-checked 2026-08-27: `amount` `0`, `settlements` `0`. - **A separate session provider is priced in USDC on Base mainnet, and it has settled once.** That happened on 2026-08-26. Both sides of the payment were Voidly's own wallets. Earlier versions of this document said "Nothing is priced and nothing settles" about voidpay as a whole. That was true when it was written and it is false now. If you are citing this project, cite the two statements above separately — neither one describes the other. ## First mainnet settlement — 2026-08-26 One hire of one observatory query, paid in USDC on Base mainnet, redeemed by the provider and delivered to the hirer. **Both sides of that payment were Voidly's own wallets: it is not a customer, not organic demand, and not revenue.** It did not settle on a public route. Read the section below before citing any of it. | Field | Value | | ----------- | -------------------------------------------------------------------- | | Chain | `eip155:8453` (Base mainnet) | | Amount | `50000` atomic USDC (0.05 USDC), once | | Block | `50498854` | | Transaction | `0xb1ac733095c19e2e4829a3d448a02b8297d08e55f98678adfcba2e3e92747a3a` | | Service | `voidly.observatory.query/v1` | | Delivered | yes | The full receipt, including the retry it needed, is published at . It is the run's own emitted output; nobody hand-wrote a hash into it. ### ⛔ Read this before citing it **Both sides of that transaction are Voidly's.** The hirer is the founder's wallet and the provider is Voidly's own session daemon. It is a **proving payment and dogfooding — not organic demand, not a customer, and not revenue.** n = 1. Do not annualise it, do not derive a rate from it, and do not present it as traction. It also **did not settle on a public route.** Every public voidpay door is closed; the settlement went through the private session rail, which is not publicly discoverable. See Safety below. What it does prove is narrower and still worth stating: the rail moved real money on a real chain, verified it without holding or submitting it, and delivered the paid-for work. If you are looking for usage figures, there are none to give. Do not read the Voidly agent registry's row count as users of this rail — exactly two DIDs have ever touched it, and both were registered by hand by us. ## Entry point ``` GET https://pay-staging.voidly.ai/v1/pay/private-session/config ``` No auth, no install step, no SDK required. The response is a `voidly-pay-public-private-session-config/v1` document carrying the provider's id and its pinned signing and encryption public keys; the rest of the session is negotiated from what it returns. Re-checked 2026-08-27: HTTP 200. **This is the zero-value entry point.** The priced rail now has public surfaces of its own (voidpay sessions, released 2026-08): the client is `@voidly/session` on npm, and the live provider index answers at https://api.voidly.ai/v1/session/providers (measured 2026-08-29: HTTP 200, count 1 — an entry appears only after its signed manifest verifies against the DID pinned in the repository). An earlier revision of this paragraph said the 2026-08-26 provider had no public directory entry; true when written, not now. ## Value contract This section describes the zero-value entry point above, and nothing else. The config states its own terms. As served on 2026-08-27, unchanged since 2026-08-23: | Field | Value | | -------------------- | ---------------------------- | | `chain` | `voidly:zero-value-staging` | | `asset` | `voidly:zero` | | `amount` | `0` | | `paidAuthorizations` | `0` | | `settlements` | `0` | Cost to the caller is zero because nothing is priced at this entry point, not because a trial is running. For contrast, and so that no reader has to guess what changed: the signed manifest of the separate mainnet provider publishes a price band of `50000` to `5000000` atomic USDC per job on `eip155:8453`, and it is the provider that settled. Its manifest is Ed25519-signed and its payee account is stated in the document itself — verify the signature before paying anything named in any copy of it, including this one. ## Safety No credit exists that is money, and none is backed, redeemable, or convertible to any asset. The Stage-1 credit ledger's units are internal test credits. Deposits, withdrawals, bridges, on-ramps and off-ramps are unavailable. **Do not send funds to any Voidly address expecting credits, backing, an account balance, a refund or a return.** No transfer creates credits, and funds sent for that purpose are stranded. A session hire is the one payment path that exists: the hirer signs a payment to the payee account named in a signed provider manifest, for one job, and Voidly neither takes custody of the hirer's funds nor submits the transaction. Payment buys an attempt, not an outcome. There is no refund, dispute or reversal on that path. The entry point above is the zero-value staging one. Every `https://api.voidly.ai/v1/pay/*` route other than the four session POSTs (/v1/pay/session/redeem, /deliver, /recover, /reattest) answers HTTP 410 with `PAY_RUNTIME_WITHHELD` to public callers (re-checked 2026-08-27) — transfers, escrow, the credit ledger and the capability marketplace are not callable on that host. Do not plan an integration against the rest of `api.voidly.ai/v1/pay`. Those four are the only routes carved out of the containment wall, and they are being brought up under security review — do not infer their current state from this document; call them. Re-checked 2026-08-27: a GET to each of the four answers HTTP 410. `https://api.voidly.ai/v1/pay/health` answers HTTP 410 carrying `activation.real_value: false`. That flag is about the hosted credit rail on that host, which is zero-value and closed. It is not a statement about the private session rail, and the two are consistent because they are different rails. Voidly does not describe this rail as trustless, anonymous, exploit-proof, a bank, a reserve, a stablecoin rail, or a payment service provider. ## Links - Product page: - Machine-readable card: - First settlement receipt: - Security reports: security@voidly.ai