The Extreme Energy Incorporated API — previously a single BannedUsers.txt endpoint on Netlify — has been fully replaced by the UT GBS System. The legacy endpoint remains live and updated for backward compatibility. New integrations should use the JSON endpoints at database.unknown-technologies.us, which support richer data and include the new group blacklist endpoint.
What Changed
EEI API
A single endpoint existed: eei-api-533b.netlify.app/api/BannedUsers.txt — a raw text file manually edited and pushed to GitHub. It used a proprietary non-JSON format, meaning only a User ID and ban reason could ever be stored. No date, no moderator, no metadata of any kind. No group blacklist system existed.
GBS System
Two proper JSON endpoints now exist: BannedUsersAPI.json and BannedGroups.json. Bans now store User ID, ban reason, date, moderator, and any additional metadata. Group blacklisting is a brand new capability that did not exist before.
New System Capabilities
Proper Administration Panel
Staff can manage bans and group blacklists through a dedicated web panel. No more committing to repositories or editing raw files.
Scalable Staff Management
Add or remove staff members freely without worrying about messing up internals. Each staff account is scoped and independently managed.
Proper JSON Format ★ NEW
The old EEI API used a proprietary non-JSON text format — the only data it could hold was a User ID and a ban reason. The GBS System outputs standard JSON, allowing bans to carry a ban date, responsible moderator, and any additional fields we choose to add in the future.
Group Blacklist System ★ NEW
The old EEI API had no group blacklist system at all. The GBS System introduces this as a first-class feature with its own dedicated endpoint — BannedGroups.json — managed directly through the admin panel with full validation and audit trails.
Full Backward Compatibility
All old EEI API domains and endpoint paths are preserved and actively maintained. Legacy integrations continue to work without modification.
Improved Reliability
The new infrastructure is far more stable and resilient than the previous GitHub-backed system. Data integrity is enforced at the system level.
API Compatibility Reference
| Endpoint / Domain | EEI Status | GBS Status | Notes |
|---|---|---|---|
| eei-api-533b.netlify.app/api/BannedUsers.txt | Legacy .txt | Still Active | Maintained for backward compatibility |
| database.unknown-technologies.us/api/BannedUsersAPI.json | Did Not Exist | Recommended | Full JSON — ID, reason, date, moderator + more |
| database.unknown-technologies.us/api/BannedGroups.json | Did Not Exist | New Feature | Entirely new — group blacklisting not in EEI API |
Staff who previously managed the GitHub repository should migrate to the new GBS admin panel.
You will be issued an individual staff account. The old workflow of committing
.txt files is discontinued —
all changes must be made through the panel going forward to maintain data integrity and audit logs.