Do you charge by MAU? No. SigID does not bill by user count or monthly active users. Human login, passkey login, wallet sign-in, consent views, discovery, JWKS reads, and revocation are free.
Do human logins consume Auth Credits? No. Hosted login, passkey login, wallet sign-in, consent screens, discovery, JWKS reads, and token revocation do not consume Auth Credits.
What are Auth Credits for? Auth Credits meter higher-value identity operations such as agent authentication, token exchange, delegated access, introspection, wallet policy authorization, and signing.
Can I use SigID in production on Starter? Yes. Starter is intended for first production projects and includes custom branding plus 7-day audit retention. Growth is recommended when you need Premium Support, 30-day audit retention, more Auth Credits, and lower commerce fees.
When do I need Enterprise? Choose Enterprise for custom scale, long-term audit retention, advanced governance, compliance packages, data residency, procurement support, and SLA.
Is the x402 fee a protocol fee? No. SigID charges a commerce orchestration fee for identity, authorization, policy, receipts, audit, agent governance, and wallet controls around the payment flow.
Can my agent use my existing API keys and accounts? Yes. Store third-party OAuth tokens, API keys, and SSH keys in the credential vault and grant them to an agent with scopes and expiry. OAuth credentials are exchanged for short-lived provider tokens; static secrets are used through egress injection, where the key is attached at the boundary and the agent never sees it. Revoke the grant and access stops immediately.
Does SigID see my agent's traffic? Only if you route it through SigID-hosted egress. The egress data plane is open source: run it in your own infrastructure and workload traffic stays inside your network – SigID sees credential grants and audit envelopes, never request or response bodies.