Paid Tier
Paid Tier
The free tier is for checking the current live version, reading public docs, and using the subset of offsets currently exposed to everyone.
Premium access is for users who need complete, current data and tools that fit into an existing workflow.
Support and paid-tier questions: Telegram, Discord: monkrel, or the contact me back form.
What premium unlocks
War Thunder access
Your license covers War Thunder. Premium applies to the War Thunder endpoints.
Complete offset responses
Free users only receive the public allow-list. Premium users receive the full offset set for licensed games.
Use the same endpoint with your API key:
GET /api/v1/offsets?game=warthunder
Authorization: Bearer <your_api_key>
Premium responses include:
- every resolved offset for the requested licensed game
- offset types
<not-found>markers when a signature needs attention, and"quality": "ambiguous"when a signature matches more than once with different values- your private custom offsets when you have created custom signatures
Historical versions
Free users can read the current public version. Premium users can request historical versions for licensed games:
GET /api/v1/offsets?game=warthunder&version=2.57.1.12
Authorization: Bearer <your_api_key>
Historical access is useful when you need to compare builds, debug old client support, or reproduce a change.
Dev channel data
War Thunder premium users can request the dev channel when it is available:
GET /api/v1/offsets?game=warthunder&channel=dev
Authorization: Bearer <your_api_key>
Dev builds may be less stable than live builds. Treat dev data as early visibility, not a replacement for live offsets.
Changelog and compare
Premium changelogs include more entries and all offsets, not just the free allow-list:
GET /api/v1/changelog?game=warthunder&limit=20
Authorization: Bearer <your_api_key>
Premium users can also compare two versions directly:
GET /api/v1/compare?game=warthunder&v1=2.57.1.10&v2=2.57.1.12
Authorization: Bearer <your_api_key>
Exports
Premium users can export offsets as JSON, C++, C#, Python, or a saved custom template. Code presets scope each group (C++ namespaces, C# nested classes, Python classes), so the file drops into your project and compiles as-is — no name collisions between groups.
GET /api/v1/export?game=warthunder&format=cpp
Authorization: Bearer <your_api_key>
Saved templates let you shape output around your own project instead of rewriting generated files every update.
Aliases
Aliases let you rename offsets in your account without changing the canonical server name.
Use aliases when your codebase has its own naming style or when you want stable local names across refactors.
Webhooks
Premium users can register webhooks for licensed games. Webhooks notify your endpoint when a new version, offset change, or tracked binary event happens — including user_signature.broken, a private event that tells you the moment one of your own custom signatures stops resolving on a new build.
Webhook deliveries are signed with an HMAC secret shown when the subscription is created. Store that secret once; it is not shown again.
See the complete webhook reference for every request body, delivery headers, retry behavior, and signature-verification examples.
Custom signatures
Premium users can add private signatures for licensed games. Write a byte pattern once and the server maintains the offset for you from then on.
- Test before you save. Run any pattern against the current build straight from the panel: you immediately see whether it matches, whether the match is unique, and what value it extracts. No more waiting for the next update to find out a pattern was wrong.
- Auto-resolved on every build. Each new game version is scanned with your signatures automatically. Your values are ready the moment the update is processed — the same pipeline that resolves the official set.
- Breakage alerts. If a build ships that your pattern no longer matches, the signature is flagged in the panel and a
user_signature.brokenwebhook fires at you (and only you). You find out from us, not from your users. - Private by design. The scanner and official signature set stay private, and your custom offset values are visible only to your account. They appear in your normal offset responses and exports with
source: user.
Practical docs and examples
The Python and C++ API quickstart includes downloadable clients for versions, offsets, history, compare, changelog, exports and license status. The same clients support free and premium access; pass your API key to use your license.
For offsets fixed before compilation, the Python download includes update_offsets.py. It verifies the target build, writes the export atomically and preserves the previous file on failure. The guide includes a CMake build step. Webhooks, aliases and custom signatures are managed in the panel; your configured names and private values appear in offset responses and exports.
API key handling
Your API key is shown once when you redeem an invite or rotate the key.
Store it somewhere safe. The panel only keeps your login session, not the plaintext API key. If you lose the key, rotate it from the dashboard and update any clients using the old one.
Use the key as a bearer token:
Authorization: Bearer <your_api_key>
Expiration and renewals
When a license expires, your account is not deleted and the panel remains available with free-tier data. Requests that still send the expired API key return 402 Payment Required so an unattended client cannot silently continue with a reduced offset set. Remove the Authorization header to use the anonymous free tier, or renew from the panel.
After renewal, the same active API key can regain premium access. You do not need to rotate the key unless you want to.
Pricing
Paid access is invite-only while the service is in beta.
Current beta pricing:
$20for 30 days$50for 90 days$90for 180 days
Accounts from before October 23, 2026 keep their original rate ($15 / $40 / $70) on every renewal. The renewal page shows your price.
Every duration includes the same War Thunder premium feature set.
Pricing may change later as the service grows. Early users keep the access term they paid for.
Free vs premium summary
| Feature | Free | Premium |
|---|---|---|
| Current live version | Yes | Yes |
| Public offset allow-list | Yes | Yes |
| Full offset set | No | Yes |
| Historical offsets | No | Yes |
| War Thunder dev channel | No | Yes |
| Changelog | Limited | Full |
| Version compare | No | Yes |
| Exports | No | Yes |
| Aliases | No | Yes |
| Webhooks | No | Yes |
| Custom signatures (test, auto-resolve, breakage alerts) | No | Yes |
| Full exe download where enabled | No | Yes |
Getting access
Paid access is handled manually right now.
To get in:
- Message me on Telegram or Discord, or leave your contact details and I’ll reply when available.
- Say you want War Thunder access.
- After payment is confirmed, you receive a one-time invite link.
- Open the invite link, choose a username and password, then save the API key shown after redemption.
Existing users can renew in the portal. Contact me if you need help.
If you use Discord, allow friend requests and look out for monkrel.
