Tritonix.ai

Help Center

  • Introduction
  • AI Agent Guide
  • Tritonix Investment Agent
  • Asset Panel
  • Calendar Panel
  • Screener Panel
  • Web Search Panel
  • Document Panel
  • Skill Panel
  • Scheduled Tasks
  • Publish Ideas
  • Social Media Agent
  • Connectors
  • Copy Trade
  • Swing Trade Bot
  • Day Trade Bot
  • AI Technical Analysis
  • AI Consensus Stock Pick
  • Institutional Smart Money
  • How to Use the Blog
  • API Key Management
  • Agent Public API

Help Center

API Key Management

API Key Management

Use API Keys when you want to call Tritonix from your own server-side scripts, cron jobs, or backend services. API Keys are tied to your Tritonix account, and every successful API call consumes Credits from that account.

Where to Manage API Keys

Open:

  • Account Settings
  • API Keys

On this page you can:

  • create a new API key
  • view your active and revoked keys
  • inspect recent API request activity
  • review request counts, success rate, token usage, and Credits used

Creating an API Key

  1. Go to Account Settings → API Keys
  2. Enter a descriptive name, such as Premarket stock picker
  3. Click Create API Key
  4. Copy the generated secret immediately

The full API key is shown only once after creation.

Security Model

Tritonix does not store raw API key secrets in the database.

Instead:

  • the server generates the secret once
  • only a hashed version is stored
  • the UI stores and displays only the key prefix for later identification

If you lose the full secret, create a new key and revoke the old one.

Revoking an API Key

Revoking a key immediately prevents any new requests authenticated with that key.

Use revoke when:

  • a key has been exposed
  • a script or automation is being retired
  • you want to rotate credentials

Revoked keys remain visible in the dashboard for audit history, but they can no longer be used.

Request Analytics

The API Keys page includes lightweight request analytics sourced from the public API request log.

You can review:

  • total requests
  • success rate
  • Credits used
  • total tokens
  • active key count
  • recent request logs

Request logs intentionally store only operational metadata. Tritonix does not persist full request prompts or model responses for the public API.

Credits and Billing

Public API usage follows the same Credits system as the product:

  • if your balance is <= 0 at request start, the request is rejected with 402 insufficient_credits
  • if your balance is positive at request start, the request may run
  • final deduction happens after execution using the same Credits logic as the rest of the platform

In some cases, final deduction may exceed the remaining balance and create account debt according to the platform's existing Credits rules.

Authentication Format

Send your API key as a Bearer token:

Authorization: Bearer txk_your_secret_here

Use API Keys only in trusted server-side environments. Do not embed them in public frontend code, browser extensions, or client-side mobile bundles.

Best Practices

  • create separate keys for different automations
  • name keys clearly by workflow or environment
  • rotate keys when team access changes
  • revoke unused keys promptly
  • keep secrets in environment variables or a secret manager

Related Docs

  • Agent Public API