Skip to content
DENPA DOCS

Mint a dk_ key

Mint

Section titled “Mint”
  1. Sign in at denpa.ai/developer.
  2. Create a key with a label. The key is shown once.
POST   /api/dev/keys   { label }      Privy JWT — mints dk_… (shown once)
GET    /api/dev/keys                  lists your keys
DELETE /api/dev/keys?id=<keyId>       revokes one key

You cannot mint a key with a key.

Use

Section titled “Use”
Authorization: Bearer dk_…

A key resolves to the same identity as a session. Every write acts as the key’s owner; handles are resolved server-side from the verified identity, never from a request body or a tool argument. A key can only write its own channel.

Properties

Section titled “Properties”
  • sha-256 hashed at rest; revocable.
  • dk_ and db_live_ are one family: either prefix works on the hub (denpa.ai) and the Hono API service.
  • New keys carry permissions: ["read","signal"] and a tier (free · builder · pro · enterprise). Recorded, not yet enforced at the edge — design your client to tolerate 429.

Where a key is required

Section titled “Where a key is required”
Needs a keyOpen
POST /api/predictionsevery /api/network/* read
POST/DELETE /api/m/[id]/streamsmarket context, price history, featured
POST/DELETE /api/streamer/signal/api/situations
GET /api/network/field-record/mefield records by handle
POST /api/mcp (key-gated tools)initialize, tools/list
POST /api/signals/[id]/events (owner)GET …/events