Server-operated threshold custody: two independent server domains take part in every signature, and no complete private key is ever assembled.
Illustration: a transfer of 250.00 USDC is approved on a phone with Face ID. In the signing dashboard the policy allows it, server domains A and B each contribute a partial signature from their own half of the key authority, and the request is signed with no complete key assembled.
Production availability is qualified separately for each chain, region, custody profile and release.
Each signature is bound to its permit and checked against confirmed chain state; swap venues come from a reviewed allowlist with bounded slippage. Any difference refuses, and the refusal names the check.
A swap is compared with its permit: chain state, calldata, router and fee cap match; the platform fee differs, so signing is refused and nothing is signed.
Counted in USD cents, checked by issuer, gateway and signer.
An 18,000 cent request against a 25,000 cent cap passes at the issuer, the gateway and the signer.
Passkeys approve protected actions; each signer release needs a second approver.
A signer release with a matching measurement is approved by a second person with Face ID.
FROST for Solana, threshold ECDSA for EVM, one round trip per signature.
A request crosses to the signers and back once and is signed; the nonce it used is tombstoned.
Each wallet is homed at its nearest site; active shares stay there.
Four sites: US West, US East, Europe and Asia Pacific. A new wallet is homed in Europe, its nearest site.
Recovery backups are prepared before enrolment and owner keys rotate offline, without exporting a complete key. Every verdict, approval and refusal is appended to the decision record.
Decision record entries: transfer allowed; signer release approved; swap refused, platform fee differs; transfer refused, over the spend cap.
List networks with the TypeScript SDK, or call the REST API from any language. Protected actions also need signed authorization.
@miyaocat/sdk-server, sdk-browser, sdk-react, sdk-walletconnect
Teams manage wallets, members, keys and approvals in the dashboard; operators approve in the iOS app, which needs device and distribution qualification before release. Approval keys are separate from wallet signing shares.
Read the API reference// npm i @miyaocat/sdk-serverimport { MiyaoClient } from "@miyaocat/sdk-server"; const miyao = new MiyaoClient({ apiKey: process.env.MIYAO_API_KEY, baseUrl: "https://api.miyao.io",}); const networks = await miyao.networks.list();200 OKillustrative response
{
"data": [
{ "name": "example-evm-testnet", "family": "evm", "environment": "test" },
{ "name": "example-solana-devnet", "family": "solana", "environment": "test" }
]
}SDK. MiyaoClient is the published alias of FabricClient in @miyaocat/sdk-server 0.2.2. Protected actions also require signed approvals.
curl -sS https://api.miyao.io/v1/networks \ -H "Authorization: Bearer $MIYAO_API_KEY"200 OKillustrative response
{
"data": [
{ "name": "example-evm-testnet", "family": "evm", "environment": "test" },
{ "name": "example-solana-devnet", "family": "solana", "environment": "test" }
]
}Every response carries an x-request-id header; quote it when you report a problem.
// reqwest = { version = "0.12", features = ["json"] }// tokio = { version = "1", features = ["full"] }, serde_json = "1"use std::env; #[tokio::main]async fn main() -> Result<(), Box<dyn std::error::Error>> { let api_key = env::var("MIYAO_API_KEY")?; let networks: serde_json::Value = reqwest::Client::new() .get("https://api.miyao.io/v1/networks") .bearer_auth(api_key) .send() .await? .error_for_status()? .json() .await?; println!("{networks:#}"); Ok(())}200 OKillustrative response
{
"data": [
{ "name": "example-evm-testnet", "family": "evm", "environment": "test" },
{ "name": "example-solana-devnet", "family": "solana", "environment": "test" }
]
}Plain REST with reqwest. This is not an SDK.
package main import ( "fmt" "io" "log" "net/http" "os") func main() { req, err := http.NewRequest(http.MethodGet, "https://api.miyao.io/v1/networks", nil) if err != nil { log.Fatal(err) } req.Header.Set("Authorization", "Bearer "+os.Getenv("MIYAO_API_KEY")) resp, err := http.DefaultClient.Do(req) if err != nil { log.Fatal(err) } defer resp.Body.Close() body, err := io.ReadAll(resp.Body) if err != nil { log.Fatal(err) } fmt.Println(resp.Status, string(body))}200 OKillustrative response
{
"data": [
{ "name": "example-evm-testnet", "family": "evm", "environment": "test" },
{ "name": "example-solana-devnet", "family": "solana", "environment": "test" }
]
}Plain REST with net/http. This is not an SDK.
import os import requests resp = requests.get( "https://api.miyao.io/v1/networks", headers={"Authorization": f"Bearer {os.environ['MIYAO_API_KEY']}"}, timeout=10,)resp.raise_for_status()print(resp.json())200 OKillustrative response
{
"data": [
{ "name": "example-evm-testnet", "family": "evm", "environment": "test" },
{ "name": "example-solana-devnet", "family": "solana", "environment": "test" }
]
}Plain REST with requests. This is not an SDK.
Monthly settlement in USDC. No cards and no security downgrade by tier: every production plan includes the core API, SDKs, policies, approvals and evidence surface.
Miyao: $49 a month. Turnkey: $599 a month. Privy: $299 a month.
Miyao Launch plan
$49
Turnkey Pro
$599
Privy 500 to 2,499 MAU
$299
Privy is priced by monthly active users; here each active wallet counts as one. List prices from turnkey.com/pricing and privy.io/pricing, October 2026. Enterprise pricing excluded.
$0USDC / month
Build and evaluate on test networks.
Test only, with a hard production cap
$49USDC / month
For an early production integration.
Overages from $0.008 / wallet
$149USDC / month
For growing embedded-wallet products.
Overages step down as you scale
$249USDC / month
For established platforms with volume.
0.02 bps outbound-volume overage
Custom
Pricing, capacity and topology
Launch pricing. Allowances and overages remain subject to final service terms.
The Developer plan is free: build and evaluate on test networks, with a hard production cap.