Become a verified issuer

Generate keys and issuer profile

Run the onboarding command to generate an Ed25519 keypair and a starter issuer profile JSON. Keep your private key secret — the public key goes in the well-known file in the next step.

badge-cli onboard-issuer --domain yourdomain.com --name "Your Org Name"

This outputs three files: issuer-private.pem, issuer-public.pem, and openbadges-issuer.json.

Host the issuer profile at your well-known URL

Upload openbadges-issuer.json to your web server so it is reachable at the path below. HTTPS is required. Serve with Content-Type: application/json.

https://yourdomain.com/.well-known/openbadges-issuer.json

{
  "@context": "https://www.w3.org/ns/credentials/v2",
  "id": "https://yourdomain.com/.well-known/openbadges-issuer.json",
  "type": ["Profile"],
  "name": "Your Org Name",
  "url": "https://yourdomain.com",
  "publicKey": [
    {
      "id": "https://yourdomain.com/.well-known/openbadges-issuer.json#key-1",
      "type": "Ed25519VerificationKey2020",
      "controller": "https://yourdomain.com/.well-known/openbadges-issuer.json",
      "publicKeyMultibase": "z..."
    }
  ]
}

Verify your domain

Submit your domain to the public trust API. This fetches your well-known file, validates its structure, checks key discoverability, and writes a domain trust record. Rate-limited — no API key required.

curl -X POST "https://badges.firmament.works/public/api/issuers/verify" \
  -H "Content-Type: application/json" \
  -d '{"domain":"yourdomain.com"}'

{
  "trustState": "DOMAIN_VERIFIED_SIGNATURE",
  "issuerDomain": "yourdomain.com",
  "message": "Domain verified successfully."
}

Issue and sign badges via CLI

Use the CLI to create a credential subject, sign it with your private key, and output a portable JSON badge file. The signed file can be hosted anywhere and verified by anyone using the public API.

badge-cli sign-badge \
  --issuer-key issuer-private.pem \
  --badge-class "Research Comprehension" \
  --recipient-email [email protected] \
  --recipient-name "Alex Smith" \
  --summary "Completed synthesis of three conflicting papers."

Or issue badges via MCP (AI tool integration)

Add the Signet MCP server to Claude Desktop, Cursor, or any MCP-compatible client. Your AI tool can then create badge classes, issue credentials, and sign them using the same API contract — with your API key set in the environment.

{
  "mcpServers": {
    "signet": {
      "command": "npx",
      "args": ["-y", "signet-mcp"],
      "env": {
        "SIGNET_API_KEY": "<your-api-key>",
        "SIGNET_BASE_URL": "https://badges.firmament.works"
      }
    }
  }
}

Once connected, prompt your AI: "Issue a badge for Alex Smith for completing the onboarding module." The MCP server handles key lookup, signing, and returns a verify URL you can share immediately. See llms.txt for machine-readable API docs.

Share and verify

Host your signed badge JSON at any HTTPS URL and share a verify link. Anyone — no account, no platform — can check the trust state using the public verifier or directly via the API.

https://badges.firmament.works/verify.html?url=https%3A%2F%2Fyourdomain.com%2Fbadges%2Fbadge.json&autoverify=1

curl "https://badges.firmament.works/public/api/verify/badge/https%3A%2F%2Fyourdomain.com%2Fbadges%2Fbadge.json"