Simple hello to the network that returns some useful information. This can be used for discovery.

A QR code that maps to a URL to adopt the device. Send it to someone to scan to adopt the device.

Get account preferences.

Retrieves the paid and unpaid byte count provided to the network

Unique network code to refer new users

Check if the network name is available. A new network name must satisfy:

• at least 3 characters different from an existing network name
• at least 8 characters
• domain name compatible (see RFC 5890)
• not contain the dash (-) character (BringYour subdomains are reverse-flattened to a single level using dashes)

Fetches the payout wallet associated with the network

A QR code that maps to a URL to add the shared device. Send it to someone to scan to add the device.

Change password.

Authenticate with an auth code. The returned session is tied to the session that created the auth code, and will be expired with any of the creator's sessions. This is a subset of an OAuth flow.

Remove an adopt code. This must be called from the side that initiates the adoption.

Send verification code to email or phone number.

Send password reset code to email or phone number.

The status of the adopt-code device. The status can be one of:

• unassociated
• associated pending confirmation
• associated

Initialize the Circle USDC user self custody wallet. This starts a process that must be completed by the user.

Set account preferences.

Verify ownership of email or phone number.

Validate a USDC wallet address on the user custody wallet chain. This can be used to check whether an address can receive a transfer out from the user custody wallet. Please use this before initiating any transfer out to avoid lost funds.

Get the balance for the USDC user custody wallet. The user custody wallet allows BringYour to query the balance, but the user must take actions against the wallet.

Confirm the adoption of a device. This must be called from the side that initiates the adoption.

Create a limited use code (auth code) to share authentication with connected apps and tools. The code is tied to the caller session, and will be expired with any of the caller's sessions. Currently a code cannot be created for a client JWT (from /network/auth-client). This is a subset of an OAuth flow.

Set an existing account wallet as the wallet to receive network payments.

Remove a device association. The association can be any of:

• pending adoption device
• incoming shared device (not owned by the caller network)
• outgoing shared device (owned by the caller network)

Creates a code to adopt a device. The adopt code is valid for a limited time.

Remove a client from the network.

Creates an anonymous payment identifier to be used with purchases. This keeps network information out of the payment processor system. For example in Google Play this is called the "obfuscated account id".

The status of the shared device. The status can be one of:

• unassociated
• associated pending confirmation
• associated

Confirm the share of a device. This must be called from the side that initiates the share.

Set the name of the association. To set the name of devices owned by the network, use /device/set-name.

Sets the name of a device owned by the network. To set the name of devices shared with the network, use /device/set-association-name.

Randomly sample providers that for a location or group, which are active and in good health. This allows random iteration by using the exclude input to mark visited providers.

Remove a wallet from your list of account wallets

Password login for email and phone number.

Check if the balance code is valid.

Creates a code to share a device.

Create a spec object for find-providers2 using a description of the intended use of the network.

Out-of-band control messages for the connect protocol. Blocking request-response control messages need to be handled out-of-band to resolve the possibility of dedlocks in the client sequence.

Redeem the balance code and add the transfer balance to the caller network.

Set up a transfer from the Circle USDC user self custody wallet to an address. This starts a process that must be completed by the user.

Create a new wallet for your network. You can then use it as a payout wallet by posting to /account/payout-wallet.

Gain permission to use the connect protocol as the requested clientId, or assign a new clientId. Each network can have at most 128 clientIds. Above that number, new clientId requests will error until one or more existing clientIds are removed.

Start a login for a user authority. The user authority may be:

• email
• phone number
• Apple JWT
• Google JWT

Set the provide mode for a device.

Add a device, which can either be owned by the network or shared with the network. The code provided can be either adoption code or a share code. Once a code is added, the device becomes an associated device until confirmation. If the device is a shared device, it will remain an associated device after confirmation.

Create a new network. A user authority can be associated with at most one network.

Feedback.

Get statistics for all providers in the caller network for the last 90 days. This is meant to answer the top level question of how the providers in a network are performing.

Get a list of wallets associated with your network

Get all providers in the caller network. Each provider includes stats from the last 24 hours.

Randomly sample providers for locations, groups, or devices, which are active and in good health. This allows random iteration by using the exclude input to mark visited providers.

The devices associated with the caller network. Associated devices are:

• pending adoption devices
• incoming shared devices (not owned by the caller network)
• outgoing shared devices (owned by the caller network)

Get the current subscription status and transfer balance.