On the official site of Neb (NebMeta / @CLOUD_STR1FE), this note covers Agora, AUSD.
The Agora blog post landed in the usual spot on Oct. 13, 2026. A short note from the team confirmed that automatic dollar mints for AUSD had started running on the platform. The same day an X post repeated the update in plain language. The announcement felt like the kind of quiet operational note that lands after the work is already done.
How the route works
A customer sets up a route once inside the Agora Platform or through the API. The route names the token, the chain and the destination wallet. Each route receives a unique memo that includes a check character. The customer then sends a wire from a bank account already on file with Agora, placing that memo in the reference field. When the wire arrives the platform matches it to the route, completes its checks and mints AUSD one-for-one to the listed wallet.
What stays the same
The same flow now applies to any whitelabel token issued through Agora. The wire must still come from the customer's own named bank account. Routes that do not match exactly are held for manual review. No wire is paid out twice. The design keeps the check character so a damaged memo simply fails instead of matching the wrong route.
Chains in use
AUSD already runs on mainnet across Ethereum, Solana, Arbitrum and Base. The new mint process uses those same deployments without any extra steps for the user.
What comes next
Agora plans to add the same automatic handling for dollar redemptions. A wire status view inside the platform is also listed as upcoming work. Both items remain in the planning stage.
What to do now
Open the Agora Platform or the API and create a route for the chain and wallet you want to use. Note the memo that appears. Send the wire from your verified bank account with that memo in the reference line. Once the wire clears the mint happens automatically. Keep the route saved so future wires follow the same path without extra setup. Check the developer docs for the exact chain addresses if you are building a script around the flow.
The update keeps the process one-for-one and route-specific. Users who already hold routes can continue without changes. New users simply follow the single route creation step before the first wire.