Zeronda’s private pilot is focused on proving the beneficiary and sponsor flow end to end. A public API will follow the same rule: an invoice file is mandatory, and no caller can assert its own payable total.
POST /v1/invoice-requests
Authorization: Bearer zrd_…
Idempotency-Key: invoice_2026_041
Content-Type: multipart/form-data
invoice=@original-invoice.pdf
sponsor_email=finance@example.com
purpose=Client cloud infrastructureExtraction, duplicate checks, then sponsor outreach
The API will write to the same invoice registry and payment ledger as the Zeronda workspace—not to a parallel developer-only sandbox.
A platform supplies evidence, beneficiary identity, sponsor email, purpose and its own reference. Zeronda derives the amount and returns an opaque request ID.
Signed, replay-resistant webhooks will report validation, sponsor decisions, Stripe-confirmed payment, refunds and disputes—without including the private invoice file.
No pretend endpoint. The earlier developer preview predated the invoice-first product and has been removed.
No amount-only requests. An integration will not be able to bypass evidence extraction by supplying a total in JSON.
No browser secret. Creation keys will belong on a platform’s server; sponsors will continue through Zeronda and Stripe-hosted pages.
The public contract will be built on the behaviour we validate with real beneficiary and sponsor teams.