Demandscope Core: data engine admin
Wandlit accounts, tokens and optional proxies for JEC AI. This page only opens on the gateway PC.
Balance
Wandlit accounts
Each account has its own balance, plan and limits. Two tokens of one account share its money (never two balances). A job stays on one account, except a job that uses the shared pool (below), which may be split across the accounts switched on there. Nothing moves money between accounts. Disable and archive are local to the gateway: nothing is changed or revoked on Wandlit.
| Account | Plan | Left · held · available | Tokens | Runs | Balance read |
|---|
Replace the main account's token (old single-token form)
Shared pool (split jobs across accounts)
A job that costs more than one account's money is split automatically across the accounts switched on here, in this order (lower priority number is used first). A job that cannot be split runs on one account, or is refused before anything is spent. Accounts start OFF: a friend's money is used only after you switch the account on. The caps limit only what shared jobs take (per UTC day / month, on top of the account's own limits); empty = no extra cap. A client uses the pool when its default account is "auto (shared pool)" (Client API keys below) or when it asks for
accountId: "auto"; only its allowed accounts are used.| Order | Account | In pool | Priority (lower first) | Max $ per day (shared jobs) | Max $ per month (shared jobs) | Shared jobs spent today · month | Room left under caps | Available now |
|---|
Who paid what (recent shared jobs)
| When | Job | Client | Total | Paid by account | State |
|---|
Totals are Wandlit costs. A cost that is not final yet counts as its cap in the pool's daily / monthly spend. Click a job to see its parts and runs per account.
Wandlit tokens
A token is checked with Wandlit through its own API route before it is saved (encrypted, never shown again). Its account comes from Wandlit's answer: a token of a known account joins that account. With a proxy route, the token first takes a slot on that proxy IP; a full IP refuses it.
Advanced: scraping through the proxy
One click: every token gets a random working proxy, a different IP for each token while there are enough. Running jobs keep their proxy.
| Token | Account | Proxy (what Wandlit sees) | State | Unfinished runs |
|---|
Proxies (optional)
A proxy makes Wandlit see the proxy's IP instead of yours. 1. Paste your proxies and press Check. 2. Give each working one a name, pick the token that should use it, and press Add. To change it later, use the Proxy column in Wandlit tokens above. If a proxy stops working, its token waits; it never falls back to your own IP.
Saved proxy list
Every list you check or load here is kept for good (encrypted on this PC), so the refill always has proxies to try.
…
Add proxies
Or fill in one proxy field by field
Advanced
Any number of proxies, 50 checked at once. The check runs in the gateway: it keeps going if you reload or close this page, and working proxies appear as soon as they are found. Check only asks an IP-check service which IP each proxy exits from (no Wandlit token is sent). Nothing is saved until you press Add. A rotating proxy changes its IP: use a static / ISP proxy or a sticky session.
| # | Proxy | Result | Country | Name | Use for token |
|---|
Add a proxy IP by hand (you know its fixed exit IP)
Semrush API (optional)
Not set.
| Report | Units per line | Max lines |
|---|
Budgets and limits
Client API keys
Create as many keys as you need, one per app. A key is shown once; the gateway keeps only its hash. Revoke a key and that app stops at once.
| Name | Key ends with | Created | Last used | Runs / cost (30 d) | Wandlit accounts it may use · default | Status |
|---|
A client key is not an Wandlit token and never takes a proxy slot. The v1 API always uses the client's main account; the v2 API may choose among its allowed accounts. Default "auto (shared pool)": requests that name no account use the allowed accounts switched on in the shared pool.
Needs attention
Runs whose start may or may not have reached Wandlit (their cap stays held; they are never started again), stops Wandlit has not confirmed, results not readable yet and costs not final. Every action here is written to the audit log.
Recent runs
| When | Actor | Feature | Account · token | Route | Status | Estimate | Cap | Cost | Items |
|---|
Spend by account and proxy IP (30 days)
| Account / proxy IP | Runs | Cache hits | Wandlit cost | Items |
|---|
Wandlit costs only. Proxy provider fees are billed by the provider and are unknown to the gateway.
Spend by feature (30 days)
| Feature | Runs | Cache hits | Cost | Saved by cache | Items |
|---|
Actor allowlist
Only these actors can run. Max $ per run is the hard cap of one run.
| Actor | Max $ / run | Cache hours | Sensitive | On |
|---|
Scraping proxy per Actor
A token with a Scraping or Both route only runs Actors marked supported; other Actors are refused before anything is spent. Mark an Actor supported only with evidence that its target requests really leave through the proxy IP (an input field that accepts a proxy is not proof). The Actor receives the proxy login in its input, and Wandlit keeps run inputs.
| Actor | Status | Adapter · field · build | Evidence | Change |
|---|
Admin logins
Owner sees this whole page. Agent logs in on the agent page (
/agent) and can only add proxies and API tokens: no balances, tokens, keys or settings.| Username | Role | Created | Last login |
|---|
Audit log
| When | Who | Action | Detail |
|---|