AROBAI·DELIVERABLE API·BETA
AI capability, delivered as finished work.
arobai (AROBAI) is a deliverable API: you pay only for output that passes QC, the API is locked at /v1, and upstream model changes never reach your code.
1 Frame Credit = 1 accepted outputQC 96.4–100/v1 locked
SERIES 01 · 01-01 MEMOIR SCENE API / 01-02 LIFE ALBUM API · NO SLA
three rules
Three rules that make it a deliverable API.
L—01
Billing unit = delivery unit
1 Frame Credit = 1 accepted output. Failed jobs, and the re-rolls after them, are not billed.
1 Frame Credit
L—02
The quality gate sits on our side
96.4–100 across 13 real frames. A frame that misses the gate is re-rolled once, at our cost.
QC 96.4–100
L—03
Upstream changes never reach you
The interface is locked at /v1. When the model behind it changes, your request and response shapes do not.
/v1
both in beta · no sla
Series 01 — image narrative. Two APIs, both in beta.
13 frames · one run
Evidence — 13 frames, one QC ledger.
1910s
JIANGNAN
1930s
PORT
1940s
VILLAGE
POSTCARD
PRESET 05
TBD
- 13
- FRAMES
- 96.4
- MIN
- 100
- MAX
- 1
- RE-ROLL
frames available on request
the first year
You can wire it up in an afternoon. Then what?
| DAY | BUILT YOURSELF | DELIVERED BY AROBAI |
|---|---|---|
| 30 | upstream bumps the model — you re-tune | we absorb it |
| 90 | QC standard shifts — you build a gate | ours already re-rolls |
| 180 | a job fails silently — you instrument it | you read a typed error |
| 365 | nobody remembers the retry logic | it is still ours |
three steps
Three calls, one delivery.
01 Submit
curl -sS -X POST https://api.arobai.com/v1/jobs \ -H "Authorization: Bearer $AROBAI_KEY"\ -H "Content-Type: application/json" \ -d '{"text":"a family in Jiangnan, 1913, warm sepia"}'# -> 202 accepted . status queued . job 8f2b1c4e9d7a3f5002 Poll
curl -sS https://api.arobai.com/v1/jobs/8f2b1c4e9d7a3f50 \ -H "Authorization: Bearer $AROBAI_KEY"\# -> {"status":"succeeded","image_url":"/v1/images/..."}03 Fetch
curl -sS -o frame.jpg \ https://api.arobai.com/v1/images/<name> \ -H "Authorization: Bearer $AROBAI_KEY"\# -> 200 image/jpegbeta — keys issued by hand; auth headers are the final shape.
shipped ≠ promised
The ledger — shipped, measured, and not promised.
| PRODUCT | STATUS | MEASURED | ENDPOINT | NOT PROMISED |
|---|---|---|---|---|
| 01-01 Memoir Scene API | Beta | 10–15 s end-to-end · 5 presets | POST /v1/jobs | SLA · success rate · concurrency |
| 01-02 Life Album API | Beta | 8–9.8 s per frame · QC 96.4–100 | POST /v1/lifealbum/jobs | SLA · success rate · concurrency |
| 02 Text Intelligence | Planned | — | — | release date |
| 03 Audio-Visual | Planned | — | — | release date |
beta: no SLA committed. version policy unaffected: still locked at /v1.
numbers only rise
Series 02 and 03 are planned, not promised.
Series numbers only increase. A new series never reuses a number, and never changes the auth, envelope or billing unit you already integrated.
02
Text Intelligence
03
Audio-Visual
one claim per answer
Four questions we get asked.
- What is a deliverable API?
It prices per accepted output, not per call. The quality gate is ours: a frame that fails QC is re-rolled and never counted against your Frame Credits.
- What happens when a frame fails QC?
It is not billed. The job is re-rolled inside the same budget; you get an accepted frame or one code from the published error list. Failure costs us, not you.
- Does a model upgrade break my integration?
No. The interface is locked at /v1 and the response envelope is fixed. Upstream model changes are invisible to callers; request and response shapes do not move.
- How do I get access during beta?
Beta keys are issued by hand. Write to hello@arobai.com with your use case. No self-serve signup, no SLA, and Series 02 and 03 have no release date.