Security

Before you sign

Only sign an offer you chose. Check its network, asset, payTo and amount before approving it. Keep a client-side per-call and daily budget. The TypeScript SDK pins the SingIt pay-to and native USDC asset for supported production networks and checks the selected offer before signing; its guards also enforce your configured budget.

With upto, read the per-request ceiling and reject offers above your budget. Actual metered billing cannot exceed that authorization. A client-side budget complements server checks and does not change the server’s limits.

API keys and scopes

Create a key in the SingIt app; the wallet signs its daily cap, per-request cap and expiry. Revoke keys you no longer need. Revoked or incorrect keys receive 401. For MCP, web_search and read_page need search scope; the paid market-data tools need tools scope. Free price and model lookup tools work without a key. See Developers.

Wallet allowances

Wallet limiter rules apply only to wallets that granted SingIt an allowance. For those wallets, daily caps, per-purchase caps, expiry and pause constrain spending through that SingIt allowance. See agent spending limits. Keep these wallet rules separate from SDK counters and individual API-key caps.

Private keys and vulnerability reports

SingIt never asks you to send your wallet private keys or seed phrase. Keep signing material in your wallet or local signer; do not paste it into support messages or reports.

Report vulnerabilities privately to [email protected]. Include the affected component, reproduction steps or a proof of concept, and the potential impact. Do not open a public issue or pull request for a security problem. Do not include real private keys, seed phrases or other people’s data. See the security policy.