How Kiro operates The Trinity Beast Infrastructure — pre-built API routines, deployment automation, and session-persistent context.
The Kiro Command Center (KCC) is a set of pre-built operational routines that Kiro uses to manage The Trinity Beast Infrastructure (TBI). It consists of a bash script (scripts/kcc.sh) with 25+ commands, a steering file (.kiro/steering/kiro-command-center.md) that loads automatically at the start of every session, and a live web dashboard at cpmp-site.org/docs/dashboard.html.
Instead of building curl commands from scratch for every health check, deployment, or verification, Kiro calls the KCC script. This eliminates repetitive command construction, ensures consistency, and reduces the chance of errors during operations.
In short: The TBCC is Cory's Command Center (browser-based, WebSocket relay to Neo). The KCC is Kiro's Command Center (script-based, direct API calls from the development environment). Both operate the same infrastructure through the same API endpoints with the same admin key.
During a typical session, Kiro performs dozens of operations against The TBI — health checks after deployments, endpoint verification after code changes, cluster stats during monitoring, payment link status checks, and feed status reviews. Each of these requires:
https://api.cpmp-site.org for LPO, https://lrs.cpmp-site.org for LRS)X-Admin-Key headerWithout the KCC, every operation is a hand-built curl command. With the KCC, it's a single call:
# Without KCC (manual)
curl -s -H "X-Admin-Key: tbmc-admin-..." https://api.cpmp-site.org/admin/cluster-stats | python3 -m json.tool
# With KCC (one command)
bash scripts/kcc.sh cluster-stats
The steering file ensures Kiro always has the admin key, resource names, and operational procedures loaded in context — even after a session restart or context compaction.
Located at .kiro/steering/kiro-command-center.md with inclusion: auto. This means it is loaded into Kiro's context at the start of every session — no manual activation required. It contains:
Located at scripts/kcc.sh. A standalone bash script with 31 commands that encapsulates all operational API calls. Each command:
resp.data)All commands are invoked as bash scripts/kcc.sh <command>.
Checks all services — LPO health, LRS health, and cluster stats (3/3 nodes reporting). This is the first command run after every ECS deployment.
bash scripts/kcc.sh health
# Output:
# LPO: ✅ [LPO] [us-east-2] [BeastMirror] [/health] [200]
# LRS: ✅ [LRS] [us-east-2] [BeastLRS] [/health] [200]
# Cluster: Nodes: 3/3
# BeastMain: published 2026-04-26T19:04:29Z
# BeastMirror: published 2026-04-26T19:04:29Z
# BeastLRS: published 2026-04-26T19:04:28Z
Verifies the last nightly sync job ran successfully. Pulls the most recent log stream from CloudWatch (/aws/ecs/trinity-beast-sync) and displays run time (EST), completion status, duration, cache totals, and per-category sync counts (price logs, usage logs, API keys, app params, cleanup). Run this every morning right after health.
bash scripts/kcc.sh sync-check
# Output:
# Run Time: April 28, 2026 at 01:00 AM EST
#
# Status: ✅ Sync complete
# Duration: 186.909018ms
# Cache: 3285260 logs in Cache
#
# Sync Results:
# Price logs: 72 new logs loaded
# Usage logs: 19 entries written to Cache
# API keys: 2 keys written to Cache
# App params: 60 params written to Cache
# Cleanup: 🟢 Pruned 0 old logs (>93 days)
Hits 16 key endpoints (6 public + 10 admin) and reports the HTTP status code for each. Used after major changes to confirm nothing is broken.
bash scripts/kcc.sh verify
# Output:
# Public Endpoints:
# ✅ GET /health (LPO) — 200
# ✅ GET /health (LRS) — 200
# ✅ GET /exchanges — 200
# ✅ GET /asset-categories — 200
# ...
# Admin Endpoints:
# ✅ GET /admin/config — 200
# ✅ GET /admin/cluster-stats — 200
# ...
Returns the full cluster-wide metrics snapshot — all 24 counters aggregated across all 4 containers via ElastiCache pipeline read.
bash scripts/kcc.sh cluster-stats
Shows all 16 payment links with their enabled status, click counts, and Stripe URLs. Used to verify link configuration before and after Stripe setup.
bash scripts/kcc.sh payment-links
# Output:
# Total: 16 links
# Type Tier Enabled Clicks URL
# subscription pro ✅ 42 https://buy.stripe.com/xxx...
Shows the connection status of all 6 exchange WebSocket feeds with subscription counts and stale asset counts.
bash scripts/kcc.sh feed-status
# Output:
# coinbase_ws ✅ Connected Subs: 12 Stale: 0
# gemini_ws ✅ Connected Subs: 12 Stale: 0
# kraken_ws ✅ Connected Subs: 12 Stale: 0
# gateio_ws ✅ Connected Subs: 12 Stale: 0
# cryptocom_ws ✅ Connected Subs: 12 Stale: 0
# okx_ws ✅ Connected Subs: 12 Stale: 0
Full ECS deployment pipeline — Docker build (no-cache), ECR tag, ECR push, force deploy all 4 services. The most common deployment command.
bash scripts/kcc.sh deploy-ecs
# Builds → Tags → Pushes → Force deploys main, mirror, LRS
# Then: bash scripts/kcc.sh health (after ~40s)
Uploads HTML files to S3 and invalidates CloudFront. Automatically strips the cpmp-redesign/ prefix to determine the S3 path.
bash scripts/kcc.sh deploy-site cpmp-redesign/docs/Trinity-Beast-API-Reference.html
bash scripts/kcc.sh deploy-site cpmp-redesign/subscribe-listener.html cpmp-redesign/docs/index.html
Lists all 16 system profiles with their key parameters (QPS, burst, TTL, DB pool size).
bash scripts/kcc.sh profiles
Shows the current application parameters — cache TTL, prewarm intervals, pool sizes, demo key, etc.
bash scripts/kcc.sh config
Collects all infrastructure metrics (endpoints, feeds, cluster, Valkey, Lambda, sync, SQS queue, website analytics) and stores them as a single JSON blob in Valkey (kcc:daily key, 24h TTL). This is the data source for both the CLI daily command and the KCC Live Dashboard.
bash scripts/kcc.sh daily-collect
Renders the compact daily status dashboard from the Valkey cache. If no cached data exists, it auto-runs daily-collect first. Shows services, ECS nodes, Valkey health, Lambda, nightly sync, SQS queue depth, and 7-day website analytics.
bash scripts/kcc.sh daily
# Output:
# ════════════════════
# KCC — May 02 02:11PM EDT
# ════════════════════
# ─── Services ───
# ✅ LPO ✅ LRS ✅ Web
# Cluster: 3/3
# ─── SQS Usage Queue ───
# ✅ Pending: 0 In-flight: 0
# ─── Website (7d) ───
# Total 14,250 2.2GB Avg 2,035/day
Security dashboard — CloudFront WAF (24h blocks), API WAF (per-rule breakdown), GuardDuty threat detection, CloudWatch security alarms, and application rate limiting stats.
bash scripts/kcc.sh security
Reloads all application parameters from Aurora → local cache + ElastiCache, re-parses prewarm asset lists, flushes prices, and resets all timers across all containers. Use after changing application_parameters in the database.
bash scripts/kcc.sh force-deploy
Validates all 161 prewarm assets across 6 exchanges against their live APIs. Reports any dead/delisted assets that need replacement. Run periodically — exchanges delist and rebrand assets more often than expected.
GET /admin/eam/audit (async, results in ~12s) and renders results visually — per-exchange bars, inline Disable/Replace buttons for dead assets, and one-click drift remediation. Use the CLI command for terminal sessions; use the panel for interactive maintenance.
bash scripts/kcc.sh prewarm-audit
# Output:
# ✅ COINBASE 26/26 OK
# ✅ CRYPTOCOM 24/24 OK
# ✅ GATEIO 24/24 OK
# ✅ GEMINI 25/25 OK
# ✅ KRAKEN 26/26 OK
# ✅ OKX 36/36 OK
Rebuilds the multi-lingual full-text search index from all 32 documents across 12 languages (384 total) plus daily operations reports (English only, 30-day rolling archive). Fetches each doc from CloudFront, parses HTML into sections, and stores per-language indexes in Valkey. Run after deploying new or updated documents. The nightly sync also triggers this automatically.
Search features: Paginated results (9 per page), multi-lingual scoring, daily report indexing, and an interactive Search Demo showing the English → Japanese flow.
bash scripts/kcc.sh build-search
Pushes all 12 language JSON files from cpmp-redesign/lang/ to Valkey (lang:{code} keys). The i18n system's primary source is the API (/public/lang/{code}), which reads from Valkey. If language files are edited locally and deployed to S3 but NOT pushed to Valkey, the API serves stale data and new i18n keys won't appear on the website. Run after any edit to language JSON files.
bash scripts/kcc.sh push-langs
Validates that TBI-CHUNK markers are preserved through the translation reassembly pipeline for a given document. Checks that chunk count in the source matches chunk count in the reassembled output. Run before submitting a document to the translation engine to confirm chunk integrity.
bash scripts/kcc.sh delta-validate Trinity-Beast-API-Reference.html
# Output:
# Source chunks: 12
# Output chunks: 12
# ✅ Chunk markers preserved — safe to submit
Scans a document and reports the size of each chunk between TBI-CHUNK markers. Flags any chunks that exceed the translation engine's size policy (15 KB baseline, 18 KB max, 12 KB for dense/code-heavy sections). Also suggests where to add new markers if any chunk is over-limit. Run before submitting large or recently updated documents to the translation engine.
bash scripts/kcc.sh chunk-size cpmp-redesign/docs/Trinity-Beast-API-Reference.html
# Output:
# Chunk 1: 11.2 KB ✅
# Chunk 2: 14.8 KB ✅
# Chunk 3: 17.1 KB ⚠️ approaching limit
# Chunk 4: 9.3 KB ✅
# Chunk 5: 19.4 KB 🛑 OVER LIMIT — add TBI-CHUNK near line 412
Forensic trace of an IP address — WAF blocks (last 24h sampled requests) and usage logs from Aurora. Shows what the IP was doing and whether WAF caught it.
bash scripts/kcc.sh trace-ip 45.148.10.247
Forensic trace of an API key — owner details (email, name, tier), recent activity (last 50 calls), and unique IPs used.
bash scripts/kcc.sh trace-key demo-public-2026-03-01-abc123
Full account trace — user account, API keys, transactions, and support tickets for an email address.
bash scripts/kcc.sh trace-email user@example.com
Shows WAF blocks by rule (last 24h) and GuardDuty findings (severity ≥ MEDIUM). Quick threat visibility without the full security dashboard.
bash scripts/kcc.sh threat-log
Current defense posture — manually blocked IPs (WAF IP set) and any firing CloudWatch alarms.
bash scripts/kcc.sh threat-status
Adds an IP to the WAF block list (trinity-beast-blocked-ips IP set). Creates the IP set if it doesn't exist. Immediate effect — all requests from this IP get 403.
bash scripts/kcc.sh block-ip 1.2.3.4
Removes an IP from the WAF block list.
bash scripts/kcc.sh unblock-ip 1.2.3.4
Immediately revokes an API key — sets status to 'revoked' in Aurora and deletes the cached key from ElastiCache. All subsequent requests with this key get 403 Forbidden.
bash scripts/kcc.sh kill-key abc123-compromised-key
Sends a threat warning email to the subscriber who owns the specified API key. Uses the ThreatWarning SES template. Does not revoke the key — this is a first-strike warning.
bash scripts/kcc.sh warn-subscriber abc123-key "Unusual request patterns detected from your API key"
Full subscriber termination — revokes key, cancels Stripe subscription (prorated refund), blocks all source IPs, and sends termination notice via SES. Irreversible. Generates a violation ID for audit trail.
bash scripts/kcc.sh terminate-subscriber abc123-key "Repeated abuse after warning"
Generates a new admin key, updates Aurora application_parameters, flushes the old key from Valkey, force-deploys params to all containers, and self-updates the KCC script. The old key is immediately invalid. Use when the admin key may be compromised.
bash scripts/kcc.sh rotate-admin-key
# Output:
# Old key: tbmc-admin-ec...e380
# New key: tbmc-admin-7f3a...b291
# [1/4] Updating Aurora application_parameters...
# [2/4] Flushing old key from Valkey...
# [3/4] Force deploying params to all containers...
# [4/4] Updating KCC script with new key...
# ✅ Admin key rotated successfully
Creates a WAF rule (priority 0 — highest) that blocks ALL /admin/* requests unless they originate from the specified IP. Emergency use — locks out everyone except you. To find your IP: curl -s ifconfig.me
bash scripts/kcc.sh lockdown-admin 73.42.156.89
# Only 73.42.156.89 can now reach /admin/* endpoints
# All other IPs get blocked at WAF before reaching the server
Removes the admin lockdown WAF rule, restoring normal admin access for all authenticated requests.
bash scripts/kcc.sh unlock-admin
Adds a geo-match WAF rule to the ALB that blocks ALL traffic from specified countries (ISO 3166-1 alpha-2 codes). Idempotent — running again replaces the previous list. Use during sustained regional attacks.
bash scripts/kcc.sh block-country "RU CN"
bash scripts/kcc.sh block-country "RU CN IR KP"
Removes the country geo-block rule entirely, allowing all geographic traffic.
bash scripts/kcc.sh unblock-country
Appends a release note to the weekly accumulator in Valkey (autoops:release-notes:week). These notes are read by the digest Lambda on Monday morning and included as a "What's New" section in the weekly subscriber newsletter. Run at the end of each session to capture subscriber-facing improvements.
bash scripts/kcc.sh release-notes "Branded HTML email notifications for all AutoOps alerts"
# Output:
# ✅ Release note added (#3 this week)
# Branded HTML email notifications for all AutoOps alerts
Shows all accumulated release notes for the current week. Use to review what will appear in Monday's newsletter.
bash scripts/kcc.sh release-notes-show
# Output:
# 1. [2026-05-10] Branded HTML email notifications via SES
# 2. [2026-05-10] SNS-to-Lambda notification pipeline
# 3. [2026-05-10] Weekly newsletter Gmail-compatible dark theme
#
# Total: 3 notes
Clears all accumulated release notes. Done automatically after the weekly newsletter sends successfully. Manual use only needed if you want to start fresh mid-week.
bash scripts/kcc.sh release-notes-clear
Escalation Sequence (Admin Key Compromise):
bash scripts/kcc.sh lockdown-admin $(curl -s ifconfig.me) — lock everyone else out NOWbash scripts/kcc.sh rotate-admin-key — invalidate the compromised keybash scripts/kcc.sh threat-log — check what damage was donebash scripts/kcc.sh trace-ip <attacker_ip> — forensicsbash scripts/kcc.sh block-ip <attacker_ip> — permanent banbash scripts/kcc.sh unlock-admin — restore normal access once safeThe steering file at .kiro/steering/kiro-command-center.md is marked with inclusion: auto, which means it is loaded into Kiro's context automatically at the start of every session. This ensures Kiro always has access to:
| Information | Purpose |
|---|---|
| Admin API Key | Authenticate against all admin endpoints without asking |
| LPO / LRS Base URLs | Construct API calls without looking up DNS |
| S3 Bucket Name | Deploy website files to the correct bucket |
| CloudFront Distribution ID | Invalidate the CDN cache after deployments |
| ECR Repository | Push Docker images to the correct registry |
| ECS Cluster + Service Names | Force deploy the correct services |
| Operational Rules | Always health check after deploy, always verify after changes |
Context Persistence: Even if the conversation is compacted due to context window limits, the steering file is reloaded automatically. This means Kiro never loses access to the operational essentials — the admin key, resource names, and procedures survive context compaction.
A typical day starts with a morning check, then moves into the code change → deploy → verify cycle:
~/daily-reports/tbi-ops-YYYY-MM-DD-session-N.html from the last session to pick up context, pending items, and roadmap ideasbash scripts/kcc.sh daily-collect then bash scripts/kcc.sh daily (full infrastructure snapshot — services, ECS, Valkey, Lambda, sync, SQS queue, analytics)bash scripts/kcc.sh prewarm-audit (validate 150 assets across 6 exchanges)bash scripts/kcc.sh threat-log + bash scripts/kcc.sh threat-status (WAF blocks, GuardDuty, alarms, block list)~/daily-reports/tbi-ops-YYYY-MM-DD-session-N.html and S3, open in browsertbi-ops-*)Every session produces an operational report — an HTML document that serves as both a health snapshot and a session log. Reports are stored locally and on S3, accessible via cpmp-site.org/daily-reports/.
| Attribute | Value |
|---|---|
| Naming | tbi-ops-YYYY-MM-DD-session-N.html |
| Local path | ~/daily-reports/ |
| S3 path | s3://trinity-beast-website-east2/daily-reports/ |
| Public URL | cpmp-site.org/daily-reports/ |
| Language | English (Google Translate widget on every report for 130+ languages) |
| Retention | 30 days (default — extensible, not hardcoded) |
Each report contains:
go build ./cmd/server/bash scripts/kcc.sh deploy-ecsbash scripts/kcc.sh health (confirm 3/3 nodes)bash scripts/kcc.sh verify (confirm all 200s)bash scripts/kcc.sh deploy-site cpmp-redesign/docs/...This entire cycle takes about 3 minutes of active work plus ~40 seconds of waiting for ECS. Without the KCC, each step would require constructing individual commands with the correct URLs, headers, and parameters.
The KCC Live Dashboard is a browser-based visual interface at cpmp-site.org/docs/dashboard.html that renders the same data collected by daily-collect. It provides:
The dashboard is also linked from the TBCC CloudWatch Monitoring widget for quick access during operations.
The Trinity Beast Infrastructure has two command centers, each designed for a different operator:
| Aspect | TBCC (Cory's) | KCC (Kiro's) |
|---|---|---|
| Operator | Cory Dean Kalani | Kiro (AI Development Environment) |
| Interface | Browser-based dashboard | Bash script + steering file + Live Dashboard |
| Access Method | WebSocket relay to Neo MacBook | Direct API calls from dev environment |
| Terminal | Built-in browser terminal | IDE terminal (Kiro's tool execution) |
| Widgets | Newsletter, Support, Email, CloudWatch, Stripe, Testing, AWS Ops, Partners, Exchange Manager, Cluster Health | 10 bash commands covering health, sync, verify, deploy, stats |
| Authentication | Admin key stored in localStorage | Admin key in steering file (auto-loaded) |
| Deployment | Copy commands → paste in local terminal | Direct execution via deploy-ecs and deploy-site |
| Persistence | Browser session | Steering file survives context compaction |
| URL | cpmp-site.org/admin/trinity-beast-command-center.html | scripts/kcc.sh |
Same API, different interfaces. Both command centers call the same endpoints with the same admin key. The TBCC is optimized for visual monitoring and manual operations. The KCC is optimized for automated, repeatable operations during development sessions.
The KCC includes a full set of commands for operating the custom Bedrock-powered translation engine. This engine translates all 32 technical documents into 11 languages using sentinel preprocessing to protect code blocks, Mermaid diagrams, and brand terms. Never use AWS Translate for document translation — it corrupts code blocks and brand terms.
Cost guardrails: $600/day spend cap (autoops:bedrock:spend:daily) + 50M combined token/day secondary cap (autoops:bedrock:tokens:input:daily + autoops:bedrock:tokens:output:daily). Both reset at midnight UTC via 24h TTL. Kill switch: SET autoops:bedrock:kill 1 in Valkey to halt all translation immediately.
Enqueues a translation job. The engine handles everything: sentinel preprocessing, Bedrock translation, S3 deployment, CloudFront invalidation, search index rebuild, and email notification. Fire and forget — one API call does it all.
# Single document, all 11 languages
curl -s -X POST -H "X-Admin-Key: $ADMIN_KEY" -H "Content-Type: application/json" \
-d '{"docs":["Trinity-Beast-API-Reference.html"],"langs":"all"}' \
"$LPO_BASE/admin/translate" | jq .
# Multiple documents, specific languages
curl -s -X POST -H "X-Admin-Key: $ADMIN_KEY" -H "Content-Type: application/json" \
-d '{"docs":["Trinity-Beast-API-Reference.html","Trinity-Beast-Architecture-Guide.html"],"langs":["es","pt","fr"]}' \
"$LPO_BASE/admin/translate" | jq .
# Delta mode — skip pairs where translated S3 file is newer than source (saves up to 90%)
curl -s -X POST -H "X-Admin-Key: $ADMIN_KEY" -H "Content-Type: application/json" \
-d '{"docs":["Trinity-Beast-API-Reference.html"],"langs":"all","options":{"delta":true}}' \
"$LPO_BASE/admin/translate" | jq .
# With idempotency key (safe to retry)
curl -s -X POST -H "X-Admin-Key: $ADMIN_KEY" -H "X-Idempotency-Key: api-ref-2026-05-27" \
-H "Content-Type: application/json" \
-d '{"docs":["Trinity-Beast-API-Reference.html"],"langs":"all"}' \
"$LPO_BASE/admin/translate" | jq .
Limits: Max 6 docs per request (multiples-of-3 convention). Max 3 active jobs (additional queue in SQS, depth 12). Max 12 languages per request. Typical cost: ~$1.65 per doc-language pair, ~$18 for 1 doc × 11 langs.
Real-time per-pair progress from Valkey. Shows each language pair's status (pending, in_progress, completed, failed), token counts, and cost.
curl -s -H "X-Admin-Key: $ADMIN_KEY" "$LPO_BASE/admin/translate/status/{job_id}" | jq .
Shows all active and queued jobs with their current state.
curl -s -H "X-Admin-Key: $ADMIN_KEY" "$LPO_BASE/admin/translate/queue" | jq .
Translation engine health snapshot — daily spend, token usage (input + output vs 50M limit), active job count, queue depth. The KCC Live Dashboard also shows this data in the Translation Engine card.
curl -s -H "X-Admin-Key: $ADMIN_KEY" "$LPO_BASE/admin/translate/health" | jq .
# Key fields in response:
# daily_spend_usd — dollars spent today
# daily_input_tokens — input tokens consumed today
# daily_output_tokens — output tokens consumed today
# daily_token_limit — 50,000,000 (50M combined cap)
# active_jobs — currently running Step Functions
# queue_depth — jobs waiting in SQS
Last 50 completed jobs from Aurora — the permanent ledger. Includes job ID, docs, languages, total cost, duration, and completion time.
curl -s -H "X-Admin-Key: $ADMIN_KEY" "$LPO_BASE/admin/translate/history" | jq .
Stops the Step Function immediately. Already-completed pairs are not rolled back — S3 files written before cancellation remain.
curl -s -X POST -H "X-Admin-Key: $ADMIN_KEY" "$LPO_BASE/admin/translate/cancel/{job_id}"
Retries only the failed language pairs from a partial job. Successful pairs are not re-translated. Cost-efficient recovery from partial failures.
curl -s -X POST -H "X-Admin-Key: $ADMIN_KEY" "$LPO_BASE/admin/translate/retry-failed/{job_id}"
Before submitting any document to the translation engine, run these two checks:
Reports the size of each chunk between TBI-CHUNK markers. Policy: 15 KB baseline, 18 KB max, 12 KB for dense/code-heavy sections. Flags over-limit chunks and suggests where to add markers. Do not submit and hope — verify first.
bash scripts/kcc.sh chunk-size cpmp-redesign/docs/Trinity-Beast-API-Reference.html
Confirms that TBI-CHUNK markers survive the translation reassembly pipeline. Chunk count in source must match chunk count in output. Run before submitting documents that have been recently edited.
bash scripts/kcc.sh delta-validate Trinity-Beast-API-Reference.html
| Component | Resource | Purpose |
|---|---|---|
| Worker | ECS Fargate task tbi-translate-worker-task (Python 3.11, 1 vCPU / 3 GB) | Sentinel preprocessing, Bedrock translation, validation |
| Deploy Lambda | tbi-translate-deploy (Go, 1770 MB, 60s) | Batch CloudFront invalidation |
| Finalize Lambda | tbi-translate-finalize (Go, 1770 MB, 180s) | Search rebuild, SNS notification, state transition |
| Step Function | tbi-translation-orchestrator (v3.0: PerLang Map) | One container per language, all docs sequentially |
| SQS Queue | trinity-beast-translation-queue | Decouples submission from execution |
| EventBridge Pipe | tbi-translate-pipe | SQS → Step Function (no glue Lambda) |
| Aurora Tables | translation_jobs, translation_job_events | Permanent ledger + audit log |
| Valkey Keys | tx:job:{id}, tx:active, tx:history, autoops:bedrock:spend:daily | Live state + cost tracking |
The KCC calls these endpoints through the unified messaging envelope. All admin endpoints require the X-Admin-Key header.
| Command | Endpoints Called | Auth |
|---|---|---|
health | GET /health (LPO + LRS), GET /admin/cluster-stats | None + Admin |
sync-check | CloudWatch Logs: describe-log-streams, get-log-events on /aws/ecs/trinity-beast-sync | AWS credentials |
verify | 16 endpoints (6 public + 10 admin) | Mixed |
cluster-stats | GET /admin/cluster-stats | Admin |
payment-links | GET /admin/payment-links | Admin |
feed-status | GET /admin/feed-status | Admin |
deploy-ecs | Docker + ECR + ECS (AWS CLI, not HTTP) | AWS credentials |
deploy-site | S3 + CloudFront (AWS CLI, not HTTP) | AWS credentials |
profiles | GET /admin/profiles | Admin |
config | GET /admin/config | Admin |
trace-ip | WAF get-sampled-requests + POST /admin/sql | AWS + Admin |
trace-key | POST /admin/sql (2 queries) | Admin |
trace-email | POST /admin/sql (4 queries) | Admin |
kill-key | POST /admin/sql-batch + POST /admin/valkey | Admin |
terminate-subscriber | POST /admin/sql + Stripe API + WAF + SES | Admin + AWS + Stripe |
rotate-admin-key | POST /admin/sql-batch + POST /admin/valkey + GET /admin/force-deploy-params | Admin |
lockdown-admin | WAF create-ip-set / update-web-acl | AWS credentials |
block-country | WAF update-web-acl (geo-match rule) | AWS credentials |
push-langs | S3 sync + POST /admin/valkey (SET lang:{code}) | AWS + Admin |
delta-validate | Local file read + chunk marker count comparison | None |
chunk-size | Local file read + awk chunk size analysis | None |
translate (submit) | POST /admin/translate | Admin |
translate (status) | GET /admin/translate/status/{id} | Admin |
translate (queue) | GET /admin/translate/queue | Admin |
translate (health) | GET /admin/translate/health | Admin |
translate (history) | GET /admin/translate/history | Admin |
translate (cancel) | POST /admin/translate/cancel/{id} | Admin |
translate (retry) | POST /admin/translate/retry-failed/{id} | Admin |