Identity badges

Optional upgrades attach public trust signals to a realm. Clients can read badges and verify permanent certificate signatures using only the public CA key — private CA material is never exposed.

Public fee table

GET/api/registry/entity

Returns fee schedule for Key and Verified applications.

bash

curl -sS https://grid-compute.com/api/registry/entity | jq .

Tier	Fee (USD)	Public signal
key	300	[Key] badge — permanent identity cert
verified	10,000	[Verified] entity badge

Read badges

GET/api/registry/entity?realm=fire

Public badges only for a realm.

bash

curl -sS 'https://grid-compute.com/api/registry/entity?realm=fire' | jq .

Certificate (public verify)

GET/api/registry/entity?realm=fire&cert=1

Badges plus permanent cert JSON when active.

GET/api/registry/entity?ca=1

Registry CA public key for offline verification.

bash

curl -sS 'https://grid-compute.com/api/registry/entity?ca=1' | jq .
curl -sS 'https://grid-compute.com/api/registry/entity?realm=fire&cert=1' | jq '.cert'

Apply (Cash App)

POST/api/registry/entity

Start or confirm an application. Same Cash App rail as name activation ($Caraveo + note). Realm should already be registered.

bash

# Start Key application (fields validated server-side)
curl -sS -X POST https://grid-compute.com/api/registry/entity \
  -H 'content-type: application/json' \
  -d '{
    "action": "start",
    "tier": "key",
    "realm": "fire",
    "pubkeyHex": "<64-hex-ed25519-pubkey>",
    "nodeId": "node_macmini"
  }' | jq .

After payment confirmation and successful review, an active application may include a permanent cert payload. Mesh UIs show only the human grid:// locator plus badge chips — not internal wire identifiers.

Never paste operator private keys into API bodies. Only public keys and realm metadata are accepted on write. Certificate private CA seeds are server-side only.