POST/account/change-name
Bearer authaccountChangeNameChange the network name of the calling network. The previous name enters a reclaim cooldown. Subject to the account action rate limit.
URnetwork ينفّذ مواصفات مشغّل بروتوكول UR بالكامل. بروتوكول UR ↗
Change the network name of the calling network. The previous name enters a reclaim cooldown. Subject to the account action rate limit.
Claim an unused network name for the calling network. Claiming and changing have SEPARATE daily budgets: a first-time claim does not consume any of the rename budget, and vice versa. Renaming a name that is still inside its reclaim cooldown is charged to the change-name budget instead.
Create an API key for the account.
uuid
Remove an API key for the account.
uuid
Fetches a list of API keys associated with the account. The list does not include the API key secrets, only metadata.
Fetches the payout wallet associated with the network
udid
USDC provider payouts have ended. This endpoint remains for existing apps and refuses every payout wallet selection with 400.
udid
Retrieves account points earned. Eventually, users will be able to convert points for tokens
uuid
uuid
What earned the points. The server only writes the four payout events today; referral is historical, kept so rows written before the referral award was withdrawn still validate.
uuid
uuid
uuid
datetime
Retrieves list of account payments
Create a new wallet for your network. Adding a wallet does not select it for payouts; USDC provider payouts have ended.
Ignored. The wallet is always created for the caller's own network, taken from the bearer token; this field is read off the body only to be overwritten.
The blockchain associated with the address. SOL and MATIC are payout chains; TAO is accepted and stored as a non-payout identity. Case-insensitive.
The wallet address on blockchain
We only support "USDC"
udid
Get a list of wallets associated with your network
A list of wallets associated with your network
udid
If the wallet was created through the Circle flow, it is the ID associated with the Circle wallet.
udid
TAO appears for a wallet created as a non-payout identity.
Blockchain wallet address
datetime
Remove a wallet from your list of account wallets. Removing the selected payout wallet clears that selection without promoting another wallet. USDC provider payouts have ended.
udid
Wallet successfully removed
Verify that a wallet holds a Seeker or Saga Genesis token by validating a signed message. Either holding succeeds; a wallet with neither is refused with error. and error.code seeker_, and a token lookup that fails is answered the same way with seeker_.
The wallet public key
The signed message
Why the wallet was not verified, for a localized message. seeker_: the wallet holds no Seeker or Saga token. seeker_: the wallet signature did not verify. seeker_: the token lookup failed. Absent from older servers; clients fall back to message for an absent or unknown code.
Fetch balance codes redeemed by network
The caller network's finalized epochs, newest first: the points earned inside each epoch's wall-clock window, the bytes the network served behind those points, and the network's share of the operator pool in basis points (0 when no coldkey was attached, i.e. points only). limit defaults to 26 and is capped at 104.
Points and bytes count the weekly operator blocks (Sunday 00:00 UTC to the next Sunday 00:00 UTC) the same way: a block counts in the epoch whose window contains the block's end. A block's bytes are the payout bytes of the provider network's settled traffic in the block: sweeps of contracts with a credit-bearing outcome (settled, or a dispute resolved) that closed at or after the earning cutoff, by settlement time. A contract settled without escrow, and traffic before the cutoff, carry none. Once a block's points are awarded, its bytes are the ones the award shared the block's payout points by. Points of other kinds (reliability, referral, multipliers, and payout-plan points for traffic before the cutoff) have no bytes behind them.
Two running figures cover the traffic no finalized epoch holds yet, both counted with the rule above. They run two to three hours behind live traffic: a settlement is counted two hours after it started, so that it has committed, and the figures refresh about hourly. Each carries as_of_millis, the time it counts traffic through.
current_ block is the open block's bytes so far. Its epoch is the epoch it will count in, the one whose window holds the block's end. It grows all week and starts again from 0 at Sunday 00:00 UTC.current_ epoch is the open epoch's bytes so far: those of the blocks that end in it. When the epoch finalizes, its served_ byte_ count continues this figure. It grows only while a block that ends in the epoch is open, or still settling just after it ended. Traffic in a block that ends after the epoch counts toward a later epoch, and shows in current_ block until then.On mainnet, epochs currently open on Friday evenings (UTC) and blocks end at Sunday 00:00 UTC. From Friday to Sunday the open block ends in the open epoch, and both figures grow. From Sunday on, the open block counts toward the next epoch: current_ holds still once the block that ended on Sunday is counted, about Sunday 02:00 to 03:00 UTC, and current_ keeps growing.
While settlement v2 is configured, an epoch it settles is listed from the ledger instead of its v1 row, once a finalized v2 root covering it has been recorded: it carries amount_rao, the network's amount of the epoch, and its share_bps is that amount's share of the epoch's amounts.
Epochs to list; absent or 0 means 26, and above 104 means 104.
Epoch window start, unix milliseconds.
Epoch window end, unix milliseconds.
Points earned inside the window.
The network's share of the operator pool in basis points; 0 when no coldkey was attached. For a settlement v2 epoch, the share of the epoch's amounts that amount_rao is, rounded down; 0 when the epoch has no amounts.
Settlement v2 epochs only, absent for a v1 epoch: the network's amount of the epoch from the ledger, a decimal string of rao; "0" when the network has none.
The bytes the network served in the operator blocks whose points the epoch counts (see the operation); 0 when none. For a block whose award has not committed yet, the bytes so far.
Epoch window start, unix milliseconds.
Epoch window end, unix milliseconds, projected at the chain's block period: the epoch is still open.
The bytes served so far in the operator blocks whose end is in the window, counted as for a finalized epoch. Traffic in a block that ends after the window counts toward the next epoch, and shows in current_ until then.
The figure counts traffic through this time, unix milliseconds: a few hours behind live traffic while a block is open, and a block's end once all of it is counted.
The operator block, counted from 1 at Sunday 2026-06-28 00:00 UTC.
Block start, unix milliseconds.
Block end, unix milliseconds.
The bytes served so far in the block, counted as for a finalized epoch.
The figure counts traffic through this time, unix milliseconds: two to three hours behind live traffic, and the block's start until any of it is counted.
The epoch the block counts in once it ends: the one whose window holds the block's end, the open epoch or a later one, projected at the chain's block period.
Unique network code to refer new users
udid
Referrals a network is paid for. 0 when the server has no referral cap configured (uncapped); clients treat 0 as unknown.
Bytes granted to the referrer per referral, per bonus period. 0 when unknown.
Bytes granted to the referred network, per bonus period. 0 when unknown.
The bonus grant period in seconds (24h = 86400). 0 when unknown.
True when this network is linked to a referrer and earns the referred bonus.
Get the network that was referred the authenticated network
uuid
Unlink the referral network from the authenticated network.
Set the parent referral network for the authenticated network.