Skip to main content
Use the Esheria API Dashboard when you want to start without operator help. The dashboard is available at https://dashboard.esheria.ai/ and is the recommended path for account setup, token management, usage review, billing, and first-request testing.
The dashboard manages access to the Regulatory Pack API. API responses remain source-backed regulatory workflow data, not legal advice.

​
What You Can Do

Create an account

Sign up with a verified Google or GitHub identity. Public email/password signup is disabled until production email verification and recovery exist.

Create API tokens

Create data tokens for services, integrations, local development, CLI, and MCP hosts.

Manage token lifecycle

List active tokens, copy token prefixes for debugging, and revoke tokens that should no longer work.

Track credits and usage

Review remaining credits, recent usage, endpoint families, status codes, charged credits, and trace IDs.

Manage billing

Start Stripe Checkout for top-ups or subscriptions and review the current subscription state.

Use the playground

Test pack discovery, claim verification, obligations, applicability, evidence, filings, penalties, graph queries, and exports from the browser.

​
First Dashboard Flow

1

Open the dashboard

Go to https://dashboard.esheria.ai/ and choose Sign up with Google or GitHub. Esheria provisions free Sandbox credits only for verified provider email addresses.
2

Create or resolve your workspace

After sign-in, the dashboard resolves your workspace and shows your current credit balance, token state, usage, and available API workflows.
3

Create a data token

Open Settings, choose up to two Sandbox packs, then open API Tokens, create a data token, and store the returned token immediately. The token secret is shown once and cannot be retrieved later.
4

Set local environment variables

Store the token in your shell, CI secret store, or server secret manager as ESHERIA_API_KEY.
5

Run the first request

Use the dashboard playground, curl, or the esheria CLI to list packs and confirm the token works.

​
Token Types

Dashboard users normally create data tokens. Data tokens call entitled Regulatory Pack API routes and spend workspace credits when billing is enabled. Management tokens are used by the dashboard server and trusted automation for workspace, token, billing, and checkout administration. Do not put management tokens in browser code, public repositories, notebooks, support tickets, or client-side applications.

​
Billing And Credits

Credits belong to the workspace, not to individual tokens. Creating more tokens does not create more free credits. The dashboard billing pages show:
  • current credit balance
  • free-credit and paid-credit grants
  • recent usage and charged credits
  • available top-up or subscription plans
  • checkout success and cancel states
  • current subscription state and cancellation controls when available
Protected API requests are metered by endpoint family. Health checks, readiness checks, token management, billing reads, and checkout-session creation are not billable. New verified workspaces receive 500 credits valid for 14 days and may select two published packs. Paid plans expand included credits, pack limits, features, and authenticated requests per minute. Billing cards and Checkout use exact server-returned SKUs; hidden browser fields never determine a price or grant.
If credits are exhausted, billable API calls return HTTP 402 with credits_exhausted. Add credits or update the workspace plan before retrying production traffic.

​
Usage And Activity

Use Usage and Activity Logs to debug integration behavior without exposing secrets. Rows include fields such as endpoint family, method, path, pack ID, token label or prefix, status code, charged credits, pricing rule version, and trace_id. Keep the trace_id with support tickets, application logs, and user-visible decisions. It is the fastest way to connect a downstream answer to the API request that produced it.

​
Workspace Settings

Use Workspace Settings for customer-visible account details such as display name, billing contact email, and plan-allowed pack selection. Subscription management lives under Billing. Team invitations and enterprise SSO are deployment-specific. If your team needs an organization rollout, contact Esheria from the dashboard sign-in page.

​
CLI Equivalents

The dashboard is the easiest self-serve entry point, but the CLI exposes the same token and billing primitives for automation:
MCP does not expose token or billing mutation tools. Use the dashboard or CLI for token and billing management before configuring esheria-mcp.

​
Safety Checklist

  • Create separate data tokens for development, staging, production, and each major integration.
  • Store token secrets in a server secret manager or local environment variable.
  • Revoke tokens immediately when they are exposed or no longer needed.
  • Do not place API tokens in browser bundles, screenshots, documentation, issue trackers, logs, or agent transcripts.
  • Use dashboard usage rows and trace_id values for debugging instead of raw token secrets.