Wallet provisioning

When a new user needs a web3 wallet, a Beam agent reads the request from your connected system and calls Venly to create the wallet, within the rules and permissions you set. It writes the returned wallet reference back to the user's record and updates their onboarding status. Standard provisioning completes on its own. When a request is missing required identity fields, duplicates an existing wallet, or fails a check you defined, the agent holds it and notifies a person. Someone confirms the details before a wallet is issued, keeping onboarding controlled and every record accurate for later reference.

NFT mint status write-back

After a mint request goes to Venly, a Beam agent reads the transaction result and status the API returns. It applies your rule for what to record, then writes the token reference and mint state back to the linked record and notifies the owner when a mint completes. Successful mints update automatically. When a transaction fails, stays pending past a threshold you set, or returns an unexpected status, the agent routes it to a person rather than marking it done. Your team decides how to handle the failure, so no record shows a mint that did not actually settle.

Onboarding status updates

As users move through web3 onboarding, a Beam agent reads their wallet and activity state through Venly and the matching record in your system. It applies your rule for each stage, then updates the onboarding field and starts the next step where the connector allows it. Users progressing normally advance without manual work. When a step fails, an account shows conflicting states, or a required action is incomplete, the agent notifies a person instead of advancing the record. Your team resolves those cases, so onboarding status always reflects what the user has actually completed on chain.