You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -300,7 +300,9 @@ with a spec such as `{"fields":{"password":{"value":"replacement"}}}`. Keep actu
300
300
secrets in protected files or stdin, never shell arguments. Omission preserves values;
301
301
null or an empty string clears supported fields, including required text/email/password fields (returning them to pending collection). The form still requires nonempty required inputs. Field definitions cannot change. Stale versions fail,
302
302
without retries. `items invoke <vault> <key> collect` reopens the full form without
303
-
clearing values; compare versions to observe edits to already-ready items.
303
+
clearing values; compare versions to observe edits to already-ready items. When an update
304
+
is bound to an earlier read, also pass `--expected-item-id <id>` to reject a replacement
305
+
item at the same key. Neither precondition is refreshed automatically.
304
306
305
307
Do not use credential items to store, collect, or fill credit card data, including card numbers (PANs), security codes (CVV/CVC), or expiration dates. Use wallet and card item types for credit cards and payment checkout instead.
306
308
@@ -515,7 +517,7 @@ card spec. Otherwise, the cardholder selects a card at approval. A reusable card
515
517
#### Invoking item operations
516
518
517
519
`items get` displays every `available_operations` entry's type and description, plus
518
-
an `items invoke` command retaining the selected project (replace `<json>` for fill).
520
+
an `items invoke` command retaining the selected project (replace `<json>` for fill or prepare_checkout).
519
521
Read the description and follow its approval requirements before invoking. Required user actions
520
522
(OAuth, enrollment, MFA, spend approval) appear separately; they are not operations to invoke
521
523
through this endpoint.
@@ -527,14 +529,37 @@ actions in `recovery_required`, even if a stale action or operation was returned
527
529
528
530
`authorize` sends `{"type":"authorize"}` without `--params` and returns the updated item,
529
531
possibly with a required user action. `collect` is also parameterless and returns a credential
530
-
collection URL. `--open` is supported for authorizeand collect.
531
-
The [API spec](https://api.onkernel.com/spec.yaml) also accepts `fill`, with its inputs in
532
+
collection URL. `--open` is supported for authorize, collect, and prepare_checkout.
533
+
The [API spec](https://api.onkernel.com/spec.yaml) also accepts `fill` and `prepare_checkout`, with their inputs in
532
534
`--params` or `--spec-file <path|->` (mutually exclusive, maximum 128 KiB). The positional
533
535
operation supplies `type`; including `type` in either input is rejected.
534
536
Parameters must be a JSON object without unknown or duplicate properties. There is no
535
537
operation `--spec` flag; wallet/card `--spec` flags remain unchanged. New parameterless
536
538
operations can still be invoked by name when advertised.
537
539
540
+
##### Prepare an AgentCard checkout
541
+
542
+
For an unused AgentCard card, invoke `prepare_checkout` only when advertised:
cmd.Long+="\nUpdate preserves omitted fields, replaces nonempty string values, and clears supported values with null or an empty string. Clearing a required text/email/password field returns pending_collection; form submissions still require a nonempty value.\nField definitions are immutable. Do not automatically retry version conflicts."
57
62
cmd.Flags().Int64("version", 0, "Expected version from items get (required; never auto-refreshed)")
58
63
_=cmd.MarkFlagRequired("version")
64
+
cmd.Flags().String("expected-item-id", "", "Immutable item ID from the original read; reject an update if the key now refers to a replacement item")
0 commit comments