Add an org member by wallet (owner-only, v1.77)
Owner-only. Adds a member by wallet address with a role. A brand-new wallet is provisioned as a human principal; an existing wallet is added by its resolved principal regardless of type (informational, not an authz gate). For non-member automation, prefer a per-project grant. Audited. vault-agent-envelopes: custody follows membership for human and agent principals alike — the member becomes a desired envelope recipient on every present and future vault the org owns (a ci principal does not), and the cap on custody-eligible memberships (MAX_EPOCH_ROTATION_ENVELOPES) is reserved at this add, keyed or not (422 MAX_EPOCH_ROTATION_ENVELOPES_EXCEEDED). vault-multi-writer rev 47: next_actions additionally carries a sync_writers entry naming the org's vaults where the new member is NOT yet an active, non-gateway-blocked writer — the signal to run add_writer_key{"writer"} (or repos access sync) for them; omitted when there is no such vault. No server-side writer admission ever happens on this route.
Request
- Base URL: https://api.run402.com
- URL: https://api.run402.com/orgs/v1/{org_id}/members
- Auth: API key in header SIGN-IN-WITH-X
Path parameters
Headers
SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.
Request body
Response
Member added
Changes
No recorded changes to this operation across all 1 revision of this API.