For platforms · future API

The API will start with the invoice.

The private pilot is proving the beneficiary and sponsor flow first. A public API will follow the same rule: every request needs an invoice, and the caller cannot supply its own payable total.

future API shape
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 infrastructure
✦
Run Invoice Intelligence first

Read and check the evidence before contacting the sponsor

Original evidence required Private file access Signed lifecycle events Idempotent creation
Planned contract

One record from request to outcome.

The API will use the same invoice registry and payment ledger as the Zeronda workspace. There will be no separate developer-only source of truth.

Create a request

Submit the original invoice

The platform supplies the evidence, beneficiary identity, sponsor email, purpose and an external reference. Invoice Intelligence derives the amount, runs its checks and returns an opaque request ID.

  • Multipart invoice upload
  • Invoice Intelligence result
  • Idempotency key from the platform

Why the API is not public yet

No placeholder endpoint. The earlier developer preview predated the invoice-first product and has been removed.

No amount-only requests. An integration will not bypass evidence extraction by sending a total in JSON.

No secrets in the browser. Creation keys will stay on the platform’s server. Sponsors will continue through Zeronda and Stripe-hosted pages.

</>
Start with the working flow

Run an invoice through the pilot.

The public contract will be based on behaviour validated with beneficiary and sponsor teams.