Pick up where you left off: your usage for today, the keys on your account, and the ability to issue or revoke them.
Any key on your account works, including a revoked-safe one you still hold. We check it against the hash we store — we never see the key itself.
Press the button to finish signing in. The link works once, and nothing is spent until you press it.
Why a button? Mail scanners follow links before you do. Spending the link on arrival would use up your one use before you ever saw it.
If that address has an account, a link is on its way. It expires in 15 minutes and works once.
There is no password on this account and there never was one to leak. A sign-in is proven by something you already hold — an API key, or a single-use link we email to the address on the account. Both are checked server-side, both expire, and signing in here does not create a credential your integration does not already have.
attribution field. Data is provided
"as is", may be delayed or inaccurate, and must be independently verified. It is not the
sole basis for decisions affecting safety of life or property at sea.