Every project getsa real identity.
Each Loomal Project comes with a built-in cryptographic identity. Sign messages, verify signatures, and prove that an action was authorized. The same identity signs your payment receipts.
Anyone on the internet can verify a Loomal signature without depending on Loomal. The public identifier itself contains the verification material, so there's no registry lookup, no centralized issuer, no rotation drama. The on-chain payment wallet is a separate thing: a smart wallet on Base, not a custodial key.
How it works
Four steps. Most fire in under a second.
Project signup creates an identity
When you make a project, Loomal generates a signing key for it and gives you a public identifier you can share or embed.
Sign through one REST call
POST the data you want signed. Loomal returns a signature you can attach to webhooks, receipts, JWTs, or anything else you build.
Anyone verifies on their own
The public identifier itself contains the verification material. Recipients check the signature locally and they're done.
What you get
Built for developers who already shipped.
Cryptographic identity
Every project has a public identifier. Sign and verify with one REST call. Verifiers don't need to call Loomal to validate a signature.
Auditable
Every signature is logged in the activity timeline alongside email sends, vault reads, payment settles, and code generations.
Delegation chain
Human → Org → Project → Action. Revoke a human and every project under them stops signing instantly.
FAQ
Things builders ask.
What's a cryptographic identity?
Can I export the signing key?
Is the on-chain payment wallet also custodial?
What if I want to rotate the signing key?
Ready to ship identity?
Sign up for free. No card required. Read the docs while you wait.