@terminal3/t3n-sdk 4.16.1 → 4.17.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.ts CHANGED
@@ -2004,15 +2004,19 @@ declare class T3nClient {
2004
2004
  * returned exactly once here and is never persisted or recoverable
2005
2005
  * afterwards, so the caller must capture it immediately.
2006
2006
  *
2007
- * Atomic registration + card hosting: pass `options.agentUri` and the
2008
- * SAME transaction also writes the agent-registry record (URI + the
2009
- * org's publish-consent link, born together) and — unless
2010
- * `options.defaultCard === false` — hosts a PRIVATE card for the new
2011
- * agent in the org's `agent-cards` scope. The card body is
2007
+ * Atomic provisioning + card hosting: the SAME transaction mints the
2008
+ * agent, writes the agent-registry record (owner binding + the org's
2009
+ * publish-consent link), and — unless `options.defaultCard === false` —
2010
+ * hosts a PRIVATE card in the org's `agent-cards` scope. The card body is
2012
2011
  * `options.card` when given (object or pre-serialised JSON string);
2013
2012
  * otherwise the CONTRACT builds and hosts its default (which can even
2014
2013
  * name the agent DID, minted inside the same transaction).
2015
2014
  *
2015
+ * `options.agentUri` is **optional**: a T3N-hosted card is served at
2016
+ * `/api/agent-card/<did>`, so an agent needs no external URI. Pass one
2017
+ * only to record an external endpoint in the DID document's
2018
+ * `AgentService`; the card is hosted either way.
2019
+ *
2016
2020
  * The card is deliberately NOT published: an org-bound agent must not
2017
2021
  * become world-discoverable as a side effect of provisioning. Publish
2018
2022
  * explicitly with `agentCardPublish` (one call — the consent link