checkout family
Posts a pay link into the conversation for a sell step
One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.
curl -X POST https://one.ie/api/signal/checkout:notify \
-H "Authorization: Bearer $ONE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"data": { "amountLabel": <any>, "group": <any>, "runId": <any>, "stepId": <any> }}'The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.
Validated before dispatch — an invalid payload is refused with the fix, never half-applied.
amountLabel any optional group any optional runId any optional stepId any optional stepName any optional url any optional The acknowledgement shape — the work itself completes after the call returns.
No declared fields.
Every call to checkout:notify, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.
Counting…
Every place in the open source that names checkout:notify, and the file that
answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no
import edge to follow and a grep is the honest shape of the question.
Structure, not volume — the count is in Traffic above.
Called from
Answered by
POST /api/signal/checkout:notify, after the envelope
validates the payload.
checkout family · 3 more
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"amountLabel": {},
"group": {},
"runId": {},
"stepId": {},
"stepName": {},
"url": {}
},
"additionalProperties": {}
} {
"$schema": "https://json-schema.org/draft/2020-12/schema"
}