Sandbox version
For experimental use only. Proceed with caution.
Portal
The Honeycluster control plane — accounts, projects, API keys, credits, and billing.

The Portal is where you manage everything that isn't XRPL data — your Honeycluster account, the projects you own, the API keys each project has issued, and the credit balance backing them.

Live at portal.honeycluster.io.

What the Portal gives you
##
  • Account management — sign in, set up 2FA, link OAuth providers (Google, GitHub, X), and manage your email/password profile.
  • Projects — create logical groupings that own their own credit balance, rate-limit tier, and set of keys. Create separate projects for staging vs. production so usage is isolated.
  • API keys — mint new keys, label them, and revoke leaked ones. Keys only surface once at creation time; store the value immediately.
  • Credits — see real-time balance, cycle-over-cycle usage, and tier upgrades. The dashboard shows the same numbers the API returns in X-Credits-Remaining headers.
  • Usage analytics — per-key and per-project request counts, credit cost breakdowns, and error rates. Useful for finding expensive call patterns before they show up on the invoice.
  • Onboarding — guided setup for first-time users: account creation, project creation, first key, first call.
Common workflows
##
Issuing your first key
###
  1. Sign in at the Portal.
  2. Projects → New Project — give it a name and pick a tier.
  3. Inside the project, Keys → New Key — label it (e.g. production-indexer), copy the value, and store it in your secret manager.
  4. Plug the key into your app's environment. See Authentication for the exact header shape.
Rotating a leaked key
###
  1. Keys → New Key — mint a replacement.
  2. Deploy the new key to your runtime.
  3. Once the usage dashboard shows the old key at zero traffic, click Revoke on it. Revocation takes effect across the edge proxy in seconds.
Upgrading a project's tier
###

A project's tier controls its rate-limit ceiling, monthly credit cap, and the action taken when the cap is hit (block / throttle / warn / allow). Change it at any time from Project → Billing → Tier. See Rate Limits for the semantics of each action.

Not for humans only
##

The portal surfaces everything via tRPC so you can automate it from your own scripts if you need to. Key creation, project setup, and usage queries all have typed endpoints — the portal UI is just one consumer.

If you're building internal tooling that needs to mint keys programmatically (CI pipelines, dynamic tenant provisioning), contact support to enable the management API for your account.